1 / 12

Integration of HL7 Security and Privacy Ontology with Other Ontologies

Integration of HL7 Security and Privacy Ontology with Other Ontologies. Tony Weida. Kinds of Ontologies (Guarino, 1998). Top-level ontology. domain ontology. task ontology. application ontology. What’s an Upper Ontology?.

dagmar
Download Presentation

Integration of HL7 Security and Privacy Ontology with Other Ontologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integration ofHL7 Security and Privacy Ontologywith Other Ontologies Tony Weida

  2. Kinds of Ontologies (Guarino, 1998) Top-level ontology domain ontology task ontology application ontology

  3. What’s an Upper Ontology? • An upper ontology (or foundation ontology) is a model of the common objects that are generally applicable across a wide range of domain ontologies. [Wikipedia]

  4. Upper Ontologies • Many candidates • Examples include BFO, Cyc, DOLCE, GFO, UMBEL, SUMO, etc. • Significant variation • No consensus choice • Practical value is debatable

  5. BFO 1.1 (current version) “BFO, the Basic Formal Ontology, is an upper level ontology that grew out of a philosophical orientation … narrowly focused on the task of providing a genuine upper ontology which can be used in support of domain ontologies developed for scientific research, as for example in biomedicine …”

  6. Adopting an Upper Ontology • HL7 Security and Privacy Ontology (“SPO”) • Upper level ontology (“Upper”) • How to integrate them? Upper ? SPO

  7. OWL Import • Think of an OWL ontology as a “box” which can include classes, properties, etc. • An ontology can import other ontologies, i.e., their entire contents • Imported entities can be restricted, including relations to each other and/or to local entities • Flexible assembly

  8. Option: Embedding an Upper Ontology • Tight coupling • Strong commitment to one upper ontology • Specific choice (BFO, SUMO, Dolce, etc.) • Fixed version (e.g., BFO 1.1) • Must be done up front • Must be normative part of SPO • Makes SPO inherently more complex SPO BFO 1.1

  9. Option: Federating with an Upper Ontology • Third ontology for combination (“Combo”) • Loose coupling • No change to SPO • Allows separate combinations with various upper ontologies • Flexible choices • Flexible versions (e.g., forthcoming BFO 2.0) • Can be done later • Need not be normative part of SPO • Simplifies SPO Combo Combo 2 BFO 1.1 BFO 2.0 SPO SPO Essentially similar points for integration with SOA Ontology, etc.

  10. Recommendations • Others can federate the HL7 SPO with other ontologies if and when they see fit • Especially considering limited time and resources, HL7 should not integrate the SPO with other ontologies at this time

  11. Note: Federated Sub-Ontologies • Overall SPO is composed of modular sub-ontologies • Base • SecurityAndPrivacyOntology.owl • Multiple extensions • ConfidentialityOntology.owl • SensitivityOntology.owl • … • The sub-ontologies are federated using OWL imports SPO Confidentiality Sensitivity …

  12. Discussion

More Related