In ISO 15926-8 rules are given for Template Specifications. In the course of the years close to 200 such specifications have been made, for the most based on actual mapping requirements, lately from the CFIHOS data model.
The Template Specifications can be found here.
These specifications have been made with due care, but they are not yet a formal part of ISO 15926-8. In case you find an error or have an improvement proposal, please let us know.
Template Specifications define a ClassOfTemplate. They are elementary ontologies, of which template instances are members.
Each specification, in XML, has the following data fields:
TEMPLATE NAME - the label and the ID of the Template Class, of which this is an example instance:
ex:4478ca0a-0d97-4417-9c86-a943290d41f6 rdf:type tpl:DescriptionOfIndividual ; etcDEFAULT RDS ID - a UUID for admin purposes.
STATUS - the start status for the Update Log in UPDATED MAR2023. Deprecated specs will remain in the list, with status DEPRECATED plus the yearMonth of deprecation. In case a deprecation would cause a problem, please contact us.
MEMBER OF - a superclass template, can be used only for selection purposes.
TIP PREDICATE - a generic predicate, that is intended to play a role in mapping.
DESCRIPTION - a plain(ish) English description of the template scope. Note that these descriptions have been simplified for quick reference. Statements like 'a temporal part of an instance of' have been omitted. However, in most cases this is still the valid text, which now has to be understood from the template graph.
REPRESENTED INFORMATION - this is a kind of template for the (optional) generation of an English description of the semantics of the template, where the [template role]s shall be replaced with the label of the referred class or individual, or with the given Literal value.
EXAMPLE - an example that demonstrates a use of the template.
NOTES - in most cases used for an instruction to add the meta:valEffectiveDate with dateTime value. But other notes may occur.
SCOPE NOTE - a note that gives information about a way or circumstance to apply the template.
ADMIN NOTE - an internal note for admin purposes.
LIFTED AND LOWERED GRAPH - the graph of the template, which is a combination of lifted and lowered graph, where 'lifted' refers to the actual graph using ISO 15926-2 entity types and, in some cases, an ISO-15926-4 reference class. A 'Lowered' template is referred to as 'Template'. The graph is for human interpretation only.
LIFTED TEMPLATE ELEMENTS - a complete list of the entity types used for the construction of the template. These have no hyperlink.
DEFINITION OF PROPERTIES OF LOWERED TEMPLATE - this is also called the "signature" of the template, with the predicates and the required rdfs:objects. This is used to generate SHACL 'shapes' for mapping validation.
SPECIFICATION IN FIRST-ORDER LOGIC - the lifted template expressed in FOL. Has not yet been used, perhaps when AI further evolves.
SAMPLE OF LOWERED TEMPLATE INSTANCE - first a generic version that can be used to quickly generate template instances. Note: This is in fact a representation of a Template Class, where something like "ID"^^dm:PossibleIndividual means that an ID (UUID or RDL ID) is expected, and that ID shall be of an instance of the given Part 2 entity type.
This is followed with a repeat of above EXAMPLE and the signature of an instance of that Template Class, filled with the applicable instances of the referenced entity types and Literals.