Folks, (01)
We had a really productive meeting on Friday (15-Oct-2010), discussing
various aspects of the (post BioPortal fork) OOR Architecture and API.
We went through key tenets that should drive decisions on the "new"
architecture; major contributors and ongoing work that we want to
accommodate; various approaches and options that have been proposed,
and then decided that we will delegate the next level of details to
our OOR Architecture Committee. (02)
Full proceedings (including the proposed approaches, in-session
chat-transcript, full audio recording, etc.) are now online.
Please refer to them at:
http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_15#nid2J3M (03)
Please review the proceedings (especially if you had missed this very
important meeting) and/or make necessary amendments as you deem fit
(if you were there, and the proceedings may have been inadequate in
representing your position, etc.) (04)
Thanks to all the contributing parties and all who were there at the
meeting, for the huge contribution they are making to the OOR
initiative! (05)
Best regards. =ppy (06)
p.s. we are also finalizing on a new set of meeting times for the OOR
team, and are exploring having OOR team meetings on all Fridays
meetings, alternating (every other week) between discussing high level
issues, content, project management, administration, etc. one week,
and then doing deep-water technical work on the next. We could even
have two separate sets of standard meeting times for them. Therefore,
all active members are urged to respond to the doodle poll (at:
http://doodle.com/a2snxkpkd8hhxek4 ) if you haven't already.
-- (07)
---------- Forwarded message ----------
From: Peter Yim <peter.yim@xxxxxxxx>
Date: Thu, Oct 14, 2010 at 9:30 AM
Subject: OOR Team Conference Call - Architecture & API discussion -
Fri 2010.10.15
To: OpenOntologyRepository-discussion <oor-forum@xxxxxxxxxxxxxxxx> (08)
Re: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_15 (09)
Note that our "big" team meeting to discuss our "post-fork" OOR
architecture and API is coming up tomorrow.
RSVP ... if you haven't already! (010)
This is a very important meeting ... if you are contributing to the
code development, you need to be there to be heard!
(ref. in particular, related discussion from our last meeting on this
- http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_01#nid2IFW
). (011)
Do pay special attention to the fact that the start time of this
meeting is : 9:00am EDT / 6:00am PDT / 3:00pm CEST / 2:00pm BST /
13:00 UTC) - and is three hours earlier than that of the previous
regular OOR-team meetings. (012)
= REMINDER = (013)
* Date: Friday, 15-Oct-2010
* Start Time: 12:00pm EDT / 9:00am PDT / 6:00pm CEST / 5:00pm BST / 16:00 UTC
o ref: World Clock -
http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=3&year=2010&hour=6&min=0&sec=0&p1=224
* Expected Call Duration: 1.5~2.0 Hour(s)
* Dial-in Number:
o from US: 1-218-844-8060 (domestic long distance cost will apply)
+ Conference ID: "4389979#"
o ... more dial-in numbers (from Europe) will be available on the session page (014)
The session page with agenda, etc. will be up, by the time of the call,
at: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_15 (015)
In particular, our agenda for the session is roughly as follows:
(http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_15#nid2J25
) and we will likely be asking the following pertinent questions: (016)
* Key requirements of the new OOR architecture? (very brief ... this
can take over the whole session otherwise!) (2J2U) (017)
* Who are the immediate software contributors that we will need to
accommodate? (2J2V) (018)
* Enumerating our options and candidate architectural approaches (1
slide (max. 2) from anyone who has a proposal.) (2J2W) (019)
* interim consensus on key tenets of the OOR architecture? ...
delegate to a small team to work this offline? (2J2X) (020)
* Suggestions towards defining an API (1 to 2 slides from anyone who
has a proposal.) (2J2Y) (021)
* interim OOR API-related consensus? ... delegate to a small team to
work this offline? (2J2Z) (022)
* Recommended development platform ... consensus (2J37) (023)
* Immediate next steps and action items. (2J30) (024)
* any other business (2J31)
** discussion on future regular meeting time -
http://www.doodle.com/a2snxkpkd8hhxek4 (025)
... Please provide any additional input (especially if you are going
to be contributing code and can't join us at the call) or suggest any
other agenda ideas via this thread (you may add directly to the wiki
session page too ). (026)
Come to the meeting, *prepared*. Kindly e-mail me any slides if you
are planning to share them during the session (see and observe above
guidelines, please; and do so at least one hour before start-time.) (027)
RSVP ... add your name to the expected attendee list on the session
page or email me offline. (028)
Talk to you all tomorrow! (029)
Thanks & regards. =ppy (030)
p.s. if you are an active OOR team member, and haven't yet responded
to the doodle poll on meeting time, please
goto: http://www.doodle.com/a2snxkpkd8hhxek4 ... and provide us your input, NOW!
-- (031)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-forum/
Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-forum/
Shared Files: http://ontolog.cim3.net/file/work/OOR/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (032)
|