From OntologPSMW

(Difference between revisions)
Jump to: navigation, search
(Formatting and additional content Last updated at: 2008-03-24 16:11:49 By user: MichelleRaymond)
(Format and spell-check Last updated at: 2008-03-24 16:46:53 By user: MichelleRaymond)
Line 20: Line 20:
 
** When calling in from a phone, use '''Conference ID: "5823120#"'''  
 
** When calling in from a phone, use '''Conference ID: "5823120#"'''  
 
** from a '''US telephone (US): +1-605-475-8590''' (South Dakota, USA)  
 
** from a '''US telephone (US): +1-605-475-8590''' (South Dakota, USA)  
 
 
** callers '''from other countries''' please dial into either one of the US or European numbers
 
 
* Please note that this session may be recorded, and if so, the audio archive is expected to be made available as open content, along with the proceedings of the call to our community membership and the public at-large under [[WikiHomePage|our prevailing open IPR policy]].
 
  
 
== Attendees:  ==
 
== Attendees:  ==
Line 41: Line 36:
 
** PatHayes  
 
** PatHayes  
  
* Regets:  
+
* Regrets:  
 
** [[BarrySmith]]  
 
** [[BarrySmith]]  
  
Line 60: Line 55:
 
* [[MichelleRaymond]] took the chair and welcomed everyone  
 
* [[MichelleRaymond]] took the chair and welcomed everyone  
 
* [[RaviSharma]] volunteered to take minutes of the meeting  
 
* [[RaviSharma]] volunteered to take minutes of the meeting  
* review and adopt agenda
 
  
 
2. Attendees:  
 
2. Attendees:  
 +
see above
  
 
3. Discussion:  
 
3. Discussion:  
  
 
Ties to the Program Planners and F2F-Program Agenda  
 
Ties to the Program Planners and F2F-Program Agenda  
 
* Tie to Communique'and F2F Program
 
** Michelle: 
 
** Mark and Leo will provide details of how champions will provide content for the Communique'.
 
  
 
*   
 
*   
** Michelle:
+
** Michelle:  
** Need to talk about time each group needs at the F2F for content summary and discussion.
+
** Mark and Leo will provide details of how champions will provide content for the Communiqu�'.  
** Suggestion from the Organizing Committee is at least half of the time be for discussions, based on breadth and depth of discussions.
+
 
** Champions can summarize or minipanel approach for presentations.
+
* Time duration for Topic Area F2F Sessions
** For OOR Architecture Michelle's (and Ravi agrees) suggestion is that we present a couple of different frameworks and related architecture issues as examples.
+
** Michelle:
 +
** Suggestion from the Organizing Committee is at least half of the time be for discussions, based on breadth and depth of discussions.  
 +
** Champions can summarize or minipanel approach for presentations.  
 +
** For OOR Architecture Session Michelle's (and Ravi agrees) suggestion is that we present a couple of different frameworks and related architecture issues as examples.  
 
** Fabian:  
 
** Fabian:  
** Concern that a panel approach may rehash thread conversations instead of bringing together concenses.
+
** Concern that a panel approach may rehash thread conversations instead of bringing together consensus.  
** Leo suggested:
+
** Leo suggested:  
** Short synopsis and starting position modified slightly by session chairs would help start off a Topic Session.
+
** Short synopsis and starting position modified slightly by session chairs would help start off a Topic Session.  
 
** Fabian:  
 
** Fabian:  
 
** On the second day if there are session "recaps" given by the session chair, those will feed into a final version of final document of Summit and may be a way of reaching consensus.  
 
** On the second day if there are session "recaps" given by the session chair, those will feed into a final version of final document of Summit and may be a way of reaching consensus.  
** Leo:
+
** Leo:  
** While individuals are updating the Topic Wiki Page's with individual contributions from the group, provide not just threads but a summary. The summary in the Wiki can be incorporated in the Communique'
+
** While individuals are updating the Topic Wiki Page's with individual contributions from the group discussions, provide not just threads but a summary. The summary in the Wiki can be incorporated in the Communiqu�'  
 
** The summary needs to be ready earlier than the F2F, by a week.  
 
** The summary needs to be ready earlier than the F2F, by a week.  
 +
** Michelle:
 +
** Suggest closely moderated session by champions to direct the discourse and to keep focus by a panel on a communiqu�' section.
 +
** Peter:
 +
** Suggested as to Why it is in the communiqu�'.
 +
 +
* Communique'
 +
** Leo:
 +
** Will contain four Sections of intellectual content and one for Second day OOR summary. That takes us through what we have done towards realizing an OOR.
 +
** The Topic summaries and sections need to be ready earlier than the F2F, by a week.
 +
** Michelle:
 +
** Previous Communiqu�' have been typically 2 pages - so say half page from each topic section?
 +
** Leo:
 +
** Yes it is a good goal, but can be say expanded to five pages.
 +
** Fabian:
 +
** Just a few sentences would be hard to do.
 +
** Peter and Michelle:
 +
** Suggestion to look at Communiqu�s from last two Summits.
  
* F2F Session lengths and starting time
+
* F2F Session lengths and starting time  
 
** Michelle:  
 
** Michelle:  
** How much time should be used for each of the 4 major sections presentations?
+
** How much time should be used for each of the 4 major sections presentations?  
 
** ?:  
 
** ?:  
** The F2F draft agenda has different lengths of time for different topics.  The first session is squeezed into 1 hour.  
+
** The F2F draft agenda has different lengths of time for different topics.  The first session is squeezed into 1 hour.  
 
** Peter:  
 
** Peter:  
 
** This is due to a NIST policy of not being able to serve refreshments until a conference has started.  It can be served at a break, but not prior to the start.  
 
** This is due to a NIST policy of not being able to serve refreshments until a conference has started.  It can be served at a break, but not prior to the start.  
Line 99: Line 110:
 
** Action: Peter will ask Steve Ray about having an 8am start time.  
 
** Action: Peter will ask Steve Ray about having an 8am start time.  
  
* Communique
+
Relevant Ontology-Forum panels
** Leo:
+
** Will contain four Sections of intellectual content and one for Second day OOR summary. That takes us through what we have done towards realizing an OOR. 
+
** The Topic summaries and sections need to be ready earlier than the F2F, by a week.
+
  
Peter Summarized the rich variety of upcoming events on 03/27, 04/03 and 04/10 that will be very varied and with rich presentations that will also have 45 minutes of Q&A time.  See details [http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/JointPanelSession_Strawman#nid1BFW here].  
+
* Peter Summarized the rich variety of upcoming events on 03/27, 04/03 and 04/10 that will be very varied and with rich presentations that will also have 45 minutes of Q&A time.  See details [http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/JointPanelSession_Strawman#nid1BFW here].  
  
Fabian: Different Perspectives on Ontologies - agreement on all types of ontologies amenable to repositories, therefore discussion summary document is required.
+
Topic Status
  
Michelle: Mainpage Ontology of Ontologies specifically added on main Summit page. Awaiting marching orders from Leo and Mark.  
+
* Fabian (for Quality and Gatekeeping):  
 
+
** Different Perspectives on Ontologies - agreement on all types of ontologies amenable to repositories, therefore discussion summary document is required.  
<pre>
+
* Michelle (for Repository Architecture):
 
+
** Not an active week. Intend to get more content on wiki from discussions and get more discussions going.  
</pre>
+
  
 
4. New Issues:  
 
4. New Issues:  
Line 120: Line 127:
 
6. Action items:  
 
6. Action items:  
  
* Mark and Leo will put out a structure for the champions to provide Communique' content.
+
* Mark and Leo will put out a structure for the champions to provide Communiqu�' content.  
 
* Peter will ask Steve Ray about having an 8am start time.  
 
* Peter will ask Steve Ray about having an 8am start time.  
 
Await Leo and Mark's guidelines and we continue to provide content for the Summit.
 
  
 
7. Verify Time and Agenda for Weekly Content Committee Meeting & Adjourn:  
 
7. Verify Time and Agenda for Weekly Content Committee Meeting & Adjourn:  
Line 129: Line 134:
 
<pre>
 
<pre>
 
--
 
--
notes taken by: [[RaviSharma]] / 2008.03.24- PDT
+
notes taken by: [[RaviSharma]] / 2008.03.24-5:26 EDT
 
All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.  
 
All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.  
 
</pre>
 
</pre>
  
 
----
 
----

Revision as of 11:02, 18 December 2012

[ ]

Contents

OntologySummit2008 - Content Committee Meeting - Mon 2008-03-24     (1)

  • This is the 3rd of the OntologySummit2008 Content Committee's weekly information sharing conference calls. The call is expected to be ~1 Hour.     (1A)
  • The key purpose of these meetings is to share information about discussion topics and     (1C)

content coordination best practices.     (1D)

As facilitators of the Summit Content Committee, our purpose is to invigorate discussion within the OntologySummit2008 and assure that the community can effectively explore, debate, deliberate and capture that content through our online discourse, between the Feb-27 Launch Event and the Apr-28 & 29 (2008) face-to-face workshop.     (1E)

Attendees:     (1H)

Agenda Ideas     (1I)

  • (please insert content below; identify yourself for follow-up purposes)     (1I1)
  • Report on tie-in of Content activities to the Program Planners and F2F-Program Agenda     (1I2)
  • Mention applicable upcoming Ontolog Forum panel sessions.     (1I3)
  • Discuss progress of discussion threads.     (1I4)
    • Brief topic area activity summaries given by one or both topic area champions.     (1I4A)

Agenda and Proceedings     (1J)

1. Meeting called to order:     (1J1)

2. Attendees: see above     (1J4)

3. Discussion:     (1J5)

Ties to the Program Planners and F2F-Program Agenda     (1J6)

  • Time duration for Topic Area F2F Sessions     (1J8)
    • Michelle:     (1J8A)
    • Suggestion from the Organizing Committee is at least half of the time be for discussions, based on breadth and depth of discussions.     (1J8B)
    • Champions can summarize or minipanel approach for presentations.     (1J8C)
    • For OOR Architecture Session Michelle's (and Ravi agrees) suggestion is that we present a couple of different frameworks and related architecture issues as examples.     (1J8D)
    • Concern that a panel approach may rehash thread conversations instead of bringing together consensus.     (1J8F)
    • Leo suggested:     (1J8G)
    • Short synopsis and starting position modified slightly by session chairs would help start off a Topic Session.     (1J8H)
    • On the second day if there are session "recaps" given by the session chair, those will feed into a final version of final document of Summit and may be a way of reaching consensus.     (1J8J)
    • While individuals are updating the Topic Wiki Page's with individual contributions from the group discussions, provide not just threads but a summary. The summary in the Wiki can be incorporated in the Communiqu�'     (1J8L)
    • The summary needs to be ready earlier than the F2F, by a week.     (1J8M)
    • Michelle:     (1J8N)
    • Suggest closely moderated session by champions to direct the discourse and to keep focus by a panel on a communiqu�' section.     (1J8O)
    • Suggested as to Why it is in the communiqu�'.     (1J8Q)
  • F2F Session lengths and starting time     (1J10)
    • Michelle:     (1J10A)
    • How much time should be used for each of the 4 major sections presentations?     (1J10B)
    • The F2F draft agenda has different lengths of time for different topics. The first session is squeezed into 1 hour.     (1J10D)
    • This is due to a NIST policy of not being able to serve refreshments until a conference has started. It can be served at a break, but not prior to the start.     (1J10F)
    • Start at 8am instead of 8:30 am and thus have time for a longer session before the "break" and refreshments.     (1J10H)
    • Action: Peter will ask Steve Ray about having an 8am start time.     (1J10I)

Relevant Ontology-Forum panels     (1J11)

  • Peter Summarized the rich variety of upcoming events on 03/27, 04/03 and 04/10 that will be very varied and with rich presentations that will also have 45 minutes of Q&A time. See details here.     (1J12)

Topic Status     (1J13)

  • Fabian (for Quality and Gatekeeping):     (1J14)
    • Different Perspectives on Ontologies - agreement on all types of ontologies amenable to repositories, therefore discussion summary document is required.     (1J14A)
  • Michelle (for Repository Architecture):     (1J15)
    • Not an active week. Intend to get more content on wiki from discussions and get more discussions going.     (1J15A)

4. New Issues:     (1J16)

5. Any Other Business:     (1J17)

6. Action items:     (1J18)

  • Mark and Leo will put out a structure for the champions to provide Communiqu�' content.     (1J19)
  • Peter will ask Steve Ray about having an 8am start time.     (1J20)

7. Verify Time and Agenda for Weekly Content Committee Meeting & Adjourn:     (1J21)

--
notes taken by: [[RaviSharma]] / 2008.03.24-5:26 EDT
All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.