View source for OntologySummit2008/ContentCommitteeMeeting 2008 03 24

= [[OntologySummit2008]] -  Content Committee Meeting - Mon 2008-03-24  =

* This is the 3rd of the [[OntologySummit2008]] Content Committee's weekly information sharing conference calls. The call is expected to be ~1 Hour. 

* URL for this page: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2008/ContentCommitteeMeeting_2008_03_24 

* The key purpose of these meetings is to share information about discussion topics and 
content coordination best practices. 

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. 

=== [[MeetingsCalls|Conference Call]] Details:  ===

* Date: '''March 24, 2008 ''' 
* Start Time: 1:30pm PDT / 4:30pm EDT / 20:30 UTC 
** ref: [http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=5&year=2008&hour=10&min=15&sec=0&p1=224 World Clock] 
* Expected Call Duration: ~1.0 hours 
* Dial-in Number: 
** Direct call from from '''Skype: +990008275823120''' 
** When calling in from a phone, use '''Conference ID: "5823120#"''' 
** from a '''US telephone (US): +1-605-475-8590''' (South Dakota, USA) 

== Attendees:  ==

* Attended: 
** [[PeterYim]] 
** [[MichelleRaymond]] 
** [[RaviSharma]] 
** [[LeoObrst]] 
** [[FabianNeuhaus]] 

* Expecting: 
** [[RexBrooks]] 
** [[MichaelGruninger]] 
** [[FrankOlken]] 
** [[PatHayes]] 

* Regrets: 
** [[BarrySmith]] 

== Agenda Ideas  ==

* ''(please insert content below; identify yourself for follow-up purposes)'' 

* Report on tie-in of Content activities to the Program Planners and F2F-Program Agenda 
* Mention applicable upcoming Ontolog Forum panel sessions. 
* Discuss progress of discussion threads. 
** Brief topic area activity summaries given by one or both topic area champions. 
* ... 

== Agenda and Proceedings  ==

1. Meeting called to order: 

* [[MichelleRaymond]] took the chair and welcomed everyone 
* [[RaviSharma]] volunteered to take minutes of the meeting 

2. Attendees: 
see above 

3. Discussion: 

Ties to the Program Planners and F2F-Program Agenda 

*  
** Michelle: 
** Mark and Leo will provide details of how champions will provide content for the Communiqué'. 

* Time duration for Topic Area F2F Sessions 
** 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: 
** Concern that a panel approach may rehash thread conversations instead of bringing together consensus. 
** Leo suggested: 
** Short synopsis and starting position modified slightly by session chairs would help start off a Topic Session. 
** 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. 
** Leo: 
** 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. 
** 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 
** Michelle: 
** 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. 
** 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. 
** ?: 
** Start at 8am instead of 8:30 am and thus have time for a longer session before the "break" and refreshments. 
** Action: Peter will ask Steve Ray about having an 8am start time. 

Relevant Ontology-Forum panels 

* 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]. 

Topic Status 

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

4. New Issues: 

5. Any Other Business: 

6. Action items: 

* 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. 

7. Verify Time and Agenda for Weekly Content Committee Meeting & Adjourn: 


--
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. 


----