[[TracNav(TracNav/ISO15926inOWL)]] = ISO 15926-2 in OWL = This page lists and describes the different available OWL representations of various parts of ISO 15926-2. [[PageOutline(2-4,Contents,inline)]] ---- == ISO 15926-2:2003 entity types == The file http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003 contains all the entity types defined in ISO 15926-2:2003 represented as `owl:class`es. The file is generated by translating the EXPRESS file `lifecycle_integration_schema.exp` downloaded from [http://www.steptools.com/sc4/archive/oil-and-gas/15926-0002-lifecycle_integration.exp?rev=1.1&content-type=text/vnd.viewcvs-markup http://www.tc184-sc4.org/EXPRESS/] which ISO 15926-2 (2003) annex B references, to an XML serialization of OWL. A more thorough description of the translation is found in the article [wiki:ISO15926inOWLtranslateEXPRESStoOWL]. This ontology is represented in the OWL sublanguage ''OWL DL'' and has the [http://en.wikipedia.org/wiki/Description_logic#DL_Expressivity DL expressivity] [[LatexEquation(\mathcal{SHN(D)})]], this is partly because the ontology imports the [wiki:ISO15926inOWLPart2#ISO15926-2:2003OWLlist OWL linked list] representation. == ISO 15926-2:2003 definitions, examples and notes == The file http://rds.posccaesar.org/2008/07/OWL/ISO-15926-2_2003_annotations contains definitions, examples and notes of the ISO 15926-2:2003 entity types. The file is generated by transforming a version of the EXPRESS file [http://www.tc184-sc4.org/EXPRESS/ lifecycle_integration_schema.exp] containing this information in comments. This EXPRESS file is not "ISO official", so there is no guarantee of the correctness of the content. There is a [http://www.tc184-sc4.org/wg3ndocs/wg3n1328/lifecycle_integration_schema.html ISO published online version of ISO 15926-2:2003], please report back if you find errors in our OWL representations. This ontology is represented in the OWL sublanguage ''OWL DL'' and has the [http://en.wikipedia.org/wiki/Description_logic#DL_Expressivity DL expressivity] [[LatexEquation(\mathcal{SHN(D)})]]. This complexity is completely due to the complexity of [wiki:ISO15926inOWLPart2#ISO15926-2:2003entitytypes 2008/02/OWL/ISO-15926-2_2003] which this file imports. All definitions, examples and notes are represented using `owl:AnnotationProperty` which have no effect on the DL expressiveness of an OWL ontology. == ISO 15926-2:2003 membership relationships == The file http://rds.posccaesar.org/2008/07/OWL/ISO-15926-2_2003_entityMembership contains membership relationships between the entity types of ISO 15926-2:2003. These relationships are expressed after an interpretation of the text definitions of the entity types of ISO 15926-2:2003; a discussion on this work is found on the wiki page [wiki:ISO15926inOWLPart2EntityMembership Adding membership relationships to ISO 15926-2 in OWL]. The file http://rds.posccaesar.org/2008/07/OWL/ISO-15926-2_2003_entityMembershipCandidates contains candidate membership relationships. See the above mentioned wiki page for more information. {{{ #!RightFigure {{{ #!graphviz.dot digraph G { overlap=false; rankdir=RL; node [fontname=Arial, shape=box]; edge [fontname=Arial, fontsize=8]; B[label="\nCLASS"]; A[label="\nTHING"]; Rel[label="\nCLASSIFICATION"]; Rel -> A[label="hasClassifier", color="grey70", fontsize=6]; Rel -> B[label="hasClassified", color="grey70", fontsize=6]; A -> Rel[label="isClassifierIn", style="dashed", color="red", minlen=3]; B -> Rel[label="isClassifiedIn", style="dashed", color="red", minlen=3]; {rank = same; A; B;} } }}} ''Figure 1: The `owl:Class` `Classification`, the `owl:ObjectProperty`s[[BR]]`hasClassifier` and `hasClassified` (in grey) -- and their inverse[[BR]]`owl:ObjectProperty`s `isClassifierIn` and `isClassifiedIn` (in red) respectively.'' }}} == ISO 15926-2:2003 inverse roles == The file http://rds.posccaesar.org/2008/09/OWL/ISO-15926-2_2003_inverseRoles defines the inverse `owl:ObjectProperty` of all the `owl:ObjectProperty`s defined in http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003. The naming convention is that the inverse property of `hasX` is named `isXIn`. __Example__: The `owl:ObjectProperty`s `hasClassifier` and `hasClassified` are defined in [http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003 ISO-15926-2_2003] as {{{ ObjectProperty: hasClassifier Domain: Classification Class: Classification SubClassOf: hasClassifier exactly 1 Class }}} i.e., the domain of `hasClassifier` is `Classification` and the range of `hasClassifier`, set locally on the `owl:Class` `Classification`, is `Class`. `isClassifierIn`, the inverse property of `hasClassifer`, is then an `owl:ObjectProperty` with `Classification` as ''range'' and `Class` as ''domain''. See Figure 1. {{{ #!RightFigure {{{ #!graphviz.dot digraph G { overlap=false; rankdir=RL; ranksep=2; node [fontname=Arial, shape=box]; edge [fontname=Arial, fontsize=8]; B[label="\nCLASS"]; A[label="\nCLASS"]; Rel[label="\nSPECIALIZATION"]; Rel -> B[label="hasSuperclass"]; B -> Rel[label="isSuperclassIn", style="dashed", color="grey70", fontsize=6]; Rel -> A[label="hasSubclass", color="grey70", labelfontcolor="grey70", fontsize=6]; A -> Rel[label="isSubclassIn", style="dashed"]; B -> A[minlen=3, style=dashed, dir=back, label="isSubclassIn-o-hasSuperclass", color="red"]; {rank = same; A; B;} } }}} ''Figure 2: The `owl:Class` `Specialization`, the `owl:ObjectProperty`s `hasSubclass`[[BR]]and `hasSuperclass` (solid line), their inverse `owl:ObjectProperty`s `isSubclassIn`[[BR]]and `isSuperclassIn` (dashed line) respectively -- and the `owl:propertychain`[[BR]]`isSubclassIn-o-hasSuperclass` (in red).'' }}} == ISO 15926-2:2003 chained roles == The file http://rds.posccaesar.org/2008/09/OWL/ISO-15926-2_2003_chainedRoles defines a series of `owl:propertyChain`s. Property chains are the "owl-equvialent" to the mathematical [http://en.wikipedia.org/wiki/Relation_composition composition of relations]. Note: [http://www.w3.org/2007/OWL/wiki/Requirements#F8:_Property_Chain_Inclusion `owl:propertyChain` is a OWL 2 construct], so this file is not OWL DL. The (binary) relations defined in ISO-15926 are ''reified'', meaning that they are represented as entities with two attributes, e.g., the `COMPOSITION_OF_INDIVIDUAL` entity has two attributes: `part` and `whole`. In OWL the common way of representing relations is by means of binary properties, e.g., `hasPart` having "wholes" as domain and "parts" as range. This is equivalent to a binary logical predicate [[LatexEquation(hasPart(x, y))]] which is true only if [[LatexEquation(y)]] is a part of [[LatexEquation(x)]]. The property chain construct in OWL allows for an elegant definition of the more "OWL friendly" binary properties from the reified relations. __Example__: Specializations of classes in ISO 15926 are represented using the reified entity `SPECIALIZATION`. `SPECIALIZATION` has two attributes `subclass` and `superclass`. In the [http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003 OWL representation of ISO 15926-2] this becomes the `owl:Class` `Specialization` and two `owl:ObjectProperty`s `hasSubclass` and `hasSuperclass` where the domain of the two properties is the class `Specialization`. (Read more on the OWL representation here). In OWL specialization is represented using `rdsf:subClassOf`. This relation can be mimiced by a property chain of `isSubclassIn` (the inverse property of `hasSubclass`) and `hasSuperclass`. This property chain is defined in [http://rds.posccaesar.org/2008/09/OWL/ISO-15926-2_2003_chainedRoles ISO-15926-2_2003_chainedRoles] and is called `isSubclassIn-o-hasSuperclass`. See Figure 2 for an illustration of this example. == OWL list == The [http://www.co-ode.org/ontologies/lists/2008/09/11/ OWL list ontology] defines a set of entities used to describe the OWL list pattern written by Nick Drummond et al, see http://owl-workshop.man.ac.uk/acceptedLong/submission_12.pdf This ontology is represented in the OWL sublanguage ''OWL DL'' and has the [http://en.wikipedia.org/wiki/Description_logic#DL_Expressivity DL expressivity] [[LatexEquation(\mathcal{SHN})]]. == Dependence diagram == The following diagram displays the dependencies and relationships between the ontologies listed on this page. {{{ #!graphviz.dot digraph G { overlap=false; node [fontname=Arial, shape=box]; edge [fontname=Arial, fontsize=8]; "ISO-15926-2_2003_entityMembershipCandidates\n(2008/07)" [URL="http://rds.posccaesar.org/2008/07/OWL/ISO-15926-2_2003_entityMembershipCandidates"]; "ISO-15926-2_2003_entityMembership\n(2008/07)" [URL="http://rds.posccaesar.org/2008/07/OWL/ISO-15926-2_2003_entityMembership"]; "ISO-15926-2_2003\n(2008/02)" [URL="http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003"]; "OWL list" [URL="http://www.co-ode.org/ontologies/lists/2008/09/11/"]; "ISO-15926-2_2003_annotations\n(2008/07)" [URL="http://rds.posccaesar.org/2008/07/OWL/ISO-15926-2_2003_annotations"]; "ISO-15926-2_2003_inverseRoles\n(2008/09)" [URL="http://rds.posccaesar.org/2008/09/OWL/ISO-15926-2_2003_inverseRoles"]; "ISO-15926-2_2003_chainedRoles\n(2008/09)" [URL="http://rds.posccaesar.org/2008/09/OWL/ISO-15926-2_2003_chainedRoles"]; "ISO-15926-2_2003\n(2008/02)" -> "OWL list" [label="imports"]; "ISO-15926-2_2003_annotations\n(2008/07)" -> "ISO-15926-2_2003\n(2008/02)" [label="imports"]; "ISO-15926-2_2003_entityMembershipCandidates\n(2008/07)" -> "ISO-15926-2_2003_entityMembership\n(2008/07)" [label="imports"]; "ISO-15926-2_2003_entityMembership\n(2008/07)" -> "ISO-15926-2_2003\n(2008/02)" [label="imports"]; "ISO-15926-2_2003_inverseRoles\n(2008/09)" -> "ISO-15926-2_2003\n(2008/02)" [label="imports"]; "ISO-15926-2_2003_chainedRoles\n(2008/09)" -> "ISO-15926-2_2003_inverseRoles\n(2008/09)"[label="imports"]; } }}}