From OntologPSMW

Jump to: navigation, search
[ ]


OpenOntologyRepository: OOR "Hackathon" Session (n.03) - Tue 2013_07_30     (1)

Session Topic: The "OOR-Ontohub-Gatekeeper API - III" Hackathon     (1A)

Session Co-chairs: TillMossakowski & KenBaclawski     (1B)

This is the 3rd session in a series of regular "hackathon" activities for the OOR team. The plan is to devote one meeting a month to intense coding (or other low level development) work.     (1C)

  • Dial-in:     (1D4)
    • Phone (US): +1 (206) 402-0100 ... (long distance cost may apply)     (1D4A)
    • Skype: joinconference (i.e. make a skype call to the contact with skypeID="joinconference") ... (generally free-of-charge, when connecting from your computer ... ref.)     (1D4B)
      • when prompted enter Conference ID: 141184#     (1D4B1)
      • Unfamiliar with how to do this on Skype? ...     (1D4B2)
        • 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.     (1D4B2A)
      • Can't find Skype Dial pad? ...     (1D4B3)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1D4B3A)
        • for Linux Skype users: please note that the dial-pad is only available on v4.1 (or later; or on the earlier Skype versions 2.x,) if the dialpad button is not shown in the call window you need to press the "d" hotkey to enable it. ... (ref.)     (1D4B3B)
    • 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").     (1D5A)
    • 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.     (1D5B)
    • 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!     (1D5C)
  • Discussions and Q & A:     (1D6)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1D6A)
    • 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.)     (1D6B)
    • 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.)     (1D6C)
    • 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.)     (1D6D)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (1D7)
    • view-only password: "ontolog"     (1D7A)
    • 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.     (1D7B)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the [ slides] (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1D7C)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1D9)
  • 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.     (1D11)

Attendees     (1E)

  • Expecting:     (1E2)
    • (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)     (1E3A)

Agenda Ideas     (1E5)

  • review and finish defining the OOR-Ontohub-Gatekeeper API     (1E5A)
  • start setting up requirements on the handling of ontology categorization and ontology metadata     (1E5B)
  • set deliverables, due dates and follow-up action plans     (1E5C)
  • decide on future sessions ... possibly an open session on ontology categorization     (1E5D)
  • ... (add yours)     (1E5E)

Resources     (1E6)

Agenda & Proceedings     (1F)

1. Meeting called to order:     (1F5)

2. Roll Call:     (1F10)

3. Key discussion:     (1F13)

3.1 Review of previous meetings' decision and action items     (1F14)

  • 2013.06.18: we agreed to focus on developing three things (hopefully within the next 3 months): the set of metadata, the API, and some shared thoughts on the UI (ref.)     (1F15)
  • 2013.06.25: we reached consensus that we will be formalizing the API as discussed using the (OMG) Interface Definition Language (IDL) (v3.5)     (1F16)

3.2 work for this hackathon session     (1F17)

  • review and finish defining the OOR-Ontohub-Gatekeeper API     (1F18)
  • start setting up requirements on the handling of ontology categorization and ontology metadata     (1F19)
  • set deliverables, due dates and follow-up action plans     (1F20)
  • decide on future sessions ... possibly an open session on ontology categorization     (1F21)

4. Prior Discussions: ... for reference only!     (1F22)

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

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

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

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

  • (discussion 2011.05.06):     (1F28)
    • an adopted Architecture & API is definitely crucial, but that's not all     (1F28A)
  • All team members are encouraged to mull over how we can get to that state effectively     (1F29)
    • in particular ... how do we make this a "successful" community-driven, open source project!?     (1F29A)
  • (discussion 2011.08.07) ...     (1F30)
    • ref. IAOA Committee and SIG session at FOIS (2012.07.25) discussion:     (1F30A)
      • IAOA Ontology Registry and Repository Committee to put focus on contents     (1F30A1)
      • getting FOIS papers to be submitted with cited ontologies and their metadata, and have those ontologies hosted on OOR     (1F30A2)
  • 4.6 Getting us to a stage when we can run a OOR-production box ... (deferred discussion of this item)     (1F34)
    • we need a gatekeeping/policy module in place - [KenBaclawski]     (1F34A)
  • 4.7 Renewed OOR tactics (as agreed during the 2013.06.18 meeting) - there is general consensus we would change to a more bottom-up approach (rather than the "top-down" approach we have been taking ...     (1F35)
    • we will allow 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.)     (1F35A)
    • 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     (1F35B)
    • we will make to be an ontology registry, which then links to the ontologies in the actual ontology repository where the ontology is described     (1F35C)
    • 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     (1F35D)
    • after that, we will focus on building up content with each OOR node tackling the domain(s) they are best with     (1F35E)

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

see raw transcript here.     (1G1)

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

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

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

Chat transcript from room: oor_20130730     (1G5)

2013-07-30 GMT-08:00 [PDT]     (1G6)

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

OpenOntologyRepository: OOR Hackathon Session n.03 - Tue 2013_07_30     (1G8)

Session Topic: The "OOR-Ontohub-Gatekeeper API - III" Hackathon     (1G9)

This is the first of a series of regular activities for the OOR team. The plan is to devote one meeting a month to intense coding (or other low level development) work.     (1G11)

Proceedings     (1G14)

[7:02] Peter P. Yim: Till: Daniel and Aleksandra are on the same voice line with me     (1G15)

[7:02] Peter P. Yim: Michael: I need to leave in an hour     (1G16)

[7:04] Peter P. Yim: == Till: let's start with the IDL interface     (1G17)

[7:05] Peter P. Yim: Till: Daniel has completely revised the interface (API)     (1G19)

[7:08] Michael Grüninger: my github id is gruninger     (1G20)

[7:09] Till Mossakowski: OK, have added you     (1G21)

[7:10] Peter P. Yim: Till: API needs to be compatible with OMV - ref.     (1G22)

[7:18] Till Mossakowski: TODO: links, covering both ontology alignments, as well as the relation between an OWL version     (1G23)

and the CL version of an ontology     (1G24)

[7:29] Till Mossakowski: [consensus] links are a fundamental notion, hardwired into the API. But the properties of links     (1G26)

are expressed using a meta ontology.     (1G27)

[7:30] Peter P. Yim: == Gatekeeper API discussion     (1G28)

[7:31] Till Mossakowski: [consensus] gatekeeper is included, but modified in that it is about access of users to repositories     (1G29)

(the latter in turn contain ontologies)     (1G30)

[7:32] Peter P. Yim: == Till: discussing the meta-ontology on categories     (1G31)

[7:33] Peter P. Yim: ... Aleksandra explains her work     (1G32)

[7:45] Peter P. Yim: Till: this is a meta-ontology on subjects only     (1G35)

[7:50] Todd Schneider: Why can't the 'categories' of ontology subject be instances of a class 'category' and thus the range of 'hasSubject'?     (1G37)

[7:55] Peter P. Yim: at the OOR level, maybe we want to "under-specify" ... and leave it to the domain-specific     (1G38)

Ontology Repositories (open or otherwise) to define their own categorization     (1G39)

[7:58] Ken Baclawski: The ontology classification should be a distributed ontology in several senses of "distributed".     (1G40)

[7:59] Till Mossakowski: However, all these meta ontologies should be properly aligned, such that they form a     (1G41)

distributed ontology, which can also (using DOL's combine construct) by combined into one big meta ontology.     (1G42)

[8:00] Till Mossakowski: This lifts federation among ontology repositories to the level of meta ontologies, which also     (1G43)

need to be federated and aligned.     (1G44)

provides a meta-classification that according to the domain subjects distributes domain-ontologies into the domain-specific     (1G46)

classes. The first version (respecting the specification of the International Standard Classification of Education (ISCED))     (1G47)

consists of 102 classes. The revised version, extended with biological and medical categories consists of 225 classes.     (1G48)

[8:01] Till Mossakowski: Michael: we should work in a bottom up way, looking at existing meta classifications for ontologies.     (1G49)

[8:03] Till Mossakowski: Michael: we should not freeze things in advance     (1G50)

[8:02] Peter P. Yim: @Aleksandra & Till - ref. the categorization proposed earlier by Mike Dean -     (1G51)

- would this categorization be a subset of the "Domain_fields.owl" ontology now?     (1G52)

[8:04] Till Mossakowski: @Peter: no, it is not (yet)     (1G53)

[7:58] Till Mossakowski: [consensus] OOR and Ontohub should only have a coarse-grained meta-ontology for subject classification.     (1G54)

Different communities will have more specific OOR / Ontohub instances, with more specialized meta ontologies.     (1G55)

The latter should be maintained by these specialized communities.     (1G56)

[8:07] Till Mossakowski: for Ontohub, we plan that the user can add new categories on-the-fly. This is a bit like tagging.     (1G57)

However, we want to force the user to place the new category at some position in the class tree of the meta ontology.     (1G58)

[8:07] Till Mossakowski: This new category can then later be accepted, modified or rejected by the maintainer of the meta ontology.     (1G59)

[8:09] Peter P. Yim: I suspect we are having the same discussion that the people were having! :)     (1G60)

[8:09] Todd Schneider: Good suggestion     (1G61)

[8:12] Peter P. Yim: ... [on further discussion, adopting doesn't seem very appropriate] point well taken;     (1G62)

we can't just adopt ... their scope and use case is very different from ours     (1G63)

[8:15] Todd Schneider: Bottom up is not necessarily bad, only when it's unconstrained.     (1G64)

[8:16] Todd Schneider: Have to go. Cheers.     (1G65)

[8:24] Till Mossakowski: Peter: we have agreed on 1) API, 2) metadata, 3) UI. We can discuss all three points.     (1G66)

[8:25] Till Mossakowski: UI=user interface     (1G67)

[8:27] Till Mossakowski: we agreed on having three topics 1) API, 2) metadata, 3) UI     (1G68)

[8:37] Peter P. Yim: to be exact ... we have agreed *to focus on* three topics 1) API, 2) metadata, 3) UI ... and try to complete     (1G69)

[8:28] Till Mossakowski: in detail, we have more agreement on API than on metadata than on UI     (1G71)

[8:30] Peter P. Yim: we will align our (OOR team) thoughts on categorization at the Sep.10 OOR meeting (internally) ... then     (1G72)

schedule a community session, on Tue Sep.24, to get input and buy-in from other major domain communities (like BioPortal,     (1G73)

Geospatial, Standards, etc.)     (1G74)

... [action] ALL: please start thinking who we should be inviting over to that 9/24 session     (1G75)

[8:32] Peter P. Yim: [action] we will start a wiki page for the categories meta-ontology ... to capture developing work, and     (1G76)

help prepare for the Sep-24 community session     (1G77)

[8:38] Peter P. Yim: next meeting - Tue 2013.09.03 - 7:00am PDT / 10:00am EDT / 4:00pm CEST / 3:00pm BST / 1400 UTC - regular     (1G78)

OOR Team (admin & planning) session     (1G79)

[8:38] Peter P. Yim: talk to you all then! Have a wonderful summer holiday in August!     (1G80)

[8:39] Peter P. Yim: very productive session!     (1G81)

[8:39] Peter P. Yim: -- session ended: 8:37am PDT --     (1G82)

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

6. Action items:     (1G84)

7. Any Other Business: ... (deferred to the next meeting)     (1G86)

  • we have decided to host a community session to collect input, discuss, and gain consensus on the approach towards the "Meta-Ontology for Ontology Categories" - this is now scheduled for Tue 2013.09.24 - start-time: 7:00am PDT / 10:00am EDT / 4:00pm CEST / 3:00pm BST / 1400 UTC     (1G87)
    • we hope stewards of current and developing ontology repositories (folks from BioPortal, SOCoP-OOR, COLORE, Ontohub, and various OOR nodes ... and other domain ontology repositories, like, for Standards, space-portal, etc. )     (1G87A)

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

  • no OOR meeting in the month of August, 2013 - Enjoy the Summer, Everyone!     (1G89)
  • next Meeting - Tue 2013.09.03 - Regular OOR Team planning and admin monthly meeting     (1G90)
  • then we'll have - Tue 2013.09.10 - OOR-hackathon n.04 - Co-chairs: Ken Baclawski & Till Mossakowski     (1G91)
  • also scheduled: Tue 2013.09.24 - OOR community session on "Meta-Ontology for Ontology Categories"     (1G92)
  • regular meeting start-times will be: 7:00am PDT / 10:00am EDT / 4:00pm CEST / 3:00pm BST / 1400 UTC     (1G93)
  • 1st Tuesdays of each month will be for OOR team regular monthly confcall - for admin/planning     (1G94)
  • 2nd Tuesdays of each month will be for OOR-hackathon     (1G95)
  • ... please mark your calendars and make sure you can come!     (1G96)

notes taken by: Peter P. Yim / 2013.07.30-9:59am PDT     (1G99)

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

Resources     (1H)

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

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