From OntologPSMW

Jump to: navigation, search
[ ]


OOR Panel Discussion: "Getting OOR Development Going - Take-IV" - Fri 17-Sep-2010     (1)

This session is sometimes referred to as the "fork" session. The key issue being addressed at this virtual workshop session is on how we should manage to incorporate various ongoing OOR-related software development efforts, and how best to "fork" from the BioPortal codebase while staying synergistic.     (1A)

  • Co-chairs: Dr. ToddSchneider (Raytheon) and Professor MichaelGruninger (U of Toronto)     (1B)

  • Shared-screen support (VNC session) will be started 5 minutes before the call at:     (1E5)
    • view-only password: "ontolog"     (1E5A)
    • 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.     (1E5B)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides above and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1E5C)
  • Discussions and Q & A:     (1E6)
    • (Unless the conference host has already muted everyone) Please mute your phone, by pressing "*2" on your phone keypad, when a presentation is in progress. To un-mute, press "*3"     (1E6A)
    • You can type in your questions or comments through the browser based chat session by:     (1E6B)
      • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field). 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.     (1E6C1)
    • (when everyone is muted) If you want to speak or have questions or remarks to make, please "raise your hand (virtually)" by click on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the speaker or the session moderator (again, press "*3" on your phone to unmute). 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 "*2" on your phone to mute yourself after you are done speaking.)     (1E6D)
    • 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!     (1E6E)
  • Please note that this session will be recorded, and the audio archive is expected to be made available as open content to our community membership and the public at-large under our prevailing open IPR policy.     (1E10)

Attendees     (1G)

Resources     (1G5)

Agenda & Proceedings     (1H)

Session Topic: "Getting OOR Development Going - Take-IV"     (1H1)

Abstracts     (1I)

This session is sometimes referred to as the "fork" session. The key issue being addressed at this virtual workshop session (as the new OOR code repository at emerges) is on how we should manage to incorporate various ongoing OOR-related software development efforts, and how best to "fork" from the BioPortal codebase while staying synergistic.     (1I2A)
Figure 1: A Concept Map on OOR Development     (1I4A1A)

Transcript of the online chat during the session     (1I5)

see raw transcript here.     (1I5A)

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

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

-- begin of chat session --     (1I5D)

Welcome to the OOR Panel Discussion: "Getting OOR Development Going - Take-IV" - Fri 17-Sep-2010     (1I5F)

This session is sometimes referred to as the "fork" session. The key issue being addressed     (1I5G)

at this virtual workshop session is on how we should manage to incorporate various ongoing     (1I5H)

OOR-related software development efforts, and how best to "fork" from     (1I5I)

the BioPortal codebase while staying synergistic.     (1I5J)

o Dr. Todd Schneider (OOR; Raytheon) - "Getting OOR Development Going - a proposal"     (1I5M)

o Mr. Mike Dean (OOR; Raytheon-BBN) - "The OOR Code Repository"     (1I5N)

- to be presented by Peter P. Yim on MikeDean's behalf     (1I5O)

o Dr. Natasha Noy (NCBO; Stanford-BMIR) - "Forking OOR Development: Thoughts from NCBO"     (1I5P)

o Dr. Immanuel Normann (Bremen U; BORG) - "More Service Orientation to open Ontology Repositories - HeTS, TNTBase, and OOR"     (1I5Q)

o Professor Ken Baclawski (Northeastern U) - "OOR: Architecture and Interfaces"     (1I5R)

o Dr. Alexander Garcia (Bremen U BORG) - "The ORATE Contribution"     (1I5S)

o Professor Michael Grüninger (U of Toronto; IAOA) - "Concerns from the vantage point of COLORE"     (1I5T)

Please refer to details on the session page     (1I5U)

anonymous morphed into Paul Alexander     (1I5W)

anonymous1 morphed into Todd Schneider     (1I5X)

anonymous morphed into Nikkia Anderson     (1I5Y)

Alan Rector: Todd - could you speak louder? thanks     (1I5Z)

anonymous morphed into Elizabeth Florescu     (1I5AA)

Cameron Ross: @All - The BioPortal resource model seems oriented around OWL-based(?) terms like     (1I5AC)

concepts, instances and properties etc. This doesn't seem to align well with general CL theories.     (1I5AD)

Does anyone have ideas on how to rationalize this?     (1I5AE)

Simon Spero: Github (and git in general)++     (1I5AF)

Simon Spero: But can track svn repository     (1I5AG)

Cameron Ross: @NatashaNoy - Is all BioPortal data stored as triples within MySQL?     (1I5AH)

Paul Alexander: @Cameron: BioPortal data is not currently stored as triples, but that's where we'll     (1I5AI)

be moving in the future. Currently OWL/Protege ontologies are stored in a Protege back-end. OBO,     (1I5AJ)

RRF, etc are stored using LexEVS. Metadata is stored in a Protege back-end as well.     (1I5AK)

Cameron Ross: @PaulAlexander - Is the Protege back-end just and XML file, or is it some kind of     (1I5AL)

database?     (1I5AM)

Paul Alexander: MySQL with one table per ontology and another table for the metadata     (1I5AO)

Cameron Ross: @All - I think storing general CL in a triple store will be a challenge.     (1I5AQ)

Paul Alexander: RE: Common Logic fitting the OWL model. It wouldn't be difficult to have a separate     (1I5AR)

set of REST services to handle common logic. Of course this would make it so there is no common     (1I5AS)

method for accessing all of the resources in the repository.     (1I5AT)

Cameron Ross: @PaulAlexander - I wonder if the resource interface could be generalized... if not then     (1I5AU)

supporting unique resource interfaces would be useful.     (1I5AV)

Natasha Noy: RE: Common logic: it is true though that our user interface is very much class-centric,     (1I5AW)

and so are our REST services. That's what *our* users needed. Adapting it to CL is definitely a     (1I5AX)

challenge as it is a very different view of ontologies.     (1I5AY)

Cameron Ross: @NatashaNoy - Thanks... I tend to agree.     (1I5AZ)

Simon Spero: Q: What do you mean by "SKOS-based"?     (1I5AAA)

Natasha Noy: @Simon SKOS-based: when we move to a triple store, we want to have a simple model for     (1I5AAB)

representing ontologies and terminologies, including things like preferred names, synonyms,     (1I5AAC)

definitions, etc. This will be a unifying layer among the different formats that we have. SKOS     (1I5AAD)

provides this layer, and we may need to extend it with a few additional properties     (1I5AAE)

Simon Spero: @NatashaNoy: So you just want to use it for labeling of ontologies, right?     (1I5AAF)

Natasha Noy: for labeling of ontology concepts, not ontologies themselves     (1I5AAG)

Simon Spero: @NatashaNoy: good - have had a lot of problems with people confusing the word     (1I5AAH)

butterfly with butterflies.     (1I5AAI)

Natasha Noy: @Simon: yes we have that model now as well. But it is a bit idiosyncratic. So, we want     (1I5AAJ)

something more thought-out and standards based for the next major version. SKOS is a perfect     (1I5AAK)

standard for that     (1I5AAL)

Paul Alexander: @Cameron: I'm not very familiar with common logic. If there are enough commonalities     (1I5AAM)

between CL and OWL/OBO/RRF it should be do-able. However, it would be a major change and require a     (1I5AAN)

significant amount of work to restructure all of the service signatures and XML responses (assuming     (1I5AAO)

you can't shoe-horn CL into the existing resource model).     (1I5AAP)

Cameron Ross: @PaulAlexander - The resource difference on the interface tier might be manageable, but     (1I5AAQ)

representing CL in a triple store would probably be futile.     (1I5AAR)

Natasha Noy: @Paul: Michael Grüninger looked at trying to shoe-horn CL into the class-centric model of     (1I5AAS)

BioPortal, and I think the conclusion was that it pretty much didn't work. CL is axiom-based and so     (1I5AAT)

it is a very different focus     (1I5AAU)

Paul Alexander: @Cameron: Sure, but there's nothing stopping running a different store alongside the     (1I5AAV)

triplestore. We very much respect OOP and already have our code handling different formats/stores.     (1I5AAW)

Very soon we'll have MySQL, LexEVS, Protege Server, and a triple store all running different parts     (1I5AAX)

of BioPortal.     (1I5AAY)

Natasha Noy: On CL: I think it is the UI that is more of a problem. Our UI is coompletely focused on     (1I5AAZ)

browsing classes and class hierarchies. My understanding is that it's pretty useless for CL     (1I5AAAA)

(Cameron, am I right?)     (1I5AAAB)

Cameron Ross: @NatashaNoy - I guess it depends on the CL theories you're considering, but in general,     (1I5AAAC)

I believe so.     (1I5AAAD)

Simon Spero: @ImmanuelNormann: Does using a version control repository that deals in files make     (1I5AAAE)

properly tracking provenance of assertions harder?     (1I5AAAF)

Simon Spero: @NastashaNoy: As long as you ignore the SKOS support for of Non-Transitive hierarchical     (1I5AAAG)

relations which was forced in due to butterfly/"butterfly" confusions     (1I5AAAH)

Natasha Noy: @Simon: not sure i understand     (1I5AAAI)

Simon Spero: @Natasha: SKOS was changed so that everything about Concept A is always also about     (1I5AAAJ)

Concept B, everything about Concept B is always also about Concept C. but it is possible for     (1I5AAAK)

something to be about Concept A but not about Concept C     (1I5AAAL)

Natasha Noy: Simon: Sorry, still confused. What is the relationship between concepts A, B, and C in     (1I5AAAM)

your example     (1I5AAAN)

Simon Spero: A broader B , B broader C     (1I5AAAO)

Natasha Noy: There are two "broader" properties in SKOS: one is transitive, one is not     (1I5AAAP)

Cameron Ross: @Immanuel - The general architecture I think you're proposing sounds very familiar to     (1I5AAAQ)

JohnSowa's Flexible Modular Framework for Intelligent Systems.     (1I5AAAR)

Simon Spero: @Natasha: yes - that was a bug introduced after the SMEs left     (1I5AAAS)

Natasha Noy: @Simon: Still don't see why this is a bug. As long as you choose the appropriate     (1I5AAAT)

broader property, you are ok, aren't you? There are cases for both of them, aren't there?     (1I5AAAU)

Simon Spero: @NatashaNoy: when you add the note that you're not supposed to assert the (traditional     (1I5AAAV)

KOS) BT relationship, which was called broader until 2004, but then renamed to broaderTransitive.     (1I5AAAW)

Simon Spero: @Natasha: can take off line     (1I5AAAX)

Simon Spero: To take this point further: a lot of the functionality being described generalizes     (1I5AAAY)

across all kinds of Repositories of Semantic data (not just repositories of Ontologies)     (1I5AAAZ)

Alan Rector: Apologies - I must go to catch a train     (1I5AAAAA)

Cameron Ross: @All - If we're talking about platform independence, then we should focus on the     (1I5AAAAB)

specification... +1     (1I5AAAAC)

Cameron Ross: @Ken - Are the non-functional requirements documented beyond the 2008 communique?     (1I5AAAAD)

Immanuel Normann: I absolutely agree with Cameron: we should focus on the specification ... and     (1I5AAAAE)

consider the BioPortal of one possible instance, satisfying this spacification to a certain extend     (1I5AAAAF)

Todd Schneider: Cameron, there has been little additional work on the requirements.     (1I5AAAAG)

anonymous morphed into Frank Olken     (1I5AAAAH)

Peter P. Yim: @Ken - ref. your slide#14 - the link to the "OOR Interface" doesn't seem to be active ...     (1I5AAAAJ)

please advise what the URL should be     (1I5AAAAK)

Ken Baclawski: Here is the link to the OOR Interface page:     (1I5AAAAL)

Cameron Ross: Re: CL - The BioPortal presentation tier, interface tier and persistence tier all     (1I5AAAAN)

require 'thought' for CL.     (1I5AAAAO)

Ken Baclawski: @Cameron I believe that they have, but I don't recall what the link is. Perhaps Peter     (1I5AAAAP)

could find this?     (1I5AAAAQ)

Peter P. Yim: @Cameron & Ken - ref. the question on non-functional requirements - the slides from Todd     (1I5AAAAR)

and Ken today are good ... some of those may also have been captured into the "OOR_Requirement" page     (1I5AAAAS)

Peter P. Yim: Key content pages for OOR are listed at:     (1I5AAAAU)

Cameron Ross: @PeterYim - Thanks Peter.     (1I5AAAAW)

Simon Spero: Isn't that orthogonal to federation?     (1I5AAAAX)

Peter P. Yim: @Simon - this conversation is going to be archived ... therefore, please provide some     (1I5AAAAY)

context when making a comment (otherwise it will not mean much to someone going through the archives)     (1I5AAAAZ)

Simon Spero: @PeterYim: (adding context) Isn't the issue of handling CL and OWL separate from     (1I5AAAAAA)

federation (which is more a distributed architecture)     (1I5AAAAAB)

Natasha Noy: sorry, will have to sign off in a couple of minutes     (1I5AAAAAC)

Peter P. Yim: @Todd and All - ref. an earlier presentation by Ken Baclawski and Máximo Gurméndez of NEU on     (1I5AAAAAD)

Quality and Gatekeeping Use Cases for the OOR at:     (1I5AAAAAE)

Todd Schneider: All, I'll need to leave this meeting at 13:45 EDT. Thanks to all presenters. Let's     (1I5AAAAAH)

Terry Longstreth: on provenance- not all artifacts will be necessarily be generated by individuals.     (1I5AAAAAJ)

Provenance tracking should include provisions for stowing identifiers for automated functions.     (1I5AAAAAK)

Simon Spero: [May I comment on the meta first]     (1I5AAAAAL)

Simon Spero: [on the multiple view problem the issue comes up when different viewers have different     (1I5AAAAAM)

sets of people who are willing to view for example Wiki/DBPedia timeliness v. reliability issues     (1I5AAAAAN)

Simon Spero: [reference to frame based]     (1I5AAAAAP)

Simon Spero: Q: Is there a BioPortal git repository right now, or is this currently proposed?     (1I5AAAAAQ)

Paul Alexander: @Simon: We're exploring migrating to Git, especially if there is a broader community     (1I5AAAAAR)

interested in participating using some of the tools out there that would seemingly enable easier     (1I5AAAAAS)

community development (like GitHub).     (1I5AAAAAT)

Paul Alexander: Re: Git. We would definitely love comments if people have opinions.     (1I5AAAAAU)

Simon Spero: Paul: git svn fetch works reasonably well     (1I5AAAAAV)

Paul Alexander: @Simon: One of the reasons we're considering switching is so we can more easily roll     (1I5AAAAAW)

changes that are being made back into our master repository. I don't think the svn-git conversion     (1I5AAAAAX)

would help us there.     (1I5AAAAAY)

Terry Longstreth: new term for me - 'git'. Can you explain or provide a URL?     (1I5AAAAAZ)

Simon Spero: @Paul: also git svn commit-diff and git patch     (1I5AAAAAAB)

Paul Alexander: Git is one of a number of solutions for a new paradigm for source control management     (1I5AAAAAAC)

where the code gets distributed rather than centralized in a single repository. Similar to SVN but     (1I5AAAAAAD)

Terry Longstreth: Thanks. Source code control is very complicated when your managing individual items     (1I5AAAAAAF)

(concepts, data elements...     (1I5AAAAAAG)

Peter P. Yim: can't hear you any more Immanuel     (1I5AAAAAAI)

Immanuel Normann: I lost telephone connection - don't know why - sorry     (1I5AAAAAAJ)

Immanuel Normann: My telephone seems to be broken - I will put my comments on the OOR mailing list -     (1I5AAAAAAK)

and leave the session now. Thanks and good bye!     (1I5AAAAAAL)

Cameron Ross: @Ken - What exactly is "the issue"... to be clear?     (1I5AAAAAAM)

Ken Baclawski: @Cameron regarding "the issue". I see the issue as being whether the fork should     (1I5AAAAAAN)

remain consistent with the BioPortal code base or should we diverge so that we would not be able to     (1I5AAAAAAO)

remain consistent with their code base.     (1I5AAAAAAP)

Cameron Ross: @All - I agree with Immanuel. We could really use Use Cases that describe the reasoning     (1I5AAAAAAQ)

related functionalities, as this is the part that seems to have more uncertainty associated with it.     (1I5AAAAAAR)

Cameron Ross: @Ken - Shouldn't we start with the "API" and not the implementation?     (1I5AAAAAAS)

Ken Baclawski: @Cameron - Yes, I think the discourse should be at the architecture and API level for now.     (1I5AAAAAAT)

Cameron Ross: @Ken - Great! I couldn't agree more.     (1I5AAAAAAU)

Peter P. Yim: @Ken - ref. the comment about robustness - it *is* an objective of the OOR initiative to     (1I5AAAAAAW)

provide (at least one instance of a) robust OOR ... therefore, we (the OOR-team) are not deferring     (1I5AAAAAAX)

that to "commercial enterprises"     (1I5AAAAAAY)

Ken Baclawski: @Peter re: robustness. I misspoke. The reference implementation must be robust. My     (1I5AAAAAAZ)

intention was to distinguish a reference implementation which has only the required functionality     (1I5AAAAAAAA)

from an "industrial-strength" implementation which has much more. In other words, the reference     (1I5AAAAAAAB)

implementation is only a starting point for other groups, whether they are open source or     (1I5AAAAAAAC)

Peter P. Yim: Please continue the conversation on the [oor-forum] & [oor-dev] list ... and come to the     (1I5AAAAAAAE)

next (and future) OOR-team meeting     (1I5AAAAAAAF)

Simon Spero: Good bye and good yomtov     (1I5AAAAAAAG)

Peter P. Yim: -- session ended: 11:03am PDT --     (1I5AAAAAAAI)

-- end of chat session --     (1I5AAAAAAAJ)

  • Further Question & Remarks - please post them to the [ oor-forum ] listserv     (1I5AAAAAAAK)
    • if you are already subscribed, post to <oor-forum [at]>     (1I5AAAAAAAK1)
    • (if you are not yet subscribed) you may subscribe yourself to the [ oor-forum ] listserv listserv, by sending a blank email to <oor-forum-join [at]> from your subscribing email address, and then follow the instructions you receive back from the mailing list system.     (1I5AAAAAAAK2)

Audio Recording of this Session     (1J)

  • suggestion: its best that you listen to the session while having the presentation opened in front of you. You'll be prompted to advance slides by the speaker.     (1J5)
  • Take a look, also, at the rich body of knowledge that this community has built together, over the years, by going through the archives of noteworthy past Ontolog events. (References on how to subscribe to our podcast can also be found there.)     (1J6)

For the record ...     (1J7)

How To Join (while the session is in progress)     (1K)

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