From OntologPSMW

Jump to: navigation, search
[ ]


OpenOntologyRepository: OOR Code Development Workshop (n.10) - Tue 2013_12_10     (1)

Topic: Ontohub at OOR: Should the OOR code be based on Ontohub?     (1A)

Session Co-Chairs: TillMossakowski and KenBaclawski     (1B)

  • Dial-in:     (1C4)
    • Phone (US): +1 (206) 402-0100 ...     (1C4A)
    • 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") ...     (1C4B)
      • when prompted enter Conference ID: 141184#     (1C4B1)
      • Unfamiliar with how to do this on Skype? ...     (1C4B2)
        • 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.     (1C4B2A)
        • you may connect to the user:"joinconference" even if the skype GUI shows that this user is offline!     (1C4B2B)
      • Can't find Skype Dial pad? ...     (1C4B3)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1C4B3A)
        • 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. ...     (1C4B3B)
      • 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#     (1C4B4)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: ... view-only password: "ontolog"     (1C5)
    • 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.     (1C5A)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides below (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1C5B)
  • Discussions and Q & A:     (1C6)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1C6A)
    • 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.)     (1C6B)
    • 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.)     (1C6C)
    • 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.)     (1C6D)
    • 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").     (1C7A)
    • 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.     (1C7B)
    • 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!     (1C7C)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1C9)
  • 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.     (1C11)

Attendees     (1D)

  • Expecting:     (1D2)
    • (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)     (1D2B)

Agenda Ideas     (1D4)

In-session Resources     (1D5)

Agenda & Proceedings     (1E)

1. Meeting called to order:     (1E5)

2. Roll Call:     (1E10)

3. Key discussion:     (1E13)

3.2 Open discussion: "Should the OOR code be based on Ontohub?"     (1E15)

4. IM Chat Transcript captured during the session     (1F)

see raw transcript here.     (1F1)

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

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

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

Chat transcript from room: oor_20131210     (1F5)

2013-12-10 GMT-08:00 [PST]     (1F6)

[7:00] Peter P. Yim: Welcome to the     (1F7)

OpenOntologyRepository: OOR Code Development Workshop (n.10) - Tue 2013_12_10     (1F8)

Topic: Ontohub at OOR: : Should the OOR code be based on Ontohub?     (1F9)

Logistics:     (1F11)

  • (if you haven't already done so) please click on "settings" (top center) and morph from "anonymous" to your RealName     (1F13)
  • Mute control (phone keypad): *7 to un-mute ... *6 to mute     (1F14)

(i.e. even if it says it is "offline," you should still be able to connect to it.)     (1F17)

    • if you are using skype and the connection to "joinconference" is not holding up, try using (your favorite POTS or     (1F18A)

VoIP line, etc.) either your phone, skype-out or google-voice and call the US dial-in number: +1 (206) 402-0100     (1F19)

... when prompted enter Conference ID: 141184#     (1F20)

Proceedings     (1F25)

[7:03] anonymous morphed into Paul Alexander     (1F26)

[7:06] Peter P. Yim: == Till Mossakowski and Ken Baclawski starts the session     (1F27)

[7:07] Peter P. Yim: == Till makes presentation on Ontohub - see slides     (1F28)

[7:25] Till Mossakowski: (in response to question from Ken on the availability of the installation instructions)     (1F30)

[7:29] Peter P. Yim: Till: federation will be a feature in the future ... for now, mirroring of git instances is supported     (1F32)

[7:53] Peter P. Yim: I strongly urge a healthy dialog between the Ontohub / OOR team and the (BioPortal) team ... especially towards setting up     (1F33)

an agenda to interface, integrate and federating content of repositories based on these two code-bases in the future     (1F34)

[7:55] Till Mossakowski: Paul: rack is the useful level for speaking with BioPortal.     (1F35)

[7:56] Till Mossakowski: Paul: the triple store is not recommended as a production-level interface. It is more for simple SparQL queries.     (1F36)

[7:57] Till Mossakowski: Paul: The API is being moved to a new version, and it is highly optimized.     (1F37)

[7:58] Till Mossakowski: Paul: some rack middleware (run on both systems) could provide a common interface to program against internally     (1F38)

[7:59] Till Mossakowski: Paul: this would be a more fine-grained integration than just the REST API     (1F39)

[8:00] Till Mossakowski: on the other hand, the RESTful API is already there and requires no extra programming     (1F40)

[8:02] Till Mossakowski: Paul: the API should only give you ontologies that don't have legal issues     (1F41)

[8:02] Peter P. Yim: Paul: access to IPR encumbered content from BioPortal will not be supported through the API     (1F42)

[8:01] Peter P. Yim: would it be possible to schedule, say, quarterly session to align API's and other pertinent issues     (1F46)

(integration, federation, etc.) between the two teams?     (1F47)

[8:15] Peter P. Yim: where do we stand on implementing the mandatory capture of ontology metadata when content is uploaded     (1F48)

... and "gatekeeping" in general     (1F49)

[8:20] Peter P. Yim: I am also concerned that, while both the OOR software license (Simplified BSD)[1] and the Ontohub software license (AGPL)[2]     (1F50)

are open source, the former (Simplified BSD) is a "gift" License, and the latter (AGPL) is a "reciprocal" license. I hope they can be aligned     (1F51)

[8:20] Till Mossakowski: anyone who would want to commercialize the Ontohub software are welcome to talk to us.     (1F54)

[8:20] Peter P. Yim: @Till, I will try to talk to you offline (as I do hope the original spirit of the IPR Policy is maintained.)     (1F55)

[8:24] Till Mossakowski: this is about the tree view of repositories in Ontohub     (1F57)

[8:25] Peter P. Yim: to allow team members to support Ontology Summit 2014, the OOR regular meetings will be paused between now and the     (1F58)

end of the Summit. Therefore, the next regular OOR meeting will be in may 2104.     (1F59)

[8:26] Peter P. Yim: hope Ontohub has a strong representation in the Ontology Summit 2014 organizing team (Oliver?)     (1F60)

[8:26] Peter P. Yim: -- session ended: 8:26am PST --     (1F61)

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

5. Action items:     (1F63)

6. Any Other Business:     (1F65)

7. Schedule Next Meeting & Adjourn:     (1F68)

notes taken by: Peter P. Yim / 2013.12.10-12:29pm PST     (1F72)

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

Resources     (1G)

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

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