OpenOntologyRepository: Metadata Workshop-IV - Tue 2011_10_18    (2XW0)

Topic: OOR Metadata Workshop-IV    (2XX3)

Session Chair: MichaelGruninger    (2XX4)

Archives:    (2Y20)

Conference Call Details:    (2XW1)

Attendees    (2XWO)

Agenda Ideas:    (2XWY)

please insert any additional items below (along with your name for follow-up purposes)    (2XWZ)

References:    (2Y2E)

Agenda & Proceedings    (2XX1)

1. Meeting called to order:    (2Y2R)

2. Roll Call:    (2Y2V)

3. Key items for review and discussion today:    (2Y31)

3.1 Opening: - by MichaelGruninger    (2Y32)

Today's (2011.10.18) agenda:    (2Y33)

3.2 Discussion:    (2Y37)

3.3 IM Chat Transcript captured during the session:    (2Y3B)

 see raw transcript here.    (2Y3C)
 (for better clarity, the version below is a re-organized and lightly edited chat-transcript.)
 Participants are welcome to make light edits to their own contributions as they see fit.    (2Y3D)
 -- begin in-session chat-transcript --    (2Y3E)
	PeterYim: Welcome to the    (2Y6R)
	 = open ontology repository (oor) session - tue 2011_10_18 =    (2Y6S)
	Topic: OOR Metadata Workshop-IV    (2Y6T)
	Session Chair: MichaelGruninger    (2Y6U)
	Session page:    (2Y6V)
	 == proceedings: ==    (2Y6W)
	anonymous morphed into TimWilson    (2Y6X)
	TimWilson: Hi, this is Tim Wilson.  I am having work done in my basement, it is very noisy.    (2Y6Y)
	MichaelGruninger: I am having trouble connecting by phone    (2Y6Z)
	Tim Darr: Joining ...    (2Y70)
	PeterYim: are you trying to connect via skype?    (2Y71)
	PeterYim: Michael got in!    (2Y72)
	ToddSchneider: Michael, What's a 'module'?    (2Y73)
	anonymous morphed into NikkiaAnderson    (2Y74)
	anonymous morphed into AliHashemi    (2Y75)
	ToddSchneider / MichaelGruninger: Manchester's TONES repository -    (2Y76)
	MichaelGruninger: how ontologies relate to one another elevates OOR from being 
        "just a library of ontologies" (e.g. if you look at TONES from Manchester, that 
        is a large list of ontologies with no interaction between them)    (2Y77)
	AliHashemi: Scenario:
	Ontology O1 in OWL (in OOR)
	Ontology O2 in CL (not in OOR)
	Ontology O3 in CL (in OOR) <-- (previously: "ORR" - typo corrected)    (2Y78)
	Declare in OMV:
	O3 hasImport O1
	O3 hasImport O2
	O1 hasLanguage OWL
	O2 hasLanguage CL
	O3 hasLanguage CL    (2Y79)
	--- ---    (2Y7A)
	AliHashemi: ORR is a typo meant OOR    (2Y7B)
	TimWilson: At my work, ORR is Operational Readiness Review.    (2Y7C)
	PeterYim: There is actually an "ORR" - the MMI project's Ontology Registry and Repository 
        (which is also BioPortal based) - see:    (2Y7D)
	If ontologies are located externally to OOR
	How to handle this in a workflow tool?    (2Y7E)
	Speak to a need to differentiate between Ontologies that are registered 
       (and axioms are available on OOR)    (2Y7F)
	MichaelGruninger: Using the notion of importing ontologies, there will exist 
        a set of ontologies that are imported by other ontologies but which do not themselves 
        import any others. Such ontologies would be "building block" modules, and we would 
        require them to be registered in the repository.    (2Y7G)
	AliHashemi: hasImport --> useImports*    (2Y7H)
	TimWilson: (Very interesting discussion, but I need to go.)    (2Y7I)
	TerryLongstreth: The notion of imports entrains a responsibility on the part of the OOR services to validate the imported items    (2Y7J)
	TerryLongstreth: Once validated, the imported ontology module is presumed to be an invariant    (2Y7K)
	ToddSchneider: OOR will automatically parse import statements and check for 
        the presence of the ontologies to be imported in OORs.    (2Y7L)
	ToddSchneider: Terry, invariant? With respect to what?    (2Y7M)
	TerryLongstreth: With respect to the importing object    (2Y7N)
	AliHashemi: If you're building services in the OOR to exploit elements of an ontology, 
        if it is not in (or transparent to) the system you can't really deploy the services    (2Y7O)
	TerryLongstreth: If the imported, validated module can change, than everything that 
        imports it can be invalidated    (2Y7P)
	AliHashemi: (I've got to run. Bye.)    (2Y7Q)
	TerryLongstreth: some arbitrary time in the future    (2Y7R)
	ToddSchneider: (Sorry, but have to go.)    (2Y7S)
	MichaelGruninger: How does BioPortal capture the notion of different ontology versions and the possibility of new  versions being used which are not part of BioPortal?    (2Y7T)
	TerryLongstreth: How does Bioportal reflect changes in semantics of medical ideas?    (2Y7U)
	KenBaclawski: There are two different notions of import.  One can import an ontology with 
        no specification of which version is being imported.  One could also have a strict import 
        that requires the imported ontology to be a specific version.  One can enforce 
        a strict import by specifying a checksum.    (2Y7V)
	MichaelGruninger: Find examples within BioPortal of one ontology importing another ontology, 
        either internal or external to BioPortal    (2Y7W)
	PeterYim: MichaelGruninger: at the next workshop, we can put some focus on "versioning"    (2Y7X)
	MichaelGruninger: Action Item (for everyone): find papers on ontology versioning    (2Y7Y)
	PeterYim: -- session ended: 10:05 am PDT --    (2Y7Z)
 -- end of in-session chat-transcript --    (2Y3F)

4. Any Other Business:    (2Y3G)

5. Action items:    (2Y3H)

6. Schedule Next Meeting & Adjourn:    (2Y3I)

 notes taken by: PeterYim / 2011.10.18-10:16am PDT
 All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.    (2Y3P)

Resources    (2XX2)