From OntologPSMW

Jump to: navigation, search
[ ]

Contents

Joint OpenOntologyRepository-OntologySummit2008 Panel Discussion Session - Thu 10-April-2008     (1)

  • Subject: Developing an Ontology of Ontologies for OOR     (1A)
  • Panelists:     (1C)
    • Professor MichaelGruninger (U of Toronto) - "A Framework for an Ontology of Ontologies"     (1C1)
    • Dr. PeterHaase (AIFB, U of Karlsruhe; Project NeOn) - "The OMV Ontology Metadata Vocabulary"     (1C2)
    • Dr. NatashaNoy (Stanford-BMIR) - "Ontology metadata in NCBO's BioPortal"     (1C3)
    • Ms. ElisaKendall (OMG; Sandpiper Software) - "Metadata Support for OMG's Emerging Ontology and Vocabulary Management Initiative"     (1C4)

  • Shared-screen support (VNC session) will be started 5 minutes before the call at: http://vnc2.cim3.net:5800/     (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 below and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1E5C)
  • Please note that this session will be recorded, and the audio archive, along with the entire proceedings of the session, are 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     (1F)

Background     (1H)

Two parallel initiatives are ongoing in the community, revolving around the theme of "Open Ontology Repository". On the one hand, a working group under the auspices of the OpenOntologyRepository Initiative, and on the other, the discourse (and essentially a discussion group that culminates in a two-day workshop) conducted as the main focus for OntologySummit2008.     (1H1)

It is at the intersection of these two initiatives that this panel discussion session is being held. The OpenOntologyRepository team is taking the opportunity to have some of its members who are bringing technology and infrastructure to the table to present them side-by-side, and to discuss how these can all fit nicely together. The Ontology Summit 2008 folks, on the other hand would want to take the opportunity to survey (at least a subset of) the technology & infrastructure landscape to gain insight into the state-of-art in Ontology Registry and Repository.     (1H2)

Besides hearing from the panelists, we are setting aside ample time after their briefings, for some good Q&A and discussions among all who are participating in this session.     (1H3)

Agenda & Proceedings     (1I)

  • This is the last of the four OOR-panel discussion sessions taht has been scheduled to explore various aspects of an "Open Ontology Repository (OOR)." In this session, the focus will be on the incorporation and development of an Ontology of Ontologies that would be of value (probably crucial) to an well designed and implemented OOR. Again, We are attemptig to bring together some of the world's top experts who has done related work to participate in this panel discussion sessions. Besides hearing from the panelists, we are setting aside ample time (~45 minutes) after their briefings, for some good Q&A and discussions among all who will be participating in this sessions.     (1I1)
  • Session Format: this is a virtual session conducted over an augmented conference call.     (1I2)

Topic: Developing an Ontology of Ontologies for OOR     (1J)

Panelists' Presentation Titles and Abstracts:     (1J1)

A Framework for an Ontology of Ontologies - MichaelGruninger     (1J2)

Under the appellation of "ontology" are found many different types of artifacts created and used in different communities to represent entities and their relationships for a wide range of purposes.The Ontology Summit 2007 "Ontology, Taxonomy, Folksonomy: Understanding the Distinctions," was an attempt to bring together various communities having a different understanding of what is an ontology, and to foster dialog and cooperation among these communities.     (1J2B)
The results of the Summit identified a limited number of key dimensions along which ontologies can be characterized and to provide operational definitions for these dimensions.     (1J2C)
This talk will give an overview of the framework that is constituted by these dimensions.     (1J2D)

The OMV Ontology Metadata Vocabulary - PeterHaase     (1J3)

In my presentation I will talk about OMV, a proposal for an Ontology     (1J3B)

Metadata Vocabulary that has been originally developed within the Knowledge Web project and is now maintained by the OMV consortium. I will explain the coverage and scope of OMV, some basic design rationales as well as applications. In particular, I will talk about uses and tool support for OMV developed in the NeOn project.     (1J3C)

Ontology metadata in NCBO's BioPortal - NatashaNoy     (1J4)

The National Center for Biomedical Ontology (NCBO; see http://bioontology.org) is developing BioPortal, an open-source repository of ontologies, terminologies, and thesauri of importance in biomedicine. BioPortal is accessible at http://bioportal.bioontology.org. Users can access the BioPortal content interactively via their Web browsers or programmatically via Web services. An alpha version of the next BioPortal release, which is available at http://alpha.bioontology.org supports facilities for visualizing ontologies, for creating mappings between ontologies, and for adding "marginal notes" through which the user community can comment on ontologies and discuss modeling decisions.     (1J4B)
I will discuss the metadata requirements for BioPortal and our approach for representing metadata about ontologies, maintaining the metadata as the ontologies evolve, and encouraging users to provide metadata both on the ontologies that they author and the ones that they use in their own projects.     (1J4C)

Metadata Support for OMG's Emerging Ontology and Vocabulary Management Initiative - ElisaKendall     (1J5)

As presented in EvanWallace's talk in the OOR-Panel Session (ConferenceCall_2008_03_27), the OMG is exploring what it would take to host a repository to manage standard ontologies and vocabularies. An initial request for information was issued at the recent OMG Technical Meeting in Washington, DC. (http://www.omg.org/cgi-bin/doc?ontology/08-03-02.pdf, Ontology and Vocabulary Management RFI). Searchable metadata is a critical aspect of this anticipated facility, and as such, we are actively investigating and seeking input on ontology management metadata.     (1J5B)
Potential starting points include, but are certainly not limited to: the OMV Ontology Metadata Vocabulary augmented via lessons learned in developing the BioPortal, current work in the ISO JTC1 SC32 WG2 effort to update the ISO 11179 Metadata Registry standard to include concept systems, vocabularies, and ontologies, and lessons learned in provenance and trust research by Dr. DeborahMcGuinness and her colleagues. I will briefly present some of the requirements and challenges we have identified for a successful ontology management capability at OMG, and look forward to active discussion and input from this community.     (1J5C)

( more details coming! ) - see: developing details     (1J5D)

Resources     (1J6)

Questions, Answers & Discourse     (1J7)

  • (Unless the conference host has already muted everyone) Please mute your phone, by pressing "*2" on your phone keypad, when the talk is in progress. To un-mute, press "*3"     (1J7A)
  • If you want to speak or have questions or remarks to make, please "raise your hand (virtually)" by pressing "11" on your phone keypad. You may speak when acknowledged by the speaker or the session moderator. Test your voice and introduce yourself first before proceeding with your remarks, please.     (1J7B)
  • You can also type in your questions or comments through the browser based chat session by:     (1J7C)
  • For those who have further questions or remarks on the topic, please post them to the [ontology-summit] forum so that everyone in the community can benefit from the discourse. (One needs to be subscribed to this archived mailing list first before posting. See subscription details here.)     (1J7D)

Questions and Discussion captured from the chat session     (1J8)

Peter P. Yim: Welcome to the Joint OpenOntologyRepository-OntologySummit2008 Panel Discussion Session - Thu 10-April-2008     (1J8A)

o Professor Barry Smith (NCOR; University at Buffalo) &     (1J8D)

o Professor Michael Grüninger (University of Toronto)     (1J8E)

o Professor Michael Grüninger (U of Toronto) - "A Framework for an Ontology of Ontologies"     (1J8G)

o Dr. Peter Haase (AIFB, U of Karlsruhe; Project NeOn) - "The OMV Ontology Metadata Vocabulary"     (1J8H)

o Dr. Natasha Noy (Stanford-BMIR) - "Ontology metadata in NCBO's BioPortal"     (1J8I)

o Ms. Elisa Kendall (OMG; Sandpiper Software) - "Metadata Support for OMG's Emerging Ontology and Vocabulary Management Initiative"     (1J8J)

Arturo Sanchez: Question for Michael Grüninger: why limit the formalisms used to express semantics to Model Theory (slide 9)?     (1J8K)

Arturo Sanchez: For Michael Grüninger and Peter Haase: how would you characterize OMV according to the     (1J8L)

Rex Brooks: For Michael Grüninger: Could we have some examples of Semi-Structured Ontologies?     (1J8N)

Rex Brooks: For Michael Grüninger: I would also like to have some examples of descriptive v. prescriptive     (1J8O)

ontologies, and how we can capture that in metadata, to avoid inadvertent misuse.     (1J8P)

John Graybeal: For Michael Grüninger: On slide 17, is it really the Design Methodology that you care about,     (1J8Q)

or the validation/review characteristics of the result? The important thing would seem to be     (1J8R)

whether an ontology has been established as consistent or conformant along various axes,     (1J8S)

not how it got to that state.     (1J8T)

Todd Schneider: In general we should assume we will not know all of the 'items' that will need to be     (1J8U)

represented in the metadata associated with an artifact and design for this.     (1J8V)

John Graybeal: For Michael Grüninger: The characterization of WordNet during slide 11 (Level of Structure)     (1J8W)

lost me a little, I'd like to hear that again. (An example table, showing how a number of     (1J8X)

ontologies fits into these various dimensions, would be quite helpful.)     (1J8Y)

and search for Population-spreadsheet, various ontologies where mapped to the model     (1J8AA)

during the summit     (1J8AB)

John Graybeal: For Arturo Sanchez: This is brilliant, though the copy I found is largely empty.     (1J8AC)

Where can I find one that integrates all the results?     (1J8AD)

Arturo Sanchez: For John Graybeal: if you look under "Breakout Group Task:" you will find the     (1J8AE)

various results from all the groups. In particular, the link to the document     (1J8AF)

Peter P. Yim (added subsequently): to John Graybeal: you can also look under     (1J8AH)

... check out the various breakout groups' work products as well as     (1J8AJ)

OlivierBodenreider's "Framework Dimensions Sorted" piece     (1J8AK)

Ken Baclawski: With one of my students, I have evaluated 40 large ontologies using the Ontology Summit 2007     (1J8AM)

Framework Dimensions. I have written up some conclusions about the results and could     (1J8AN)

present them at some point.     (1J8AO)

Rex Brooks: For Peter Haase: Small note on "Party," don't you think we need a category for "Agent"     (1J8AP)

which can be a subtype of either "Organisation" or "person," as well as a "party" in its     (1J8AQ)

own right, e.g. a spider/webcrawler bot?     (1J8AR)

Peter Haase: to Rex Brooks: I believe the concept Party captures what you propose as Agent     (1J8AS)

Peter Haase: we did not want to call it agent as the term is so overloaded     (1J8AT)

Rex Brooks: Thanks PeterHaase. It may require a qualifier or another term to be able to specify     (1J8AU)

the Party as some kind of software agent v. an organisation or person. I will need     (1J8AV)

to take a good look at OMV.     (1J8AW)

Mala Mehrotra: For Natasha Noy: Are the mappings being stored as metadata? Slide 5.     (1J8AX)

Natasha Noy: For Mala Mehrotra: Yes, mappings are also metadata (and have the same issues,     (1J8AY)

such as versioning, contributions from communities, etc.)     (1J8AZ)

Mala Mehrotra: For Natasha Noy: SO what language - or what level of expressivity - are you     (1J8AAA)

all requiring in the BioPortal for mappings?     (1J8AAB)

Arturo Sanchez: For Natasha Noy: what is the definition of "validity"? without a formal definition     (1J8AAC)

it is not possible to check for such property ...     (1J8AAD)

Arturo Sanchez: For Natasha Noy: so, by allowing ontology versioning by creating brand new ontologies     (1J8AAE)

from existing ones, that means interoperability among versions might not be possible     (1J8AAF)

... any comments?     (1J8AAG)

John Graybeal: Awesome lineup, Peter. Must leave now, will catch up later.     (1J8AAH)

Todd Schneider: For Peter Haase: Does OMV support a distributed structure (e.g. P2P)?     (1J8AAI)

Rex Brooks: For Peter Haase: Would OMV be capable of being used as a "Classification Scheme"     (1J8AAJ)

in ebXML RIM, if you happen to know?     (1J8AAK)

Peter Haase: to Rex Brooks: The OMV API for the registry that I mentioned is actually an     (1J8AAL)

"OMV Specialized ebXML Registry"     (1J8AAM)

Peter Haase: so we used the extension mechanisms of ebXML     (1J8AAN)

Rex Brooks: Thanks Peter Haase, that is terrific for the groups I work with.     (1J8AAO)

Peter Haase: we have P2P-like applications that make use of OMV and have a P2P extension to describe     (1J8AAP)

the peers, but there is nothing P2P specific in OMV itself     (1J8AAQ)

Peter Haase: what kind of structures were you thinking about?     (1J8AAR)

Peter Haase: regarding the ebXML registry, you may want to look at " D6.4.1: Realisation &     (1J8AAS)

early evaluation of NeOn service-oriented registry and repository " under     (1J8AAT)

Peter Haase: what we also do have is the separation between logical identifiers of     (1J8AAV)

ontologies (ontology URI) and their physical location, this can be used to support     (1J8AAW)

replication and caching     (1J8AAX)

Todd Schneider: To Peter Haase: In that case (i.e. the ontologies are maintained locally),     (1J8AAY)

is OMV being used more for a registry? If so, can there be multiple registries     (1J8AAZ)

(i.e.distributed)? For example, different COP's maintaining their own 'instances'     (1J8AAAA)

of thier OMV registry for their domain/COP.     (1J8AAAB)

Peter Haase: yes, we have both registries and repositories using OMV. They can be distributed,     (1J8AAAC)

in fact, the Oyster system I mentioned is such a distributed system     (1J8AAAD)

Peter Haase: it also supports the propagation and synchronization of the metadata     (1J8AAAE)

Rex Brooks: To all panelists: This is really terrrific as the groups I work with head directly     (1J8AAAF)

into building registry-repositories and ontologies. Thanks All!     (1J8AAAG)

Rex Brooks: My question is for Peter Haase: Could you elaborate on the difference, with examples,     (1J8AAAH)

if you can, between prescriptive and descriptive ontologies?     (1J8AAAI)

Peter Haase: I am afraid I cannot, Michael Grüninger brought this distinction up, perhaps he can     (1J8AAAJ)

better answer [--ed. which Michael Grüninger did answer to verbally. Refer to the audio archive.]     (1J8AAAK)

Evan Wallace: I don't understand this distinction in this context.     (1J8AAAL)

Ann Wrightson: I'm uncomfortable with the use of "structured" to apparently mean "logically clean".     (1J8AAAM)

Surely these are different notions? An "unstructured" ontology in the expression-sense     (1J8AAAN)

stated in slide 11 could have in fact a considerable amount of structure in the usual sense     (1J8AAAO)

of the word (eg follow a component-assembly-structure defined in EXPRESS)     (1J8AAAP)

[--ed. which Michael Grüninger did answer this verbally when Ann Wrightson posed the     (1J8AAAQ)

question again (below). Refer to the audio archive.]     (1J8AAAR)

Ann Wrightson: My question: To Michael Grüninger, regarding Structure. I'm thinking in particular of     (1J8AAAS)

the HL7v3 RIM (Reference Information Model) that is used as a theory-of-what-there-is     (1J8AAAT)

(a semi-formal upper ontology) to both describe and prescribe the kinds of things     (1J8AAAU)

can be said in a largish family of derivative standards. The RIM has internal structure,     (1J8AAAV)

and the related set of standards has structure (that could be expressed eg using     (1J8AAAW)

STEP concepts). How would/should this kind of structure be handled in our dialogue,     (1J8AAAX)

distinct from the quality of being "structured" that is present in MichaelGruninger's slide 11?     (1J8AAAY)

Evan Wallace: For some content in some ontology language forms, some metadata could be     (1J8AAAZ)

Evan Wallace: automatically generated (DL expressivity, satisfiability, etc.).     (1J8AAAAA)

Evan Wallace: I believe that some OMV tools do this already for OWL DL ontologies.     (1J8AAAAB)

Peter Haase: yes, this is what e.g. Watson does, it generates/extracts most metadata automatically     (1J8AAAAC)

Evan Wallace: Peter Haase: Does OMV or Watson provide any support for Common Logic or some other FOL form?     (1J8AAAAD)

Peter Haase: in principle it can capture metadata about ontologies in any ontology language     (1J8AAAAE)

Ann Wrightson: Following on from the response just now, and thinking back to the NASA presentation     (1J8AAAAF)

on ConferenceCall_2008_03_20: though we shouldn't expect the OOR to provide or perform     (1J8AAAAG)

configuration management of ontologies, I guess there should be guidance concerning     (1J8AAAAH)

provision of versioning infomration that will support users who want to reuse ontologies     (1J8AAAAI)

within a strong configuration management or product line development environment.     (1J8AAAAJ)

Chaim Zins: Just a short remark: We need to diferentiate between the topic "Ontology of ontologies"     (1J8AAAAK)

and metadata issues related to the field of ontology study.     (1J8AAAAL)

[--ed. to which Barry Smith did answer, verbally. Refer to the audio archive.]     (1J8AAAAM)

Arturo Sanchez: For Peter Haase: Good point ... so, metadata management is informed (so to say) by     (1J8AAAAN)

the semantics of your model, using which concepts such as "validity", "extensions",     (1J8AAAAO)

"editing", "refinement" can be equally formally defined (in theory, at least ) Thanks.     (1J8AAAAP)

Todd Schneider: To Barry Smith: Perhaps we need a variant or sub-repository of the Open Repository that     (1J8AAAAQ)

would support a peer review process to meet higher quality standards?     (1J8AAAAR)

Peter Haase: to Arturo Sanchez: yes, in theory and to some extent already in practice     (1J8AAAAS)

Chaim Zins: I agree with your remark.     (1J8AAAAT)

Evan Wallace: BarrySmith's comment just underlines my opinion that the term Ontology     (1J8AAAAU)

Chaim Zins: The first question is "what is ontology?"     (1J8AAAAV)

Evan Wallace: of Ontologies is not a good term for describing ontology metadata needed for a repository.     (1J8AAAAW)

Evan Wallace: Cute terms are great for slideset titles but bad for describing discussion topics.     (1J8AAAAX)

Arturo Sanchez: Ontology of Ontologies in this context is: using the metadata approach to represent the     (1J8AAAAY)

knowledge about ontologies. Therefore, applications will be inherently limited by the models     (1J8AAAAZ)

used to characterized ontologies. For instance, consider the example for which the ontology     (1J8AAAAAA)

used to characterize ontologies in the repository has less "expressive power" than ontologies     (1J8AAAAAB)

it is trying to define     (1J8AAAAAC)

Michelle Raymond: Ann Wrightson mentions that (paraphased) 'in product line development environments     (1J8AAAAAD)

strong configuration management is required.' Currently, there are industry product     (1J8AAAAAE)

providers that very much MUST point to the exact ontology AND the associated metadata     (1J8AAAAAF)

for that ontologies when providing a product release. To do this now, sometimes     (1J8AAAAAG)

the "real" standard can't be linked in, as there is concern that it has remained static     (1J8AAAAAH)

or at least a needed level of consistency. Thus, the vendor includes a copy of     (1J8AAAAAI)

the ontology and associated metadata, files, documents and the like in their     (1J8AAAAAJ)

product release and does not encourage customers to visit the "real" source. This can be     (1J8AAAAAK)

a legal issue of "fair use" when a copy is made. It is also disassociating the product     (1J8AAAAAL)

from the further value potentially available in the "real" ontology and the repository     (1J8AAAAAM)

that holds it. I believe we need to address this issue both in firm rules that SHALL NOT     (1J8AAAAAN)

allow revision of a "status-final" ontology and that we must further consider requiring     (1J8AAAAAO)

some meta-data associated with an ontology as also being "status=final." Comments about     (1J8AAAAAP)

my statements are very much desired as is turning this into a conversational thread.     (1J8AAAAAQ)

Evan Wallace: We should start a thread about versioning on one of the email lists which captures both     (1J8AAAAAR)

AnnWrightson's and MichelleRaymond's comments on today's chat session. Would one of you     (1J8AAAAAS)

do it or should I?     (1J8AAAAAT)

Audio Recording of this Session     (1K)

Join us at the Ontology Summit 2008 workshop, April 28~29, 2008; either on-site at NIST, Gaithersburg, Maryland, USA or participate remotely! - see deails here.     (1K7)


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