ontologies skos
play

Ontologies SKOS Metadata Resources marked-up with descriptions of - PowerPoint PPT Presentation

Ontologies SKOS Metadata Resources marked-up with descriptions of their content. No good unless everyone speaks the same language ; Terminologies COMP62342 Provide shared and common vocabularies of a domain, so Sean Bechhofer


  1. Ontologies SKOS • Metadata – Resources marked-up with descriptions of their content. No good unless everyone speaks the same language ; • Terminologies COMP62342 – Provide shared and common vocabularies of a domain, so Sean Bechhofer search engines, agents, authors and users can communicate. sean.bechhofer@manchester.ac.uk No good unless everyone means the same thing ; • Ontologies – Provide a shared and common understanding of a domain that can be communicated across people and applications, and will play a major role in supporting information exchange and discovery. 2

  2. Ontology A Spectrum of Representation • A representation of the shared background knowledge for a community Formal Value • Providing the intended meaning of a formal vocabulary used is-a Restrictions Thesauri Catalogue to describe a certain conceptualisation of objects in a domain of interest Expressive Terms/ Informal Frames • A vocabulary of terms plus explicit characterisations of the Logics glossary is-a assumptions made in interpreting those terms • Nearly always includes some notion of hierarchical classification (is-a) • Formal representations are not always the most appropriate for • Richer languages allow the definition of classes through applications description of their characteristics 3 4

  3. COHSE COHSE’s Architecture • Conceptual driven navigation around documents • Simple text processing + vocabulary + open hypermedia HTML architecture Document in Ontology – Separating link and document Knowledge Service – Explicit navigation around a � SKOS domain vocabulary DLS Agent Search Resource Engine Service • DLS agent adds links to � documents based on the � Linked HTML Document out occurrence of concepts in � Annotation DB those documents. 5 6

  4. Demo Generic Links • Generic Links in Open Hypermedia are based on words. Linkbase Link Service Document Linked Document 7 8

  5. Generic Links + Thesaurus Generic Links + Ontology • A thesaurus can bridge gaps between terms. • An ontology can bridge gaps between concepts. Thesaurus Linkbase Ontology Linkbase Link Service Link Service Document Linked Document Linked Document Document 9 10

  6. Reflection SKOS • Our original approach involved the use of OWL ontologies to • SKOS : Simple Knowledge Organisation Scheme support the conceptual models. • Used to represent term lists, controlled vocabularies and • Over time, we came to see this as a “mistake” -- looser thesauri vocabularies were perhaps more appropriate. • Lexical labelling • The timely appearance of SKOS…. • Simple broader/narrower hierarchies (with no formal semantics) • W3C Recommendation http://www.flickr.com/photos/buildscharacter/443708336/ S. Bechhofer, Y. Yesilada, R. Stevens, S. Jupp, and B. Horan. Using Ontologies and Vocabularies for Dynamic Linking IEEE Internet Computing 12(3), p. 32--39 2008 http://dx.doi.org/10.1109/MIC.2008.68 11 12

  7. Primary Use Cases/Scenarios SKOS Goals A. Single controlled vocabulary used to index and then retrieve • to provide a simple , machine-understandable , representation framework for Knowledge Organisation Systems (KOS)… � objects • Query/retrieval may make use of some structure in the • that has the flexibility and extensibility to cope with the vocabulary variation found in KOS idioms… � B. Different controlled vocabularies used to index and retrieve objects • that is fully capable of supporting the publication and use of • Mappings required between the vocabularies KOS within a decentralised , distributed , information environment such as the world wide (semantic) web. • Also other possible uses (e.g. navigation) 13 14

  8. SKOS Concept Schemes • A model for expressing basic structure of “ concept schemes ” • A concept scheme is a set of concepts, potentially including statements about relationships between those concepts • Thesauri, classification schemes, taxonomies and other controlled vocabularies – Semantic Relationships – Many of these already exist and are in use in cultural • Broader/Narrower Terms heritage, library sciences, medicine etc. • Related Terms – A wide range of knowledge sources that can potentially – Lexical Labels provide value for Semantic Web applications • Preferred, alternative and hidden labels • SKOS aims to provide an RDF vocabulary for the – Additional documentation representation of such schemes. • Notes, comments, descriptions – A migration path bringing such resources “into the Semantic Web”. 15 16

  9. Knowledge Organisation Term Based vs Concept Based Thesaurus : Controlled vocabulary in which concepts are represented by preferred terms, formally organised so that paradigmatic relationships • SKOS adopts a concept-based (as opposed to term-based) between the concepts are made explicit, and the preferred terms are approach accompanied by lead-in entries for synonyms or quasi-synonyms. Thesaurus Related Terms Taxonomy Hierarchy Authority File Preferred Terms Synonym Ring Equivalent Terms • Concepts associated with lexical labels Controlled Vocabulary Collection of Terms • Relationships expressed between concepts. – Possibility of expressing relationships between terms Controlled vocabularies : designed for use in classifying or through SKOS-XL. indexing documents and for searching them. 17 18

  10. SKOS Example SKOS Example animals NT cats cats UF domestic cats RT wildcats BT animals SN used only for domestic cats domestic cats USE cats wildcats 19 20

  11. SKOS Semantic Relations SKOS and OWL • Hierarchical and Associative • SKOS and OWL are intended for different (but related) purposes • Broader/Narrower • SKOS Concept schemes are not formal ontologies in the way • Loose (i.e. no) semantics that, e.g. OWL ontologies are formal ontologies. – A publishing vehicle, not a set of 
 • There is no formal semantics given for the conceptual thesaurus construction guidelines hierarchies (broader/narrower)represented in SKOS. • Domain/Range restrictions on semantic relations • Contrast with OWL subclass hierarchies which have a formal • Broader/Narrower not transitive in SKOS interpretation (in terms of sets of instances). – But transitive super property – Recall partonomic discussions! • A weaker ontological commitment . 21 22

  12. Ontological Commitment SKOS and OWL • SKOS Concepts not intended for instantiation in the same way that OWL Classes are instantiated An ontology should require the minimal ontological – Leo is an instance of Lion commitment sufficient to support the intended – Born Free is a book about Lions knowledge sharing activities. An ontology should make as • Concept Schemes allow us to capture general statements about things that few claims as possible about the world being modeled, aren’t necessarily strictly true of everything allowing the parties committed to the ontology freedom – It’s useful to be able to navigate from Cell to Nucleus, even though it’s to specialize and instantiate the ontology as needed. not the case that all Cells have a Nucleus – Relationships between Polio and Polio virus, Polio vaccine, Polio disease… Gruber – Relationships between Accident and Accident Prevention, Accidents in the Home, Radiation Accidents… • But we can’t necessarily draw the same kinds of inferences about SKOS • SKOS captures the basic, informal semantics most commonly hierarchies. required by the use cases. – Broader hierarchy is not transitive. • Although mechanisms are available which allow us to query the transitive closure of the hierarchy. 23 24

  13. SKOS and OWL Annotation in OWL • SKOS itself is defined as an OWL ontology. • OWL data and object properties allow us to define the characteristics of classes • A particular SKOS vocabulary is an instantiation of that ontology/schema – Necessary/sufficient conditions etc. – E.g. SKOS Concept is a Class, particular concepts are – Model theory/semantics provides interpretations of the instances of that class assertions involving the properties • Allows us to use some of the mechanisms of OWL to define • Ontology engineering (and use) also requires annotation properties of SKOS (e.g. the querying of the transitive closure – Decoration of concepts/properties/individuals with of broader). information which is useful, but does not impact on the • Allows us to use generic tooling to construct/maintain our formal semantics or logical interpretations vocabularies • Separation of the concept from its concrete label is usually seen as a Good Thing. 25 26

  14. Annotation SKOS as Annotation • Annotations do not impact on the formal semantics or logical • SKOS labelling and documentation properties are defined as interpretations OWL Annotation Properties • Thus they are “opaque” to a reasoner. – Preferred/Alternate/Hidden Labels • But still useful for both humans and application – Documentation/Notes Application Specific General • SKOS then provides a standardised vocabulary for annotating • Labels • Entry points for forms OWL ontologies – Human readable • Driving User interaction • Leverage existing tooling. • Textual Definitions • Syntax round-tripping – OWL API – Scope notes • Hiding engineering aspects of – Protégé • DC style metadata the model – authorship • Methodological support, e.g. • Change History OntoClean • Provenance information 27 28

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend