Bell Labs
Renon Route
Bell Labs

Challenges for OWL 1.1

Peter F. Patel-Schneider, Bell Labs Research

Copyright © 2008 Bell Labs

OWL 1.1 is an update to OWL DL and is currently being considered by W3C for incorporation into a new W3C version of OWL. The original OWL was the result of a number of compromises and non-compromises between differing views of Knowledge Representation and the Semantic Web. OWL 1.1 takes differing stances on some of the issues underlying OWL, resulting in a need for rethinking the some of the design for the new OWL. In this talk, I will present the issues that underlie OWL and OWL 1.1 and present my views on how the should be resolved in the new W3C version of OWL.

What is OWL?


OWL

OWL Ontology Fragment


(Protégé 4 (a.k.a. Manchester) syntax)

Namespace: = <http://ex.com/owl/families#> Ontology: <http://ex.com/owl/families> Import: <http://ex2.com/owl/family.owl>   ObjectProperty: hasWife Annotations: rdfs:label "moglie"@it Domain: Man Range: Woman Characteristics: Functional, Inverse Functional SubPropertyOf: hasSpouse, loves ObjectProperty: hasChild Domain: Person Range: Person SubPropertyOf: inverse hasAncestor ObjectProperty: hasAncestor Characteristics: Transitive DataProperty: hasAge Domain: Person Range: integer Characteristics: Functional   Class: Person SubClassOf: hasAge exactly 1 and hasGender exactly 1 and hasGender only {female , male} Class: Man EquivalentTo: Person that hasGender value male Class: Parent EquivalentTo: Person that hasChild min 1 Class: YoungChild EquivalentTo: Person and not (Teenager or Adult)   Individual: Jeff Types: hasChild exactly 2 Facts: hasWife Emily, hasChild Ellen, hasChild Jack, hasAge 77, loves Jeff DifferentFrom: Ellen, Jack, Susan, Emily   Individual: Emily Types: hasAge some {39 , 49}

Influences on OWL


The Easy Part


The Hard Part


RDF vs Description Logics


Users vs Tools


OWL: A Grand Compromise


OWL: Ugly Underpinnings


Time Marches On


OWL 1.1


OWL 1.1 Ontology Fragment


ObjectProperty: hasWife Characteristics: Irreflexive, AntiSymmetric ObjectProperty: hasDaughter Domain: Parent Range: Person that hasGender value female SubPropertyOf: hasChild SuperPropertyOfChain: f:hasSpouse o f:hasDaughter ObjectProperty: hasSon Domain: Parent Range: Person that hasGender value male SubPropertyOf: hasChild DisjointWith: hasDaughter   Class: Adult Annotations: rdfs:label "adulto"@it EquivalentTo: Annotations: rdfs:comment "This is a rather crude definition of adult" Person that hasAge some integer[>= 21]   Class: Teenager EquivalentTo: Person that hasAge some integer[>= 13 , < 20] Class: Narcissist EquivalentTo: Person that loves Self   Individual: Jeff Types: hasChild exactly 2 Teenager Individual: Ellen Types: hasAge some integer[>= 15 , <= 19] Individual: Jack Facts: not hasAge "53"^^integer  

W3C OWL WG


Working group home page, http://www.w3.org/2007/OWL/wiki/OWL_Working_Group

Should be easy!

OWL WG Activities


OWL WG Activities (continued)


Sources of Controversy


Several views of OWL and OWL 1.1:

  1. OWL is an ontology language very close to Description Logics.
    1. OWL Full is just something required to get W3C approval.
    2. Semantic Web orientation is just something required to get W3C approval.
  2. OWL is a powerful extension of RDFS.
    • OWL DL is just one of many fragments of OWL.
  3. The real Web Ontology Language is RDFS plus functional properties (and maybe a bit of other stuff).
    • OWL DL is a theoretical language and not ready to be used in real applications, and OWL Full just shows a potential way forward for when tools get faster.
  4. Every feature of OWL must be preserved, OWL 1.1 can only add a little bit vs OWL 1.1 should fix the broken parts of OWL.

How to Proceed


  1. Remove OWL DL and OWL 1.1 from the official Semantic Web, terminating the uneasy relationship between OWL DL and OWL Full.
    1. W3C Web Ontology Language becomes OWL Full; or
    2. W3C Web Ontology Language becomes RDFS++.
  2. Go back to the previous syntaxes and relationship to OWL Full.
    • Requires eliminating new annotations and not translating metamodelling, at least.
    • Can add new restrictions, new characteristics of properties, and role chain inclusions.
  3. Relegate OWL Full to the ashcan of technology, where it belongs.
  4. Use solution proposed (implicitly) in OWL 1.1.
    • All OWL 1.1 constructs remain.
    • Annotations have no meaning in OWL 1.1.
    • New syntax for OWL 1.1.
    • Deprecate deprecation and ontology properties.
    • Better translation into RDF (and OWL Full).
    • Similar (but not exactly the same) relationship to OWL Full.

Example OWL Ontology (Complete)


Namespace: =<http://ex.com/owl/families#> Namespace: g = <http://ex2.com/owl/family.owl#> Namespace: families = <http://ex.com/owl/families#> Namespace: rdfs = <http://www.w3.org/2000/01/rdf-schema#> Namespace: rdf = <http://www.w3.org/1999/02/22-rdf-syntax-ns#>   Ontology: <http://ex.com/owl/families>   Import: <http://ex2.com/owl/family.owl>   ObjectProperty: hasWife Domain: Person, Man Range: Person, Woman Characteristics: Functional, Inverse Functional, Irreflexive, AntiSymmetric SubPropertyOf: hasSpouse, loves   ObjectProperty: hasHusband Inverses: hasWife   ObjectProperty: hasSon Domain: Person, Parent Range: Person, Person that hasGender value male SubPropertyOf: hasChild DisjointWith: hasDaughter   SubObjectProperty: f:hasSpouse o f:hasSon f:hasSon **   ObjectProperty: hasDaughter Domain: Person, Parent Range: Person, Person that hasGender value female SubPropertyOf: hasChild   SubObjectProperty: f:hasSpouse o f:hasDaughter f:hasDaughter **   ObjectProperty: hasGender   ObjectProperty: hasChild Domain: Person Range: Person SubPropertyOf: **INVERSEOF** hasAncestor   ObjectProperty: hasAncestor Characteristics: Transitive, Irreflexive   ObjectProperty: hasSpouse Characteristics: Symmetric, Irreflexive   ObjectProperty: loves Domain: Person   DataProperty: hasAge Domain: Person Range: integer Characteristics: Functional   Class: Person SubClassOf: hasAge exactly 1 and hasGender exactly 1 and hasGender only ({female , male})   Class: Man EquivalentTo: Person that hasGender value male   Class: Woman EquivalentTo: Person that hasGender value female   Class: Parent EquivalentTo: Person that hasChild min 1 Class: Teenager EquivalentTo: Person that hasAge some integer[>= 13 , < 20]   Class: Adult EquivalentTo: Person that hasAge some integer[>= 21]   Class: Child EquivalentTo: Person and not (hasAge some integer[>= 21])   Class: YoungChild EquivalentTo: Person and not (Teenager or Adult)   Class: Marriage EquivalentTo: CivilMarriage or ReligiousMarriage   Class: ReligiousMarriage DisjointWith: CivilMarriage   Class: CivilMarriage   Class: Narcissist EquivalentTo: Person that loves Self   Individual: male DifferentFrom: female   Individual: female   Individual: John Types: Person Facts: hasWife Mary, hasSon Bill, hasDaughter Susan, hasAge 33, hasGender male SameAs: Jack DifferentFrom: Mary, Susan, Bill   Individual: Mary Facts: hasSon Bill, hasDaughter Susan, hasAge 31, hasGender female   Individual: Bill Types: not (Narcissist) Facts: hasAge 13, hasGender male   Individual: Susan Facts: hasAge 8, hasGender female   Individual: Jeff Types: hasChild exactly 2 Teenager Facts: hasWife Emily, hasChild Ellen, hasChild Jack, hasAge 77, loves Jeff DifferentFrom: Ellen, Jack, Susan, Emily   Individual: Emily Types: hasAge some {39 , 49}   Individual: Ellen Types: hasAge some integer[>= 15 , <= 21]   Individual: Jack Facts: not hasAge "53"^^integer   SameIndividual: f:male g:masculine SameIndividual: f:female g:feminine EquivalentClasses: f:Adult g:Grownup EquivalentObjectProperties: f:hasChild g:child EquivalentDataProperties: f:hasAge g:age