ISO/TS 15926-8:2011
(Main)Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities — Part 8: Implementation methods for the integration of distributed systems: Web Ontology Language (OWL) implementation
Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities — Part 8: Implementation methods for the integration of distributed systems: Web Ontology Language (OWL) implementation
ISO/TS 15926-8:2011 is a specification for data exchange and life-cycle information integration using Resource Description Framework (RDF) and Web Ontology Language (OWL). ISO/TS 15926-8:2011 provides rules for implementing the upper ontology specified by ISO 15926-2 and the template methodology specified by ISO 15926-7 into the RDF and OWL languages, including models for reference data as specified by ISO/TS 15926-3 and ISO/TS 15926-4, and for metadata. The electronic files attached to ISO/TS 15926-8:2011 provide the OWL declarations, together with example instance data.
Systèmes d'automatisation industrielle et intégration — Intégration de données de cycle de vie pour les industries de "process", y compris les usines de production de pétrole et de gaz — Partie 8: Méthodes de mise en oeuvre pour l'intégration de systèmes distribués: Mise en oeuvre du langage d'ontologie du Web (OWL)
General Information
Standards Content (Sample)
TECHNICAL ISO/TS
SPECIFICATION 15926-8
First edition
2011-10-15
Industrial automation systems and
integration — Integration of life-cycle
data for process plants including oil and
gas production facilities —
Part 8:
Implementation methods for the
integration of distributed systems: Web
Ontology Language (OWL)
implementation
Systèmes d'automatisation industrielle et intégration — Intégration de
données de cycle de vie pour les industries de «process», y compris les
usines de production de pétrole et de gaz —
Partie 8: Méthodes de mise en oeuvre pour l'intégration de systèmes
distribués: Mise en œuvre du langage d'ontologie du Web (OWL)
Reference number
©
ISO 2011
This CD-ROM contains:
1) the publication ISO/TS 15926-8:2011 in portable document format (PDF), which can be viewed using
Adobe® Acrobat® Reader;
2) a separate folder containing electronic inserts, which provide OWL declarations and example
instance data.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.
© ISO 2011
All rights reserved. Unless required for installation or otherwise specified, no part of this CD-ROM may be reproduced, stored in a retrieval
system or transmitted in any form or by any means without prior permission from ISO. Requests for permission to reproduce this product
should be addressed to
ISO copyright office Case postale 56 CH-1211 Geneva 20 Switzerland
Internet copyright@iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
Published in Switzerland
ii © ISO 2011 – All rights reserved
...
TECHNICAL ISO/TS
SPECIFICATION 15926-8
First edition
2011-10-15
Industrial automation systems and
integration — Integration of life-cycle
data for process plants including oil and
gas production facilities —
Part 8:
Implementation methods for the
integration of distributed systems: Web
Ontology Language (OWL)
implementation
Systèmes d'automatisation industrielle et intégration — Intégration de
données de cycle de vie pour les industries de «process», y compris les
usines de production de pétrole et de gaz —
Partie 8: Méthodes de mise en œuvre pour l'intégration de systèmes
distribués: Mise en oeuvre du langage d'ontologie du Web (OWL)
Reference number
©
ISO 2011
© ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2011 – All rights reserved
Contents Page
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Terms, definitions, and abbreviated terms . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.1 Terms and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.2 Abbreviated terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Fundamental concepts and assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 ISO/TS 15926-7 templates and first order logic rules . . . . . . . . . . . . . . . . . . 8
3.3 ISO/TS 15926-4 reference data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 User-defined taxonomy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.5 Templates and specialized templates . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.6 Use of OWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.7 Namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4 ISO 15926-2 data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5 ISO/TS 15926-4 reference data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6 OWL template specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.2 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7 Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.2 Template model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.3 Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.4 Lifted templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.5 Lowered templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.5.1 Instantiating lowered templates . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.6 Templates in RDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.7 Example: A proto-template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.8 Templates as template instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.8.1 p7tm classes for meta-templates . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8 Object information models (OIMs) and specialized templates . . . . . . . . . . . . . . . . . 17
8.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2 OIM versus specialized template construct . . . . . . . . . . . . . . . . . . . . . . . . 18
8.3 Specialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.4 Cardinalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.5 OIM for assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.6 Naming convention on template roles . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.7 Uniqueness context of template roles . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Annex A (normative) Information object registration . . . . . . . . . . . . . . . . . . . . . . . . 21
A.1 Document identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
A.2 Schema identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
A.2.1 OWL ontology for data model . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
c ISO 2011 — All rights reserved iii
A.2.2 Template specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
A.2.3 OWL ontology for templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
A.2.4 OWL ontology for reference data . . . . . . . . . . . . . . . . . . . . . . . . . 21
A.2.5 OWL ontology for metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Annex B (normative) Templates as RDF/OWL n-ary relations . . . . . . . . . . . . . . . . . . . 23
B.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
B.2 ISO/TS 15926-8 constructs for template signatures . . . . . . . . . . . . . . . . . . . 24
Annex C (normative) Rules for usage of OWL . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
C.1 OWL native representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
C.2 Template translation from EXPRESS-native to OWL-native instance model . . . . . . 28
C.3 Library object translation from EXPRESS-native to OWL-native instance model . . . 28
C.4 owl:Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
C.5 Individual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
C.6 Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
C.6.1 Object property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
C.6.2 Datatype property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
C.6.3 Annotation property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
C.7 Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
C.7.1 rdf:ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
C.7.2 rdf:about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
C.7.3 URI reference for handed-over objects . . . . . . . . . . . . . . . . . . . . . . 30
C.8 Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
C.8.1 Declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Annex D (normative) Computer interpretable listings . . . . . . . . . . . . . . . . . . . . . . . . 32
D.1 Ontology for data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
D.2 Ontology for template model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
D.3 Ontology for proto templates and templates initial set . . . . . . . . . . . . . . . . . . 32
D.4 Ontology for metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Annex E (informative) Pattern for an ontology for reference data . . . . . . . . . . . . . . . . . . 33
Annex F (normative) Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
F.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
F.2 Metadata declarations for provenance . . . . . . . . . . . . . . . . . . . . . . . . . . 34
F.3 Metadata declarations for security and rules . . . . . . . . . . . . . . . . . . . . . . . 35
Annex G (informative) Assertion versus terminological components . . . . . . . . . . . . . . . . 36
Annex H (informative) Example use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
H.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
H.2 Example: A proto-template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
H.2.1 The template defined as a class . . . . . . . . . . . . . . . . . . . . . . . . . . 37
H.2.2 A statement using the template . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
H.3 Example: OIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
H.3.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
H.3.2 Manchester syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
H.4 Example: temporal parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
H.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
H.4.2 Generic representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
H.4.3 Specialized template IdentificationOfPhysicalObject . . . . . . . . . . . . . . . 41
H.4.4 Specialized template IdentificationOfPhysicalObject-processplant . . . . . . . . 42
iv
c ISO 2011 — All rights reserved
H.5 A specialized template and a template instance . . . . . . . . . . . . . . . . . . . . . 43
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figures
Figure 1 — Dependencies between ontologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure B.1 — W3C’s working group note: defining n-ary relations . . . . . . . . . . . . . . . . . 23
Figure C.1 — Reified relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure C.2 — OWL-native relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure H.1 — Generic temporal parts, identification OIM . . . . . . . . . . . . . . . . . . . . . . 41
Figure H.2 — ProcessPlant temporal part, name OIM . . . . . . . . . . . . . . . . . . . . . . . . 43
Tables
Table 1 — URIs under control of the World Wide Web Consortium . . . . . . . . . . . . . . . . . 9
Table 2 — Namespaces that are used for the examples in this part of ISO 15926. . . . . . . . . . . 10
Table F.1 — Examples of properties that are rdf:subPropertyOf OWL standard annotation properties 35
Table F.2 — Meta data elements from ISO/TS 15926-8 . . . . . . . . . . . . . . . . . . . . . . . 35
c ISO 2011 — All rights reserved v
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical com-
mittee has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates
closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical stan-
dardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Stan-
dards adopted by the technical committees are circulated to the member bodies for voting. Publication
as an International Standard requires approval by at least 75% of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
— an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical ex-
perts in an ISO working group and is accepted for publication if it is approved by more than 50%
of the members of the parent committee casting a vote;
— an ISO Technical Specification (ISO/TS) represents an agreement between the members of a tech-
nical committee and is accepted for publication if it is approved by 2/3 of the members of the
committee casting a vote.
An ISO/PAS or ISO/TS is reviewed every three years with a view to deciding whether it can be trans-
formed into an International Standard.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TS 15926-8 was prepared by Technical Committee ISO/TC 184, Automation systems and integra-
tion, Subcommittee SC 4, Industrial data.
ISO 15926 is organized as a series of parts, each published separately. The structure of ISO 15926 is
described in ISO 15926-1.
Each part of ISO 15926 is a member of the following series: data model, reference data, implementa-
tion methods, conformance testing methodology and framework, characterization methods, abstract test
suites. This part of ISO 15926 is a member of the implementation methods series.
A complete list of parts of ISO 15926 is available from the following URL:
http://www.tc184-sc4.org/titles/OIL_GAS_Titles.htm
vi
c ISO 2011 — All rights reserved
Introduction
ISO 15926 is an International Standard for the representation of process plant life-cycle information.
This representation is specified by a generic, conceptual data model that is suitable as the basis for
implementation in a shared database or data warehouse. The data model is designed to be used in
conjunction with reference data: standard instances that represent information common to a number
of users, process plants, or both. The support for a specific life-cycle activity depends on the use of
appropriate reference data in conjunction with the data model.
ISO 15926 is organized as a number of parts, each published separately. This part of ISO 15926 spec-
ifies the Web Ontology Language (OWL) implementation, using World Wide Web Consortium (W3C)
Semantic Web technologies.
This part of ISO 15926 deals with the translation of ISO/TS 15926-4 classes, reference data and the
ISO/TS 15926-7 template methodology to Resource Description Framework (RDF) and Web Ontology
Language (OWL), which can be used in data modelling, integration and interoperability methods. This
part of ISO 15926 is independent of infrastructure and test methods.
This part of ISO 15926 serves as the basis for data integration and interoperability infrastructure and test
methods.
This part of ISO 15926 addresses:
— the method of translating ISO/TS 15926-4 classes to RDF/OWL;
— the method of translating ISO/TS 15926-7 templates to RDF/OWL;
— the constructs of specialized templates;
— the use of object information models;
— the constructs of metadata.
Readers of this part of ISO 15926 require an understanding of conceptual data models and of
ISO/TS 15926-7.
The target audiences for this part of ISO 15926 are as follows:
— technical managers wishing to determine whether ISO 15926 is appropriate for their business needs;
— implementers wishing to make interface software between legacy systems and ISO 15926 compliant
systems;
— implementers wishing to make software internally ISO 15926-compliant for the purpose of data
integration.
In this part of ISO 15926, the same English language word might be used to refer to a real world thing, to
an EXPRESS representation of the real world thing, or to an RDF/XML representation of the real-world
thing. These uses are distinguished by the following typographic conventions:
c ISO 2011 — All rights reserved vii
— if a word or phrase occurs in normal typeface, it refers to the real-world thing;
EXAMPLE 1 cooling water pump
— if the word or phrase occurs in bold typeface with underscores, it refers to the EXPRESS represen-
tation from the ISO 15926-2 data model;
EXAMPLE 2 class of inanimate physical object
— if the word or phrase occurs in bold typeface and in CamelCase, it refers to a subtype axiom as
defined in ISO/TS 15926-7;
EXAMPLE 3 ClassOfInanimatePhysicalObject
— if the word occurs in italic typeface, it refers to an RDF/RDFS/OWL native entity type.
EXAMPLE 4 rdfs:subClassOf
References to identifiers in examples are fictitious.
viii
c ISO 2011 — All rights reserved
TECHNICAL SPECIFICATION ISO/TS 15926-8:2011(E)
Industrial automation systems and integration — Integration of
life-cycle data for process plants including oil and gas
production facilities —
Part 8:
Implementation methods for the integration of distributed
systems: Web Ontology Language (OWL) implementation
1 Scope
This part of ISO 15926 specifies implementation methods for integration, sharing, exchange, and hand-
over of life-cycle information about process plants, based on the data model of ISO 15926-2 and the
template methodology of ISO/TS 15926-7.
The following are within the scope of this part of ISO 15926:
— defining rules for applying RDF and OWL in the context of this part of ISO 15926;
— mapping of the data model of ISO 15926-2 from its EXPRESS format to OWL-2;
— defining a methodology for creating an OWL ontology for the ISO/TS 15926-4 reference data;
— defining an OWL ontology based on the base templates and the initial set of core templates;
— defining a methodology for creating an OWL ontology for “specialized templates” (see 2.1.32) that
defines the types of information for any given instance of possible individual during its lifetime.
The following are outside the scope of this part of ISO 15926:
— the specific type of rule language used to implement the first order logic;
— the decision as to whether data storage and exchange is done using lifted data or by use of lowered
template instances and objects only.
NOTE This is a business decision.
2 Terms, definitions, and abbreviated terms
2.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1.1
base template
template with only entity types in the expansion of its template axiom
[ISO/TS 15926-7:2011, definition 2.1.1]
c ISO 2011 — All rights reserved 1
2.1.2
class
category or division of things based on one or more critera for inclusion and exclusion
NOTE 1 A class need not have any known members (things that satisfy its criteria for membership).
NOTE 2 Because of the spatio-temporal paradigm used to define individuals in ISO 15926, all classes are non-well-founded
sets.
NOTE 3 Adapted from ISO 15926-1:2004, definition 3.1.1.
2.1.3
core class
class that is a commonly used subdivision corresponding to terms used in common language
NOTE The conditions for membership are often not formally defined; understanding of the class may be conveyed by exam-
ple.
EXAMPLE Pipe, floor, pump, and light bulb are all core classes.
[ISO 15926-1:2004, definition 3.1.4]
2.1.4
core template
RDL template for which all reference data items in the expansion of its template axiom are core classes
[ISO 15926-7:2011, definition 2.1.6]
2.1.5
data store
computer system that allows data to be stored for future reference
[ISO 15926-1:2004, definition 3.1.6]
2.1.6
data type
domain of values
[ISO 10303-11:2004, definition 3.3.5]
2.1.7
data warehouse
data store in which related data are merged to provide an integrated set of data containing no duplication
or redundancy of information, and which supports many di erent application viewpoints
[ISO 15926-1:2004, definition 3.1.7]
2.1.8
entity
class of information defined by common properties
[ISO 10303-11:2004, definition 3.3.6]
c ISO 2011 — All rights reserved
2.1.9
entity data type
representation of an entity
NOTE 1 An entity data type establishes a domain of values defined by common attributes and constraints.
NOTE 2 In this part of ISO 15926 the entity data types are as defined in the data model of ISO 15926-2.
NOTE 3 Adapted from ISO 10303-11:2004, definition 3.3.7.
2.1.10
entity instance
named unit of data which represents a unit of information within the class defined by an entity
NOTE 1 It is a member of the domain established by an entity data type.
NOTE 2 Adapted from ISO 10303-11:2004, definition 3.3.8.
2.1.11
first-order logic
symbolized reasoning in which each sentence, or statement, is broken down into a subject and a predicate
NOTE 1 The predicate modifies or defines the properties of the subject. In first-order logic, a predicate can only refer to a
single subject.
NOTE 2 First-order logic is also known as first-order predicate calculus or first-order functional calculus.
[ISO 15926-7:2011, definition 2.1.13]
2.1.12
individual
possible individual
thing that exists in space and time
NOTE 1 In this context, existence could be within the world we live in, or some “possible” world that can be imagined. This
therefore includes actual, hypothetical, planned, expected, or required individuals.
EXAMPLE A pump with serial number ABC123, Battersea Power Station, Sir Joseph Whitworth, and the Starship Enterprise
are examples of individuals.
NOTE 2 Adapted from ISO 15926-2:2003, definition 3.1.6.
2.1.13
individual template
template for making statements about individuals
[ISO/TS 15926-7:2011, definition 2.1.14]
2.1.14
instance
named value
[ISO 10303-11:2004, definition 3.3.10]
c ISO 2011 — All rights reserved 3
2.1.15
interoperability
ability of di erent types of computers, networks, operating systems, and applications to work together
e ectively, without prior communication, in order to exchange information in a useful and meaningful
manner
2.1.16
life-cycle information
information about a possible individual (2.1.12), collected at any point in time during the life-cycle of
that individual
NOTE Adapted from ISO/TS 15926-7:2011, definition 2.1.17.
2.1.17
Manchester syntax
user-friendlycompactsyntaxforOWL2ontologiesZKLFKisframe-based,asopposedtotheaxiom-
EDVHGothersyntaxesforOWL2
NOTE See Reference [21].
2.1.18
metadata
data that describes and defines other data
[ISO/IEC 11179-1:2004, definition 3.2.16]
2.1.19
N-triple
line-based, plain text format for encoding an RDF graph
2.1.20
object information model
OIM
ontology of classes and relations for which a particular class is singled out for characterization
NOTE In Description Logic terminology, it is a TBox (see Annex G).
2.1.21
ontology
formal representation of a set of concepts within a domain and the
relationships between those concepts
NOTE 1 Ontologies are usually used to reason about the properties of that domain, and can be used to define the domain.
NOTE2 Ontologiesareusuallyexpressedinalogic-basedlanguage,butthisisnotarequirement,neitheristheneedfor
reasoningcapability.Inadditiontorelationships,classes,properties,instancesandaxiomscanbeused.
2.1.22
OWL native
modelling style in which a relationship is expressed as an RDF predicate
c ISO 2011 — All rights reserved
2.1.23
punning
declaringaclassandanindividual,havingtheexactsameidentifier,inordertousethemindi erent
modelconstructions,ZKLFKwouldbeLOOHJDOtouseifappliedtooneobject
NOTE Punningcanalsobeappliedtotwopropertydeclarationsofdi erentpropertytypeV.
2.1.24
RDF graph
graph structure formed by a set of RDF triples
2.1.25
RDF schema
languagefordescribingvocabulariesinRDFZKLFKisasemanticextensionofRDF,providingmechanisms
IRUdescribinggroupsofrelatedresourcesandtherelationshipsbetweentheseresources
2.1.26
RDF/XML
format with an XML syntax for RDF, as defined in the W3C recommendation “RDF/XML Syntax Spec-
ification (Revised)”
2.1.27
reference data
process plant life-cycle data that represents information about classes or individuals which are common
to many process plants or of interest to many users
[ISO 15926-1:2004, definition 3.1.18]
2.1.28
reference data library
RDL
managed collection of reference data
[ISO 15926-1:2004, definition 3.1.19]
NOTE In this part of ISO 15926, “RDL” and “ontology” are used interchangeably.
2.1.29
reification
modelling style in which a relationship is expressed as an object class
EXAMPLE TherelationEmployed-byisreifiedbytheobjectEmploymentwhichisconnectedtotheobjectsEmployeeand
Organization.Themeaningoftherelationwithcardinalitiesatbothendsis“anorganizationhaszeroormoreemployees”.
ThereifiedEmploymentobjectcanbesubjectinotherrelations,definingit.
NOTE The relational entity data types of ISO 15926 are all the entity data types which have exactly two attributes, except
class of relationship.
[ISO/TS 15926-7:2011, definition 2.1.21]
2.1.30
signature
named, ordered and typed list of template roles
c ISO 2011 — All rights reserved 5
2.1.31
SPARQL endpoint
conformant to SPARQL protocol service as defined in W3C’s SPARQL Protocol for RDF (SPROT)
NOTE InReference[23],“endpoint”isdefinedas“AnassociationbetweenafullyspecifiedInterfaceBindingandanetwork
address, specifiedbyaURI[IETFRFC2396], thatmaybeusedtocommunicatewithaninstanceofaWebService. An
HndSointindicatesaspecificlocationforaccessingaWebServiceusingaspecificprotocolanddataformat.”
2.1.32
specialized template
set of statements about individuals or classes, that is subclass of a core template or another specialized
template, and which has one or more restrictions on its roles
2.1.33
taxonomy
collectionofcontrolledvocabularytermsorganizedinahierarchicalstructure,whereeachtermisinone
ormoreparent/child(broader/narrower)relationshiptoothertermsinthetaxonomy
2.1.34
template
set comprising of a first-order logic predicate for which a definition is stated as an axiom, a template
signature and a template axiom expansion
[ISO/TS 15926-7:2011, definition 2.1.22]
2.1.35
template
n-ary predicate, represented in OWL reified form as a class with one functional property (role) per
variable
2.1.36
template axiom
axiom in the template language defining the interpretation of template statements
[ISO/TS 15926-7:2011, definition 2.1.25]
2.1.37
template instance
ordered list of entity instances of which a template is true
NOTE 1 In OWL, the template instance is an individual with role relationships to the individuals that instantiate the template.
The atomic/ground statement is made by replacing the variables of the template with OWL individuals.
NOTE 2 Adapted from ISO/TS 15926-7:2011, definition 2.1.26.
2.1.38
template language
axioms in first-order logic extending the ISO 15926-2 data model
[ISO/TS 15926-7:2011, definition 2.1.27]
c ISO 2011 — All rights reserved
2.1.39
template role
named and numbered argument in a template with required type given as entity data type, data type, or
reference data class
NOTE Adapted from ISO/TS 15926-7:2011, definition 2.1.28.
2.1.40
template statement
statement made by instantiating the roles of a template with entity instances
[ISO/TS 15926-7:2011, definition 2.1.30]
2.1.41
core RDL
set of RDLs that only hold core classes and reference individuals
NOTE Part of the content is normalized.
2.1.42
triple
RDF triple
representation of a relation between the objects or data that it links
NOTE A triple comprises at least:
— an object called “subject”;
— a predicate (also called property) that denotes a relationship between a subject and an object;
— an object or data called “object”.
2.1.43
triple store
data store capable of storing triples (2.1.42)
2.1.44
value
unit of data
[ISO 10303-11:2004, definition 3.3.22]
2.2 Abbreviated terms
DL description logic
FOL first order logic
OIM object information model
OWL Web Ontology Language
RDF Resource Definition Framework
RDFS RDF Schema
c ISO 2011 — All rights reserved 7
RDL reference data library
SPARQL SPARQL Protocol and RDF Query Language
URI Uniform Resource Identifier
W3C World Wide Web Consortium
XML eXtensible Markup Language
3 Fundamental concepts and assumptions
3.1 General
The ISO 15926-2 data model is generic and highly normalized. Whilst this enables considerable flexi-
bility in what can be said, it can also give rise to complexity in how it is said. ISO/TS 15926-7 specifies
templates that are expressions of predefined units of semantics allowing the use of the model in a conve-
nient way.
This part of ISO 15926 translates these templates to OWL constructs, which can be used to perform
information storage, data integration, information exchange and interoperability.
3.2 ISO/TS 15926-7 templates and first order logic rules
The ISO 15926-2 data model defines the foundation concepts. These are represented by a generic,
conceptual data model that is suitable as the basis for implementation in a shared database or data ware-
house. The data model is designed to be used in conjunction with reference data: standard instances that
represent information common to a number of users, process plants, or both. The support for a specific
life-cycle activity depends on the use of appropriate reference data in conjunction with the data model. In
ISO/TS 15926-7, these are translated into first order logic, with EXPRESS entity data types represented
as unary predicates and EXPRESS attributes represented as binary predicates.
For this part of ISO 15926, template signatures are the basic structuring elements. In this part of
ISO 15926, the template signatures are translated to OWL, with reference to rules fulfilling the first
order logic.
3.3 ISO/TS 15926-4 reference data
ISO/TS 15926-4 provides reference data that defines a taxonomy of core classes representing the appli-
cable entity data types defined in ISO 15926-2.
For this part of ISO 15926, reference data is treated as constant terms for use in rules.
NOTE With this approach of having the attributes pointing at reference data instantiating the entity data types, the rule
equations are simplified.
3.4 User-defined taxonomy
A user often needs to define discipline-specific concepts in the form of specializations of ISO/TS 15926-4
taxonomy core classes.
c ISO 2011 — All rights reserved
EXAMPLE CP-834833 “Model 4HM pump”, a specialized class in the supplier catalog of the XYZ Corporation. The
rdfs:subclassOf relation points at the class “Centrifugal Pump” in the Core RDL.
3.5 Templates and specialized templates
Templates (see Clause 7) and specialized templates (see Clause 8) defined in this part of ISO 15926 and
in user-defined specializations, form the “derived concepts” as described in ISO/TS 15926-7.
3.6 Use of OWL
This part of ISO 15926 is based on the use of RDF, RDFS, and OWL.
Annex C specifies rules for the use of these languages in the context of this part of ISO 15926.
NOTE RDF, RDF Schema, and OWL allow for various ways to represent the same semantics. In order to make the code
more transparent and understandable, certain rules are necessary. These do not impede any linking to RDF/OWL vocabularies
that are using OWL in a di erent manner.
3.7 Namespaces
An ISO 15926 reference data system using OWL is divided into a set of ontologies, corresponding to
namespaces.
Table 1 shows the namespace prefixes with namespace URIs that are used for the examples in this part
of ISO 15926, which are under the control of the World Wide Web Consortium.
namespace namespace URI description
prefix
owl http://www.w3.org/2006/12/owl2-xml# OWL version 2
rdfs http://www.w3.org/2000/01/rdf-schema# RDF Schema
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns# Resource Description Framework
xsd http://www.w3.org/2001/XMLSchema# XML Schema
Table 1 — URIs under control of the World Wide Web Consortium
Table 2 shows the namespace prefixes with namespace URIs that are used for the examples in this part
of ISO 15926.
c ISO 2011 — All rights reserved 9
namespace namespace URI description
prefix
dm http://standards.iso.org/iso/ts/15926/-8/ed- Normative OWL classes, according
1/tech/reference-data/data-model# to the ISO 15926-2 data model and
with some extensions.
p7tm http://standards.iso.org/iso/ts/15926/-8/ed- Normative OWL declarations for
1/tech/reference-data/p7tm# templates and template roles (p7
means ISO/TS 15926-7).
p7tpl http://standards.iso.org/iso/ts/15926/-8/ed- Templates defined in
1/tech/reference-data/p7tpl# ISO/TS 15926-7, proto-templates
and “initial set” core templates. (p7
means ISO/TS 15926-7).
meta http://standards.iso.org/iso/ts/15926/-8/ed- Metadata.
1/tech/reference-data/metadata#
Table 2 — Namespaces that are used for the examples in this part of ISO 15926.
NOTE 1 The dm, p7tm, p7tpl and meta are files and not SPARQL endpoints. This is because given that these declarations
are immutable, it can be assumed these files will be locally cached by implementing systems. These files are present on the
CD-ROM of this part of ISO 15926.
NOTE 2 The following namespace (prefixes) with example.org addresses are used for the examples in this part of ISO 15926.
— rdl – http://rdl.example.org# – an endpoint having normative core classes and reference individuals, normalization-
candidate classes, and specialized templates, known as the core reference data library “Core RDL”;
— company1 – http://rdl.example.com# – an endpoint having examples of instances, specialized templates and classes, so
to serve as example of a company’s RDF store.
NOTE 3 The example namespaces are given the example.org and example.com addresses to show clearly that they are exam-
ples and therefore non-dereferencable. Also, the rdf:ID and rdf:about properties are made-up examples expressed in human-
readable wording instead of the letter-numeric IDs that they will be in practice.
EXAMPLE 1 In Manchester syntax:
Prefix: xsd:
Prefix: owl:
Prefix: rdf:
Prefix: rdfs:
Prefix: dm:
Prefix: p7tm:
Prefix: p7tpl:
Prefix: meta:
Prefix: rdl:
Prefix: steplib:
Prefix: pca:
Prefix: company1:
EXAMPLE 2 When code examples are used, the RDF heading is omitted. The following is an example of a heading:
c ISO 2011 — All rights reserved
]>
xml:base="http://rdl.example.com"
xmlns:owl="&owl;"
xmlns:xsd="&xsd;"
xmlns:rdf="&rdf;"
xmlns:rdfs="$rdfs;"
xmlns:dm="&dm;"
xmlns:p7tm="&p7tm;"
xmlns:p7tpl="&p7tpl;"
xmlns:meta="&meta;"
xmlns:rdl="$rdl;"
xmlns:steplib="&steplib;"
xmlns:pca="&pca;"
xmlns:company1="&company1;"
>
This ontology provides instances for
various examples of specialized templates.
These ontologies are interdependent, in the sense that one ontology will make use of classes defined
in another. Figure 1 shows the dependencies, an arrow between prefixes representing an owl:imports
relationship.
c ISO 2011 — All rights reserved 11
Figure 1 — Dependencies between ontologies
NOTE 4 In this part of ISO 15926, there are no namespace declarations for OIMs. An OIM should be viewed as informal
guides to usage rather than as an ontology in the OWL sense. This does not rule out representing OIMs as reference data
modules and making them referable in a SPARQL endpoint. However, for clarifying the OWL/RDF representation of templates,
normative representations of OIMs are not needed.
NOTE 5 Any of the namespaces shown in Figure 1 may be importing the meta namespace, as any thing can have metadata.
4 ISO 15926-2 data model
Based on the rules in Annex C, the data model of ISO 15926-2 has been mapped to OWL classes. It is
defined in the OWL ontology for data model.
In Annex D, a link to the normative RDF/XML listing for the data model is given.
5 ISO/TS 15926-4 reference data
Reference data shall be represented as specified in Annex E.
c ISO 2011 — All rights reserved
NOTE ISO/TS 15926-4 contains reference data relevant to this part of ISO 15926.
6 OWL template specifications
6.1 General
A template specification (for templates see Clause 7) contains all the information that is necessary:
— for a human being to understand the content of instances of the template;
— to create the OWL and rules listing for the template, that is added to the ontology for templates (see
ISO/TS 15926-7).
When a template is defined, it shall be in the format of template specifications as defined in 6.2.
For a link to an initial set of template specifications, see Annex F.
6.2 Contents
The contents of a template specification shall be:
— template name: a unique English CamelCase identifier of the lifted and lowered template (see 7.1
for lifted and lowered);
— name: the label of the template;
— intent: a brief description of the circumstances in which the template can be used;
— description: a full description of the semantics of the template.
— lifted and lowered graph: a graph that shows how the lifted template collects the nodes of the scope
graph, and how the lowered template refers to the variant nodes of the lifted template;
— lifted template elements: an alphabetically ordered list of the URIs of all nodes as collected by the
lifted template, with the applicable “elements” numbers;
— OWL code for lowered template: link to OWL ontology for templates;
— specification in First Order Logic - a first-order logic-based specification for the formalization of
the lifted and the lowered template;
— sample lowered template instance: a sample instance of the lowered template in RDF/XML format;
— definition of properties for lowered template: a list of the properties of the lowered version of the
template with a description of their rdf:objects.
NOTE For the lifted and lowered graphs a representation, as customary in the domain of RDF [24], or Manchester syntax
[21] can be used.
c ISO 2011 — All rights reserved 13
7 Templates
7.1 General
For the purpose of this part of ISO 15926, information is represented as a complex relationship between
independent objects. That complex relationship can be binary or n-ary.
The binary relationship is formed by an RDF triple’s predicate.
EXAMPLE The relationship specialization is formed by rdfs:subClassOf. The relationship classification is formed by
rdf:type.
The n-ary relationship is formed by a template and the independent objects are referred to as “external
references”.
Templates come in pairs:
— a lifted template (see 7.4), and
— a lowered template (see 7.5).
Where the lowered template provides the structure for data to be exchanged using the template, and the
lifted template provides a definitional mapping of the lowered template to the data model and reference
data of ISO 15926.
NOTE When just the word template is used, it is always a lowered template.
7.2 Template model
A template instance is member of a specialized template, by the rdf:type relationship.
A specialized template is a subclass of a specialized template or a core template, by the rdfs:subclassOf
relationship.
A core template is a subclass of a template class, by the rdfs:subclassOf relationship.
A template class is a subclass of the Multidimensional Object class, by the rdfs:subclassOf relationship.
A template class is a subclass of the Information Representation class, by the rdfs:subclassOf relation-
ship.
The Multidimensional Object class is of entity data type class of multidimensional object, which has
the following attributes:
— cardinalities : OPTIONAL LIST [1:?] OF cardinality;
— optional element : LIST [1:?] OF BOOLEAN;
— parameters : OPTIONAL LIST [1:?] OF thing;
— parameter position : OPTIONAL LIST [1:?] OF INTEGER;
— roles : LIST [1:?] OF role and domain.
c ISO 2011 — All rights reserved
NOTE Template class is more restricted than Multidimensional Object because ISO 15926-2 defines optional lists parameters
and parameter position, which are not used for templates. For the Information Representation class, there are no optional
arguments in templates and the parameters and parameter position lists are not used.
How it all fits together is shown in a series of examples (see Annex H).
7.3 Metadata
Classes, individuals or templates can have metadata.
NOTE Some metadata elements will be normalized in ISO/TS 15926-6, which is under preparation.
The following metadata elements for template instances are added in this part of ISO 15926:
— annRule;
— annAccessCode.
See Table F.2 for the definition of this metadata. The full set of metadata elements and their translation
to OWL is given in Annex F.
7.4 Lifted templates
Lifted templates serve as a reference for the exact semantics of the lowered templates.
The instantiated lowered templates are lifted by using the First Order Logic axiom listed in the template
specification.
NOTE 1 Lifted templates can be instantiated for reasons including, but not limited to the following:
— if the exchange format is done in full lifted format;
— for validation of entity data types of data connected to the template;
— if the full semantics it provides is required as subject for Semantic Web reasoning;
— if a mapping to a format, defined in ISO 10303-21 (so-called “Part 21 files”) would be required;
— if data needs to be mapped between templates where there would not be a handle available in lowered templates.
Lifted data can exist without the use of the lifted template information and metadata. Lowering such
data will require pattern matching. H
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...