Version 4 (modified by jbourne, 13 years ago)



Intelligent Data Sets Accelerating Deployment of ISO15926

Realizing Open Information Interoperability

RDS/WIP Template Definitions

This page is about the minimum requirements for template definition in the RDS/WIP. At the time of writing, it is too early to cast the RDF/OWL representation in stone, since this will require further work on the base templates first.


The main purpose is to collect requirements and propose at least an interim XML format for cooperation and collaboration amongst the IDS-ADI team. This format will have a published transformation to RDF/OWL using XSLT (free of mapping).


The format, the transform, and the RDF/OWL representation are manifestly experimental: the intent of this initiative is to discover through use any problems in the model to feed into the development process of the standardized representations. The XML representation is not ever intended to be normative ISO 15926, although it may evolve into an acceptable general input format for the RDS/WIP, subsequent to an acceptable RDF/OWL transform.

Requirements and Limitations

These requirements outline what we (the IDS-ADI team) need in order to cooperate and collaborate on template definition: these requirements explicitly do not specify minimum requirements for template definition in ISO 15926: that is a separate issue.

IETF RFC2119 describes the usage of several key words on this page and in associated discussions:

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Template Definition

A template definition MUST include:

  • a unique identifier;
  • a super class;
  • two or more roles;
  • an RDS/WIP status; and
  • provenance data.

A template definition SHOULD include:

  • names, not necessarily unique, in one or more languages; and
  • descriptions, not necessarily unique, in one or more languages.

A template definition MAY include:

  • other classifications (for grouping);
  • zero or more other statuses.

Role Definition in a Template Definition

A role definition in a template definition MUST include:

  • property for role;
  • range of role value in instantiated template (ie. class);
  • position in the sequence of roles in the instantiated template; and
  • identifier that is unique amongst the roles in the template definition.

A role definition in a template SHOULD include:

  • indication if optional or mandatory (see notes 1 & 2).

A role definition in a template MAY include:

  • names, not necessarily unique, in one or more languages; and
  • descriptions, not necessarily unique, in one or more languages.


  1. The cardinality of a role in an instantiated template must be zero or one.
  2. In the case of a mandatory role, that means the cardinality is always one.
  3. At the atomic and core template levels, it likely will be better to make a template optional than a role optional.

Property Definitions

A property definition MUST include:

  • an identifier;
  • a range restriction as an entity type; and
  • an RDS/WIP status;
  • provenance data (not yet defined).

A property definition SHOULD include:

  • names, not necessarily unique, in one or more languages; and
  • descriptions, not necessarily unique, in one or more languages.

A property definition MAY include:

  • a range restriction as a value class; and
  • zero or more other statuses.

Statuses for Template and Property Definitions

As above, both template definitions and property definitions MUST have RDS/WIP status information and MAY have additional status information.

Status information MUST include:

  • the organization making the status;
  • the date/time from when the status applies;
  • the date/time to when the status applies;
  • the scheme of the status; and
  • the status value itself.

Note: status in ISO 15926 will not be nearly so "flat", likely being expressed as temporal class membership with many other relationships.

Template Definition Extension

Templates definitions may "extend" (that is, subclass) other template definitions. When a template definition extends another template definition, it "inherits" the roles (but not the provenance, names, descriptions and statuses).

@todo consider how extension affects role order, how extension affects OWL/RDF queries (must a template be able to be easily treated as its more generic form?).

Template Definition Obsolescence

@todo consider if obsolescence can/should be completely handled by status. Consider if obsolescence requires abstract super classes that can group a set of succeeding templates as a replacement for the obsolesced template. What about when one template obsolesces a group of templates? Lots to consider - must be supported or ruled out.


@todo look into Magne's work in Part 6 referencing other ISO standards.

XML Format

@todo flesh out a representation as extension language to QXF maybe (a la QTXF), since this already has an OWL/RDF mapping. Would we need to be able to generate QTXF from the definitional format?

@note DNV's IRM unit also have their own internal XML format for defining templates - we should see if that works.


You have no rights to see this discussion.

About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std