| Standard or Recommendation | Description | URI | Status |
| ISO 15926 parts | |||
| Part 1 - Overview and fundamental principles | Specifies a representation of information associated with engineering, construction and operation of process plants. This representation supports the information requirements of the process industries in all phases of a plant's life-cycle and the sharing and integration of information amongst all parties involved in the plant's life cycle. | click here | International Standard |
| Part 2 - Data Model | Is a part of ISO 15926, an International Standard for the representation of process plant life-cycle information. This representation is specified by a generic, conceptual data model designed to be used in conjunction with reference data. | click here | International Standard |
| Part 3 - Reference data for geometry and topology | Specifies geometric and topological concepts, enabling the recording of geometric and topological data using ISO 15926-2 and in a way consistent with first order logic. Also specifies concepts related to mesh topology and functions defined with respect to meshes, enabling the recording of mesh topology data and the representation of property distributions. |
click here | Technial Specificaion |
| Part 4 - Reference data | Specifies a set of core reference data items which can be used to record information about process plants, including oil and gas production facilities. | click here | Technial Specificaion |
| Part 6 - Methodology for the development and validation of reference data | Defines a methodology for the stewarding of reference data for process plants. | click here | Technial Specificaion |
| Part 7 - Template methodology | Is a specification for data exchange and life-cycle information integration using templates based on the data model of ISO 15926-2. Provides a methodology for data integration of ontologies using mathematical first-order logic, which makes it independent of computer languages. |
click here | Technial Specificaion |
| Part 8 - Web Ontology Language (OWL) implementation | Is a specification for data exchange and life-cycle information integration using Resource Description Framework (RDF) and Web Ontology Language (OWL). 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. |
click here | Technial Specificaion |
| Part 9 - ISO 15926-8 API for RDF store | An API for an RDF store, that manages the contents in an ISO 15926-8 manner. | click here | under development |
| Part 10 - Conformance Testing | Defines the principles and methods for conformance testing of software implementations of ISO 15926. It provides guidance for developing test cases and testing procedures that cover the requirements specified in the ISO 15926 series and in different industry usage contexts, e.g. data exchange, use of reference data libraries and interface services. | click here | Technial Specificaion |
| Parts 11 thru 14 | These parts are not applicable for this website. | --- | Technial Specificaion |
| W3C Publications | |||
| Architecture of the World Wide Web, Volume One | The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support. | click here | W3C Recommendation |
| Defining N-ary Relations on the Semantic Web | Presents ontology patterns for representing n-ary relations in RDF and OWL. This document formed the basis for the ISO 15926-7 templates. Use case #3 applies. | click here | W3C Working Group Note |
| XML Schema Part 2: Datatypes Second Edition | In the context of ISO 15926 it defines Literals, that come, in implementations, in lieu of the Express counterparts. | click here | W3C Recommendation |
| RDF 1.1 Primer | Provides the reader with the basic knowledge required to effectively use RDF. It introduces the basic concepts of RDF and shows concrete examples of the use of RDF. Sections 3-5 can be used as a minimalist introduction into the key elements of RDF. | click here | W3C Working Group Note |
| RDF 1.1 Semantics | Describes a precise semantics for the Resource Description Framework 1.1 and RDF Schema. It defines a number of distinct entailment regimes and corresponding patterns of entailment. It is part of a suite of documents which comprise the full specification of RDF 1.1. | click here | W3C Recommendation |
| RDF 1.1 Turtle | Defines a textual syntax for RDF called Turtle that allows an RDF graph to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle provides levels of compatibility with the N-Triples format as well as the triple pattern syntax of SPARQL. | click here | W3C Recommendation |
| OWL 2 Web Ontology Language Primer (Second Edition) | OWL 2 is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. This primer provides an approachable introduction to OWL 2, including orientation for those coming from other disciplines, a running example showing how OWL 2 can be used to represent first simple information and then more complex information, how OWL 2 manages ontologies, and finally the distinctions between the various sublanguages of OWL 2. |
click here | W3C Recommendation |
| SPARQL 1.1 Overview | An overview of SPARQL 1.1. It provides an introduction to a set of W3C specifications that facilitate querying and manipulating RDF graph content on the Web or in an RDF store. | click here | W3C Recommendation |
| SPARQL 1.1 Query Language | Defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports aggregation, subqueries, negation, creating values by expressions, extensible value testing, and constraining queries by source RDF graph. The results of SPARQL queries can be result sets or RDF graphs. | click here | W3C Recommendation |
| R2RML: RDB to RDF Mapping Language | Is a language for expressing customized mappings from relational databases to RDF datasets. Such mappings provide the ability to view existing relational data in the RDF data model, expressed in a structure and target vocabulary of the mapping author's choice. R2RML mappings are themselves RDF graphs and written down in Turtle syntax. R2RML enables different types of mapping implementations. Processors could, for example, offer a virtual SPARQL endpoint over the mapped relational data, or generate RDF dumps, or offer a Linked Data interface. | click here | W3C Recommendation |
| Other standards | |||
| OWL API | In the OWL API is an OWLOntology, that is an interface, modelling a set of logical and nonlogical OWLAxioms, with a name (an IRI), an (optional) physical location and convenience methods to retrieve such axioms. | click here and here | Industry Standard |
| OAuth | The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. | click here and here | rfc6749 |
Standards
latest update 2023-03-10 
