OOR/OOR Team 20080429 Presentation Strawman

Ideas and Developing Plans for the "OOR-Team presentation" for the summit workshop (2008.04.29 pm)    (1E8O)

Pertinent Inputs and Resources    (1E8W)

• OpenOntologyRepository homepage    (1E92)
  • Mission - http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository#nid17YN    (1EA1)
  • the team - http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository#nid17YV    (1EA2)
• OntologySummit2008 homepage    (1E93)
• Leo's opening post on definition: registry vs. repository; goals; roadmap; ...    (1EA3)
• OOR-team discussion on this deliverable - http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2008_03_14#nid1BD9    (1E8Y)
• Proceedings of the four (4) OOR-Panel Sessions:    (1E8Z)
  • OOR-Landscape (2/28) .. Requirements-1 (3/27) .. Requirements-2 (4/3) .. Ontology-of-Ontologies (4/10)    (1E90)
• LeoObrst's posts soliciting input - 4/6 & 4/11    (1E8X)
• ToddSchneider's high-level Requirements summary - http://ontolog.cim3.net/forum/oor-forum/2008-04/msg00012.html    (1E91)

Notes from the 2008.04.19 10:30am EDT conference call    (1E8P)

Attendees: LeoObrst, MikeDean, PeterYim    (1E8Q)

1. Outline of presentation    (1E8R)

• Leo: summarizing - (i) Overview, rationale and motivations, (ii) existing efforts, and how they satisfy the rationale, (iii) what people need, and how they satisfy the rationale, (iv) summarizing that into requirements, and how they satisfy the rationale, & (v) the roadmap to developing/delivering that in an OOR implementation effort, and how they satisfy the rationale <--adopted T    (1E9A)
  • Michelle: maybe we can call item (i) "Value proposition" (which is business speak) T    (1E9B)
    • re: labeling (i), we could do both -- to satisfythe geeks as well as the business folks    (1EA5)

• Mike:    (1E9D)
  • we should look to the past as well as to the future    (1E9E)
  • the communique will be covering a lot of this too, right?    (1E9F)
  • we might tweak this based on input of the day-and-a-half before the presentation    (1E9G)

• Peter: differentiating our presentation vs. the summit presentations    (1E9H)
  • discussion group vs. implementation group    (1E9I)
  • pragmatics    (1E9J)
  • sustainability    (1E9K)
  • the OOR-Team - identifying members, implementers and observers    (1E9L)

2. Splitting up the work    (1E8S)

• Leo: (i) & (ii);    (1E9X)
• Peter - (iii) & (iv);    (1E9Y)
• Mike - (v)    (1E9Z)

3. next call to review merged draft    (1E8T)

4. candidate presentation format / presenters:    (1E8U)

• (i) Opening - Leo - 10 min.    (1E9P)
• (ii) thru (iv) - 10 minutes each    (1E9Q)
  • (ii) existing efforts    (1E9U)
  • (iii) user needs    (1E9V)
  • (iv) implementer requirements    (1E9W)
• (v) roadmap - 20 min    (1E9R)
• open discussion (with Leo, Mike, Peter and panel)    (1E9S)

• candidates (presenters/panel) - Leo, Mike, Peter, Ravi, Ken, Bruce, Todd, Frank, Fabian, Barry, Mike G, ...    (1E9T)

5. milestones    (1E8V)

• plan and split work - Sat 2008.04.19 (now) -    (1E94)
• slide segments exchanged for co-authors review and merge - by the time of the next co-authors call (below)    (1E95)
• next co-authors sync-up call - Mon 2008.04.21 6:00pm EDT / 3:00pm PDT    (1E96)
• merged draft review and released (via [oor-forum]) for team review - by end-of-day Mon 2008.04.21    (1E97)
• team discussion - 2008.04.24 10:30am meeting - ConferenceCall_2008_04_24    (1E98)
• slide deck finalized for submission -    (1E99)

6. Mike's input - discussion with Peter    (1E9C)

• platform, model, federation, connecting other repositories & loose ontologies, support, ... phasing, funding, 'open' advocacy    (1EA0)
• aligning with institutions (like Apache Foundation)    (1E9M)
• community linked by shared best practice ... and a cool logo    (1E9N)
  • use something like the W3C Linking Open Data initiative model as a stepping stone to get the OOR initiative off the ground    (1E9O)