W3C

OWL 2 Web Ontology Language:
Model-Theoretic Semantics

W3C Editor's Draft 11 April22 September 2008

This version:
http://www.w3.org/2007/OWL/draft/ED-owl2-semantics-20080411/http://www.w3.org/2007/OWL/draft/ED-owl2-semantics-20080922/
Latest editor's draft:
http://www.w3.org/2007/OWL/draft/owl2-semantics/
Previous version:
http://www.w3.org/2007/OWL/draft/WD-owl11-semantics-20080108/http://www.w3.org/2007/OWL/draft/ED-owl2-semantics-20080411/ (color-coded diff)
Authors:
Bernardo Cuenca Grau, Oxford University
Boris Motik, Oxford University
Contributors:
Ian Horrocks, Oxford University
Bijan Parsia, The University of Manchester
Peter F. Patel-Schneider,Patel-Schneider, Bell Labs Research, Alcatel-Lucent
Ulrike Sattler, The University of Manchester


Abstract

OWL 2 extends the W3C OWL Web Ontology Language with a small but useful set of features that have been requested by users, for which effective reasoning algorithms are now available, and that OWL tool developers are willing to support. The new features include extra syntactic sugar, additional property and qualified cardinality constructors, extended datatype support, simple metamodeling,metamodelling, and extended annotations.
This document provides athe model-theoretic semantics for OWL 2.

Status of this Document

May Be Superseded

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This document is being published as one of a set of 68 documents:

  1. Structural Specification and Functional-Style Syntax
  2. Model-Theoretic Semantics (this document)
  3. RDF-Based Semantics
  4. Mapping to RDF Graphs
  5. XML Serialization
  6. Profiles
  7. Primer Summary of Changes Since the previous Working Draft (dated 8 January 2008), the only change is the name of the language, from "OWL 1.1" to "OWL 2". Since the group is publishing three new Working Drafts,Conformance and the name has changed, it decided to publish the complete set with consistent names.Test Cases
  8. A Datatype for Internationalized Text

Please Comment By 11 May 2008ASAP

The OWL Working Group seeks public feedback on these Working Drafts. Please send your comments to public-owl-comments@w3.org (public archive). If possible, please offer specific changes to the text that would address your concern. You may also wish to check the Wiki Version of this document for internal-review comments and changes being drafted which may address your concerns.

No Endorsement

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

Patents

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.


Contents


1 Introduction

Editor's Note: See Issue-72 (Annotation Semantics). Editor's Note: See Issue 63 (OWL Full Semantics). Editor's Note: See Issue 69 (punning).This document defines the formalformal, model-theoretic semantics of OWL 2. The semantics given here follows the principles for definingis strongly related to the semantics of description logics [Description Logics] and is compatible with the semantics of the description logic SROIQ presented in[SROIQ]. Unfortunately,As the definition of SROIQ given in [ SROIQ ]does not provide for datatypes and metamodeling. Therefore,punning, the semantics of OWL 2 is defined in a direct model-theoretic way, by interpretingdirectly on the constructs of the functional-style syntax fromfor OWL 2 [OWL 2 Specification ].] instead of by reference to the semantics of SROIQ. For the constructs available in SROIQ, the semantics of SROIQ trivially corresponds to the one defined in this document.

Since OWL 2 does not haveis an RDF-compatible semantics. Ontologies expressed inextension of OWL RDF are givenDL, this document also provides a formal semantics by converting then intofor OWL Lite and OWL DL; this semantics is equivalent to the functional-styleofficial semantics of OWL Lite and OWL DL [OWL Abstract Syntax and interpretingSemantics]. Furthermore, this document also provides the model-theoretic semantics for the OWL 2 profiles [OWL 2 Profiles].

The semantics is defined for a set of axioms, rather than for an ontology document in the functional-style syntax. Turning ontology documents into sets of axioms involves determining the resultaxiom closure of an ontology (i.e., performing imports and renaming anonymous individuals apart) as specifieddescribed in this document.the OWL 2 Specification [OWL 2 Specification]).

OWL 2 allows for annotations of ontologies andontologies, ontology entities (classes, properties, and individuals)individuals), anonymous individuals, axioms, and ontology axioms. Annotations,other annotations. Annotations of all these types, however, have no semantic meaning in OWL 2 and are ignored in this document. Definitions inOWL 2 similarly have no semantics. Constructs onlydeclarations are simply used in annotationsto disambiguate class expressions from data ranges and definitions, like ObjectProperty , therefore doobject property from data property expressions in the functional-style syntax. Therefore, they are not show upmentioned explicitly in the tables in this document.

Since OWL2 is an extension of OWL DL, this document also provides a formalModel-Theoretic Semantics for OWL Lite and2

This section specifies the model-theoretic semantics of OWL DL and it is equivalent to2 ontologies in the definition givenfunctional-style syntax.

2.1 Vocabulary

Let D = ( NDT , NLT , NFA , ⋅ DT , ⋅ LT , ⋅ FA ) be a datatype map as defined in Section 4 of the OWL 2 Specification [OWL Abstract Syntax and Semantics ].2 Model-Theoretic Semantics forSpecification], interpreting the OWL 2 Editor's Note: See Issue-73 (infinite universe ).datatypes as defined in Sections 4.1 to 4.6. A vocabulary (or signature )V = ( NVC , N PoVOP , N PdVDP , NVI , N DVDT , VLT , NVFA ) over D is a 6-tuple where N7-tuple consisting of the following elements:

Given a vocabulary V, the same name can befollowing conventions are used in an ontologythis document to denote different syntactic parts of OWL 2 ontologies:

2.2 Interpretations

Given a datatype is defined by its name and the arity,map D and such a definition allows one to reuse the same name with different arities. The semantics of OWL 2 is defined with respect to a concrete domain , which isa tuplevocabulary V over D, an interpretation Int = ( Δ DInt , .ΔD , ⋅ C , ⋅ OP , ⋅ DP , ⋅ I , ⋅ DT , ⋅ LT , ⋅ FA ) wherefor D and V is a 9-tuple with the following structure.

Ic isThe following sections define the extensions of ⋅ OP, ⋅ DT, and ⋅ C to object property expressions, data ranges, and class expressions.

2.2.1 Object Property Expressions

The object property interpretation function that assigns to each OWL class A N Ic a subset A Ic of Δ I  ; . Ipo is the object property interpretation function that assigns to each object property R N Po a subset R Ipo of Δ I x Δ I  ; . Ipd is the data property interpretation function that assigns to each data property U N Pd a subset U Ipd of Δ I x Δ D  ; . Ii⋅ OP is the individual interpretation function that assigns to each individual a N I an element a Ii from Δ I . We extend the object interpretation function . Ipoextended to object property expressions as shown in Table 1.

Table 1. Interpreting Object Property Expressions
Object Property Expression Interpretation InverseObjectProperty(R)⋅ OP
InverseOf( OP ) { ( x , y ) | ( y , x ) R Ipo(OP)OP }

We extend2.2.2 Data Ranges

The datatype interpretation function . D⋅ DT is extended to data ranges as shown in Table 2.3. Note that datatypes in OWL 2 are all unary; thus, each datatype DT is interpreted as a unary relation (DT)DT over ΔD. Data ranges, however, can be n-ary—this allows implementations to provide built-in predicates such as comparisons or arithmetic as an extension. Hence, an n-ary data range DR is interpreted as an n-ary relation (DR)DT over ΔD.

Editor's Note: OWL WG ISSUE-127 is related to n-ary data ranges and might impact this section.
Table 2.3. Interpreting Data Ranges
Data Range Interpretation DataOneOf(v⋅ DT
OneOf( lt1 ... vltn ) { v(lt1 D)LT , ... , v(ltn D)LT }
DataComplementOf(DR) ( ΔComplementOf( DR ) D)n \ DR D(DR)DT where n is the arity of DR
DatatypeRestriction(DRDatatypeRestriction( DT f1 lt1 ... f v) then -ary relation over Δ D obtained by applying the facetltn ) (DT)DT (〈 f with value v to the data range DR as specified in [ XML Schema Datatypes ] We extend1 lt1 〉)FA ... (〈 fn ltn 〉)FA

2.2.3 Class Expressions

The class interpretation function . Ic⋅ C is extended to descriptionsclass expressions as shown in Table 3. With4. For S a set, #S we denotedenotes the number of elements in a setS.

Table 3.4. Interpreting Descriptions DescriptionClass Expressions
Class Expression Interpretation owl:Thing Δ I owl:Nothing empty set ObjectComplementOf(C) Δ I \⋅ C
Ic ObjectIntersectionOf(CIntersectionOf( CE1 ... CCEn ) C(CE1 Ic)C ∩ ... ∩ C(CEn Ic ObjectUnionOf(C)C
UnionOf( CE1 ... CCEn ) C(CE1 Ic )C ... ∪ C(CEn Ic ObjectOneOf(a)C
ComplementOf( CE ) ΔInt \ (CE)C
OneOf( a1 ... an ) { a(a1 Ii)I , ... , a(an Ii)I }
ObjectSomeValuesFrom(R C)SomeValuesFrom( OPE CE ) { x | ∃ y : ( x, x, y ) R Ipo(OPE)OP and y(CE)C Ic}
ObjectAllValuesFrom(R C)AllValuesFrom( OPE CE ) { x | ∀ y : ( x, x, y ) R Ipo(OPE)OP implies y(CE)C Ic}
ObjectHasValue(R a)HasValue( OPE a ) { x | ( x, a Ii x , (a)I (OPE)OP }
ExistsSelf( OPE ) { x | x , x R Ipo(OPE)OP }
ObjectExistsSelf(R)MinCardinality( n OPE ) { x | ( x,#{ y | x , y (OPE)OP } n }
MaxCardinality( n OPE ) { x | #{ y | x , y R Ipo(OPE)OP } n }
ObjectMinCardinality(n R C)ExactCardinality( n OPE ) { x | #{ y | ( x, x , y (OPE)OP } = n }
MinCardinality( n OPE CE ) { x | #{ y | x , y R Ipo(OPE)OP and y(CE)C Ic} ≥ n }
ObjectMaxCardinality(n R C)MaxCardinality( n OPE CE ) { x | #{ y | ( x, x , y ) R Ipo(OPE)OP and y(CE)C Ic} ≤ n }
ObjectExactCardinality(n R C)ExactCardinality( n OPE CE ) { x | #{ y | ( x, x , y ) R Ipo(OPE)OP and y(CE)C Ic} = n }
DataSomeValuesFrom(USomeValuesFrom( DPE1 ... UDPEn DR)DR ) { x | ∃ y1, ...,... , yn : ( x, x , yk ) U(DPEk Ipd)DP for each 1 ≤ kn and ( y1 , ...,... , yn ) DR D(DR)DT }
DataAllValuesFrom(UAllValuesFrom( DPE1 ... UDPEn DR)DR ) { x | ∀ y1, ...,... , yn : ( x, x , yk ) U(DPEk Ipd)DP for each 1 ≤ kn implies (imply y1 , ...,... , yn (DR)DT }
HasValue( DPE lt ) { x | x , (lt)LT DR D(DPE)DP }
DataHasValue(U v)MinCardinality( n DPE ) { x | ( x, v D#{ y | x , y (DPE)DP} n }
MaxCardinality( n DPE ) { x | #{ y | x , y U Ipd(DPE)DP } DataMinCardinality(n U DR) n }
ExactCardinality( n DPE ) { x | #{ y | ( x, x , y (DPE)DP } = n }
MinCardinality( n DPE DR ) { x | #{ y | x , y U Ipd(DPE)DP and y DR D(DR)DT } ≥ n }
DataMaxCardinality(n U DR)MaxCardinality( n DPE DR ) { x | #{ y | ( x, x , y ) U Ipd(DPE)DP and y DR D(DR)DT } ≤ n }
DataExactCardinality(n U DR)ExactCardinality( n DPE DR ) { x | #{ y | ( x, x , y ) U Ipd(DPE)DP and y DR D(DR)DT } = n }

2.3 Satisfaction of OWL 2 axiomsin an Interpretation

An interpretation Int = ( ΔInt , ΔD , ⋅ C , ⋅ OP , ⋅ DP , ⋅ I is defined as shown in Table 4. With, ⋅ DT , ⋅ LT , ⋅ FA ) satisfies an axiom w.r.t. an ontology O we denoteif the composition of binary relations. Table 4.axiom satisfies appropriate conditions listed in the following sections. Satisfaction of axioms in an Interpretation AxiomInt is defined w.r.t. O because satisfaction of key axioms uses the function ISNAMEDO defined as follows, where the axiom closure of O is defined in Section 3.4 of the OWL 2 Specification [OWL 2 Specification]:

ISNAMEDO(x) = true for x ΔInt if and only if (a)I = x for some named individual a occurring in the axiom closure of O.

2.3.1 Class Expression Axioms

Satisfaction of OWL 2 class expression axioms in Int w.r.t. O is defined as shown in Table 5.

Table 5. Satisfaction of Class Expression Axioms in an Interpretation
Axiom Condition
SubClassOf(C D)SubClassOf( CE1 CE2 ) (CE1)C Ic D Ic EquivalentClasses(C(CE2)C
EquivalentClasses( CE1 ... CCEn ) C(CEj Ic =)C = (CEk Ic)C for each 1 ≤ j , n and each 1 kn
DisjointClasses(CDisjointClasses( CE1 ... CCEn ) C(CEj Ic )C (CEk Ic is empty)C = for each 1 ≤ j , kn and each 1 k n such that jk
DisjointUnion(ADisjointUnion( C CE1 ... CCEn ) A Ic =(C)C = (CE1 Ic)C ∪ ... ∪ C(CEn Ic and)C and
(CEj Ic )C (CEk Ic is empty)C = for each 1 ≤ j , kn and each 1 k n such that jk

SubObjectPropertyOf(R S) R Ipo2.3.2 Object Property Expression Axioms

Satisfaction of OWL 2 object property expression axioms in Int w.r.t. O is defined as shown in Table 6.

Table 6. Satisfaction of Object Property Expression Axioms in an Interpretation
Axiom Condition
SubPropertyOf( OPE1 OPE2 ) (OPE1)OP S Ipo SubObjectPropertyOf(SubObjectPropertyChain(R(OPE2)OP
SubPropertyOf( PropertyChain( OPE1 ... ROPEn ) S) ROPE ) y0 , ... , yn : y0 , y1 Ipo o (OPE1)OP and ... o Rand yn-1 , yn Ipo S Ipo EquivalentObjectProperties(R (OPEn)OP imply y0 , yn (OPE)OP
EquivalentProperties( OPE1 ... ROPEn ) R(OPEj Ipo)OP = R(OPEk Ipo)OP for each 1 ≤ j , n and each 1 kn
DisjointObjectProperties(RDisjointProperties( OPE1 ... ROPEn ) R(OPEj Ipo)OP R(OPEk Ipo is empty)OP = for each 1 ≤ j , kn and each 1 k n such that jk
ObjectPropertyDomain(R C) {PropertyDomain( OPE CE ) x | y : (x, y ) : x , y R Ipo } (OPE)OP implies x (CE)C
Ic ObjectPropertyRange(R C) {PropertyRange( OPE CE ) x , y | x : (x : x , y ) R Ipo } (OPE)OP implies y (CE)C
Ic InverseObjectProperties(R S) R IpoInverseProperties( OPE1 OPE2 ) (OPE1)OP = { ( x , y ) | ( y , x ) S Ipo(OPE2)OP }
FunctionalObjectProperty(R) (FunctionalProperty( OPE ) x , y1 ), y2 : x , y1 R Ipo(OPE)OP and ( x , y2 ) R Ipo(OPE)OP imply y1 = y2
InverseFunctionalObjectProperty(R) (InverseFunctionalProperty( OPE ) x1 , x2 , y : x1 , y ) R Ipo(OPE)OP and ( x2 , y ) R Ipo(OPE)OP imply x1 = x2
ReflexiveObjectProperty(R)ReflexiveProperty( OPE ) x : xΔ IInt implies ( x , x ) R Ipo IrreflexiveObjectProperty(R)(OPE)OP
IrreflexiveProperty( OPE ) x : xΔ IInt implies ( x , x (OPE)OP
SymmetricProperty( OPE ) x , y : x , y (OPE)OP implies y , x (OPE)OP
AsymmetricProperty( OPE ) x , y : x , y (OPE)OP implies y , x (OPE)OP
TransitiveProperty( OPE ) x , y , z : x , y (OPE)OP and y , z (OPE)OP imply x , z (OPE)OP

2.3.3 Data Property Expression Axioms

Satisfaction of OWL 2 data property expression axioms in Int w.r.t. O is notdefined as shown in R Ipo SymmetricObjectProperty(R) (Table 7.

Table 7. Satisfaction of Data Property Expression Axioms in an Interpretation
Axiom Condition
SubPropertyOf( DPE1 DPE2 ) (DPE1)DP (DPE2)DP
EquivalentProperties( DPE1 ... DPEn ) (DPEj)DP = (DPEk)DP for each 1 j n and each 1 k n
DisjointProperties( DPE1 ... DPEn ) (DPEj)DP (DPEk)DP = for each 1 j n and each 1 k n such that j k
PropertyDomain( DPE CE ) x , y : x , y (DPE)DP implies x (CE)C
PropertyRange( DPE DR ) x , y : x , y R Ipo(DPE)DP implies y (DR)DT
FunctionalProperty( DPE ) x , y1 , y2 : x , y1 (DPE)DP and x , y2 (DPE)DP imply y1 = y2

2.3.4 Keys

Satisfaction of keys in Int w.r.t. O is defined as shown in Table 8.

Table 8. Satisfaction of Keys in an Interpretation
Axiom Condition
HasKey( CE PE1 ... PEn ) x , y , z1 , ... , zn  :
    if ISNAMEDO(x) and ISNAMEDO(y) and ISNAMEDO(z1) and ... and ISNAMEDO(zn) and x (CE)C and y (CE)C and
       for each 1 i n,
          if PEi is an object property, then x , zi (PEi)OP and y , zi (PEi)OP, and
          if PEi is a data property, then x , zi (PEi)DP and y , zi (PEi)DP
    then x = y

2.3.5 Assertions

Satisfaction of OWL 2 assertions in Int w.r.t. O is defined as shown in Table 9.

Table 9. Satisfaction of Assertions in an Interpretation
Axiom Condition
SameIndividual( a1 ... an ) (aj)I = (ak)I for each 1 j n and each 1 k n
DifferentIndividuals( a1 ... an ) (aj)I (ak)I for each 1 j n and each 1 k n such that j k
ClassAssertion( CE a ) (a)I (CE)C
PropertyAssertion( OPE a1 a2 ) (a1)I , (a2)I (OPE)OP
NegativePropertyAssertion( OPE a1 a2 ) (a1)I , (a2)I (OPE)OP
PropertyAssertion( DPE a lt ) (a)I , (lt)LT (DPE)DP
NegativePropertyAssertion( DPE a lt ) (a)I , (lt)LT (DPE)DP

2.3.6 Ontologies

Int satisfies an OWL 2 ontology O if all axioms in the axiom closure of O (with anonymous individuals renamed apart as described in Section 5.6.2 of the OWL 2 Specification [OWL 2 Specification]) are satisfied in Int w.r.t. O.

2.4 Models

An interpretation Int = ( ΔInt , ΔD , ⋅ C , ⋅ OP , ⋅ DP , ⋅ I , ⋅ DT , ⋅ LT , ⋅ FA ) is a model of an OWL 2 ontology O if an interpretation Int' = ( ΔInt , ΔD , ⋅ C , ⋅ OP , ⋅ DP , ⋅ I' , ⋅ DT , ⋅ LT , ⋅ FA ) exists such that ⋅ I' coincides with ⋅ I on all named individuals and Int' satisfies O.

Thus, an interpretation Int satisfying O is also a model of O. In contrast, a model Int of O may not satisfy O directly; however, by modifying the interpretation of anonymous individuals, Int can always be coerced into an interpretation Int' that satisfies O.

2.5 Inference Problems

Let D be a datatype map and V a vocabulary over D. Furthermore, let O and O' be OWL 2 ontologies, CE, CE1, and CE2 class expressions, and a a named individual, such that all of them refer only to the vocabulary elements in V.

3 Independence of the Semantics from the Datatype Map

The semantics of OWL 2 has been defined in such a way that the semantics of an OWL 2 ontology O does not depend on the choice of a datatype map, as long as the datatype map chosen contains all the datatypes occurring in O. This statement is made precise by the following theorem, which has several useful consequences:

Theorem 1. Let O1 and O2 be OWL 2 ontologies over a vocabulary V and D = ( NDT , NLT , NFA , ⋅ DT , ⋅ LT , ⋅ FA ) a datatype map such that each datatype mentioned in O1 and O2 is either rdfs:Literal or it occurs in NDT. Furthermore, let D' = ( yNDT' , x ) R Ipo AsymmetricObjectProperty(R) ( xNLT' , y ) R Ipo implies ( yNFA' , x⋅ DT ' , ⋅ LT ' , ⋅ FA ' ) is not in R Ipo TransitiveObjectProperty(R) R Ipo o R Ipo R Ipo SubDataPropertyOf(U V) U Ipdbe a datatype map such that NDT V Ipd EquivalentDataProperties(U 1 ... UN ) U j Ipd = U k Ipd for each 1 jDT', k N DisjointDataProperties(U 1 ... ULT(DT) = N ) U j Ipd U k Ipd is emptyLT'(DT) and NFA(DT) = NFA'(DT) for each 1 j , k DT NDT, and j k DataPropertyDomain(U C) { x | y : (x⋅ DT ', y ) U Ipd } C Ic DataPropertyRange(U DR) { y | x : (x⋅ LT ', y ) U Ipd } DR D FunctionalDataProperty(U) ( xand ⋅ FA ' are extensions of ⋅ DT, ⋅ LT, y 1 ) U Ipdand ( x⋅ FA, yrespectively. Then, O1 entails O2 ) U Ipd imply yw.r.t. D if and only if O1 = yentails O2 SameIndividual(aw.r.t. D'.

Proof. Without loss of generality, one can assume O1 ... a n ) a j Ii = a k Ii for eachand O2 to be in negation-normal form [Description Logics]. The claim of the theorem is equivalent to the following statement: an interpretation Int w.r.t. D and and V exists such that O1 j , k n DifferentIndividuals(ais and O2 is not satisfied in Int if and only if an interpretation Int' w.r.t. D' and V exists such that O1 ... a n ) a j Ii a k Ii foris and O2 is not satisfied in Int'. The (⇐) direction is trivial since each 1 j , k ninterpretation Int w.r.t. D' and j k ClassAssertion(a C) a Ii C Ic ObjectPropertyAssertion(R a b)V is also an interpretation w.r.t. D and V. For the (⇒) direction, assume that an interpretation Int = ( a IiΔInt , ΔD , ⋅ C , ⋅ OP , ⋅ DP , ⋅ I , b Ii ) R Ipo NegativeObjectPropertyAssertion(R a b) ( a Ii⋅ DT , b Ii⋅ LT , ⋅ FA ) w.r.t. D and V exists such that O1 is and O2 is not satisfied in R Ipo DataPropertyAssertion(U a v)Int. Let Int' = ( a IiΔInt , vΔD ) U Ipd NegativeDataPropertyAssertion(U a v) ( a Ii' , v D⋅ C ' , ⋅ OP , ⋅ DP ' , ⋅ I , ⋅ DT ' , ⋅ LT ' , ⋅ FA ' ) is not in U Ipd Let Obe an OWL 2 ontology with vocabulary V . O is consistent if aninterpretation I existssuch that

Clearly, ComplementOf( DR )DT ComplementOf( DR )DT ' for each data range DR that is satisfiable w.r.t. O if thereis either a model I of O such that C Ic is not empty. O entailsdatatype, a datatype restriction, or an OWL 2 ontology O' with vocabulary V if every modelenumerated data range. The interpretation of Odata properties is also a model of O' ; furthermore,the same in Int and Int', so (CE)C = (CE)C ' for each class expression CE occurring in O1 and O' are equivalent ifO entails O'2. Therefore, O1 is and O' entailsO2 is not satisfied in Int'. 3QED

4 References

[Description Logics]
The Description Logic Handbook. Franz Baader, Diego Calvanese, Deborah McGuinness, Daniele Nardi, Peter Patel-Schneider, Editors. Cambridge University Press, 2003; and Description Logics Home Page.
[Metamodeling] On the Properties of Metamodeling in[OWL 2 Specification]
OWL .2 Web Ontology Language:Structural Specification and Functional-Style Syntax Boris Motik. In Proceedings of ISWC-2005Motik, Peter F. Patel-Schneider, Ian Horrocks. W3C Editor's Draft, 22 September 2008, http://www.w3.org/2007/OWL/draft/ED-owl2-syntax-20080922/. Latest version available at http://www.w3.org/2007/OWL/draft/owl2-syntax/.
[OWL 2 Specification]Profiles]
OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax Boris Motik, Peter F. Patel-Schneider, Ian Horrocks. W3C Editor's Draft, 11 April22 September 2008, http://www.w3.org/2007/OWL/draft/ED-owl2-syntax-20080411/http://www.w3.org/2007/OWL/draft/ED-owl2-syntax-20080922/. Latest version available at http://www.w3.org/2007/OWL/draft/owl2-syntax/.
[OWL Abstract Syntax and Semantics]
OWL Web Ontology Language: Semantics and Abstract Syntax. Peter F. Patel-Schneider, Pat Hayes, and Ian Horrocks, Editors, W3C Recommendation, 10 February 2004.
[SROIQ]
The Even More Irresistible SROIQ. Ian Horrocks, Oliver Kutz, and Uli Sattler. In Proc. of the 10th Int. Conf. on Principles of Knowledge Representation and Reasoning (KR 2006). AAAI Press, 2006.
[XML Schema Datatypes] XML Schema Part 2: Datatypes Second Edition[RFC-4646]
RFC 4646 - Tags for Identifying Languages. Paul V. Biron and Ashok Malhotra, eds. W3C Recommendation 28 October 2004.M. Phillips and A. Davis. IETF, September 2006, http://www.ietf.org/rfc/rfc4646.txt. Latest version is available as BCP 47, (details).