From OntologPSMW

Jump to: navigation, search
[ ]


OpenOntologyRepository: Project Team Member (regular planning & admin) Conference Call - Tue 2013_12_03     (1)

This is a regular OOR Team meeting. We will be pick up from our last monthly OOR team confcall on 2013_11_05 and continue to use this meeting to work up plans and administrative details for the OOR Team, and to discuss how we will be supporting the upcoming OntologySummit2014.     (1A)

  • Dial-in:     (1B4)
    • Phone (US): +1 (206) 402-0100 ... (long distance cost may apply)     (1B4A)
    • in view of recently reported skype connection issues, this is not recommended (especially for speakers) although it may still work for some ... Skype: joinconference (i.e. make a skype call to the contact with skypeID="joinconference") ... (generally free-of-charge, when connecting from your computer ... ref.)     (1B4B)
      • when prompted enter Conference ID: 141184#     (1B4B1)
      • Unfamiliar with how to do this on Skype? ...     (1B4B2)
        • Add the contact "joinconference" to your skype contact list first. To participate in the teleconference, make a skype call to "joinconference", then open the dial pad (see platform-specific instructions below) and enter the Conference ID: 141184# when prompted.     (1B4B2A)
        • you may connect to the user:"joinconference" even if the skype GUI shows that this user is offline!     (1B4B2B)
      • Can't find Skype Dial pad? ...     (1B4B3)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1B4B3A)
        • for Linux Skype users: if the dialpad button is not shown in the call window you need to press the "d" hotkey to enable it. ... (ref.)     (1B4B3B)
      • if you are using skype and the connection to "joinconference" is not holding up, try using (your favorite POTS or VoIP line, etc.) either your phone, skype-out or google-voice and call the US dial-in number: +1 (206) 402-0100 ... when prompted enter Conference ID: 141184#     (1B4B4)
  • Discussions and Q & A:     (1B5)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1B5A)
    • To un-mute, press "*7" ... To mute, press "*6" (please mute your phone, especially if you are in a noisy surrounding, or if you are introducing noise, echoes, etc. into the conference line.)     (1B5B)
    • we will usually save all questions and discussions till after all presentations are through. You are encouraged to jot down questions onto the chat-area in the mean time (that way, they get documented; and you might even get some answers in the interim, through the chat.)     (1B5C)
    • During the Q&A / discussion segment (when everyone is muted), If you want to speak or have questions or remarks to make, please raise your hand (virtually) by clicking on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the session moderator (again, press "*7" on your phone to un-mute). Test your voice and introduce yourself first before proceeding with your remarks, please. (Please remember to click on the "hand button" again (to lower your hand) and press "*6" on your phone to mute yourself after you are done speaking.)     (1B5D)
    • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field from "anonymous" to your real name, like "JaneDoe").     (1B6A)
    • You can indicate that you want to ask a question verbally by clicking on the "hand" button, and wait for the moderator to call on you; or, type and send your question into the chat window at the bottom of the screen.     (1B6B)
    • thanks to the folks, one can now use a jabber/xmpp client (e.g. gtalk) to join this chatroom. Just add the room as a buddy - (in our case here) ... Handy for mobile devices!     (1B6C)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: ... view-only password: "ontolog"     (1B7)
    • if you plan to be logging into this shared-screen option (which the speaker may be navigating), and you are not familiar with the process, please try to call in 5 minutes before the start of the session so that we can work out the connection logistics. Help on this will generally not be available once the presentation starts.     (1B7A)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the [ slides above] (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1B7B)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1B9)
  • 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 our prevailing open IPR policy.     (1B11)

Attendees     (1C)

  • Expecting:     (1C2)
    • (please add yourself to the list above if you are a member of the community, or, rsvp to <> with the event title/date and your name and affiliation)     (1C2B)

Agenda Ideas     (1C4)

Agenda & Proceedings     (1D)

1. Meeting called to order:     (1D4)

2. Roll Call:     (1D9)

3. Key discussion:     (1D12)

Ref: our list of "Priorities & Most Critical Tasks At Hand" -     (1D13)

3.1 Review OOR priorities and focus     (1D14)

  • there is general consensus we would change to a more bottom-up approach (rather than the "top-down" approach we have been taking) ...        (1D15)
    • we will encourage each oor node project to develop (colore, ontohub, socop, oor public instance, etc.) on their own, and coordinate the "team" effort through the use of a shared set of metadata, API and the UI (e.g. how people download (or even upload) ontologies, etc.)     (1D15A)
    • The key is to ensure that each of the ontology repository projects in OOR are interoperable from the software perspective, uniform in the GUI, and they use a shared approach to ontology metadata     (1D15B)
    • initially (prior to federation mechanisms being in place) we will make <> to be an ontology registry, which then links to the ontologies in the actual ontology repository where the ontology is described     (1D15C)
    • actions will be focused on developing three things (hopefully within the next 3 months): the set of metadata, the API, and some shared thoughts on the UI     (1D15D)
    • after that, we will focus on building up content with each OOR node tackling the domain(s) they are best with, and put in a concerted effort towards OOR adoption     (1D15E)

3.2 scheduling of OOR Events'     (1D18)

3.3 OOR and our support for the upcoming Ontology Summit 2014     (1D21)

most of the content below are inherited from the previous call(s), and will be edited/updated as this meeting progresses ...     (1D24)

4. Prior Discussions:     (1D26)

4.1 Discussion: tactically, what shall we be doing differently in the next 6 to 12 months     (1D27)

... to provide synergies for all.     (1D29)

4.2 Setting the metrics - what does "success" look like     (1D30)

4.3 Action planning for "content drive" (getting people to upload ontologies) ... (deferred discussion of this item)     (1D31)

  • (discussion 2011.05.06):     (1D32)
    • an adopted Architecture & API is definitely crucial, but that's not all     (1D32A)
  • All team members are encouraged to mull over how we can get to that state effectively     (1D33)
    • in particular ... how do we make this a "successful" community-driven, open source project!?     (1D33A)
  • (discussion 2011.08.07) ...     (1D34)
    • ref. IAOA Committee and SIG session at FOIS (2012.07.25) discussion:     (1D34A)
      • IAOA Ontology Registry and Repository Committee to put focus on contents     (1D34A1)
      • getting FOIS papers to be submitted with cited ontologies and their metadata, and have those ontologies hosted on OOR     (1D34A2)
  • 4.6 Getting us to a stage when we can run a OOR-production box ... (deferred discussion of this item)     (1D38)
    • we need a gatekeeping/policy module in place - [KenBaclawski]     (1D38A)

5. IM Chat Transcript captured during the session     (1E)

see raw transcript here.     (1E1)

(for better clarity, the version below is a re-organized and lightly edited chat-transcript.)     (1E2)

Participants are welcome to make light edits to their own contributions as they see fit.     (1E3)

-- begin in-session chat-transcript --     (1E4)

Chat transcript from room: oor_20131203     (1E5)

2013-12-03 GMT-08:00 [PST]     (1E6)

[6:56] Peter P. Yim: Welcome to the     (1E7)

OpenOntologyRepository: Project Team Member Meeting - Tue 2013_12_03     (1E8)

This is a regular monthly planning & admin Conference Call     (1E9)

Attendees: Ken Baclawski, Mike Bennett (joined late), Mike Dean, Peter P. Yim (chair/scribe)     (1E11)

Proceedings:     (1E12)

[7:08] Peter P. Yim: == discussion on what we should focus on at the OOR-Hackathon n.05 (slated for next Tuesday)     (1E13)

(a) ontologies to support API4KBs and OntoIOp by Tara Athan and Elisa Kendall     (1E15)

(b) the OOR API and its current realisation in OntoIOp (41X0)     (1E17)

(c) integrating, or providing the API to incorporate OMV (extensions thereof; or even some generic set of metadata     (1E18)

for an ontology) to an OOR (actually, open or non-open.) (41X1)     (1E19)

(d) federation (42CX)     (1E20)

(e) ... more ideas? (41X2)     (1E21)

[7:18] Peter P. Yim: Ken: possibilities (e) debug why the SOCoP-OOR is down, (f) debug when the O&M ontology ran     (1E22)

into parsing error with the SOCoP-OOR     (1E23)

[7:27] Peter P. Yim: [consensus] Ken / Mike / Peter: let's do this next Tuesday (Dec-10) (e) & (f) for the OOR-Hackathon n.05     (1E24)

[7:31] Peter P. Yim: [action] Peter will try to restart the SOCoP-OOR (which is down again now) ... or restore the vm image ... [done. system rebooted, and the SOCoP-OOR is operational again.--ppy/2013.12.08 ]     (1E25)

[7:32] Ken Baclawski: [re next Tuesday's Hackathon n.05 session (which is supposedly co-chaired by Ken & Till)] If Till     (1E26)

attends the session, then it would be helpful if he could tell us about his experience with mirroring the SOCoP ontologies     (1E27)

especially with regard to the issue of federation. However, the session would not be addressing federation as one of its objectives.     (1E28)

[7:33] Ken Baclawski: I will write up (e) and (f) on the Hackathon wiki page.     (1E29)

[7:29] Peter P. Yim: == discussion on who or whether we will still stand up a bioportal-based OOR instance when the next     (1E30)

revision level of the vm image comes out     (1E31)

[7:29] Peter P. Yim: if at all, I suggest that it should be done on AWS (the amazon cloud)     (1E32)

[7:40] Ken Baclawski: Would it make sense to try basing OOR on the OntoHub code rather than on BioPortal code?     (1E33)

[7:48] Peter P. Yim: another possibility is to cancel the Hackathon n.05 session, and use the Tue Dec-10 meeting to discuss     (1E34)

the "basing OOR on the OntoHub code" possibility     (1E35)

[7:48] Peter P. Yim: [action] Ken will ping Till about this     (1E36)

[7:51] Peter P. Yim: [consensus] unless we feel we need another session, we will pause after the Dec-10 session, and put the full force of the OOR team to support Ontology Summit 2014 ... that means, after the Dec-10 OOR meeting, the next one will be in ~May-2014 (of course, there may be joint OOR-OntologySummit activities in the interim, while Ontology Summit 2014 is in session.)     (1E37)

[7:54] Peter P. Yim: Ken will advise Peter on next Tuesday's session agenda (so he can create the session page for it) by this Friday, hopefully.     (1E38)

[7:56] Peter P. Yim: -- session ended: 7:55am PST --     (1E39)

-- end in-session chat-transcript --     (1E40)

6. Action items:     (1E41)

  • Peter will try to restart the SOCoP-OOR instance again.     (1E42)
  • Ken will confer with Till, and confirm to Peter on the agenda for the next OOR call for Tue Dec-10.     (1E43)

7. Any Other Business:     (1E44)

  • [consensus] unless we feel we need another session, we will pause after the Dec-10 session, and put the full force of the OOR team to support Ontology Summit 2014 ... that means, after the Dec-10 OOR meeting, the next one will be in ~May-2014 (of course, there may be joint OOR-OntologySummit activities in the interim, while Ontology Summit 2014 is in session.)     (1E45)

8. Schedule Next Meeting & Adjourn:     (1E46)

notes taken by: Peter P. Yim / 2013.12.03-8:11am PST     (1E50)

All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.     (1E51)

Resources     (1F)

  • the Joint IAOA-OOR-Ontolog "Ontologies and Standards" mini-series:     (1F18)

This page has been migrated from the OntologWiki - Click here for original page     (1F27)