Below reference is being made to "new" TIPs that cover the "old" TIPs of iRING, and that are mapped to either one specialized template or in a set of interrelated specialized templates.
Here a cross-reference can be found between the iRING TIPs and the corresponding new TIPs.
The yellow part of a TIP is what the mapper sees, the rest is to be generated based on that input.
The TIP variables are generic and of the format var_XxxxYyyyyy
The generated, or if existing: used, GUIDs are preceded with a T (of Thing, OWL for Individual) or a C (of Class), because GUIDs may start with a number and that is not allowed.
Identifiers like :CdeclaredGUID1 are to be replaced with something like :C46AF12DE319F4D788751306FB90304BE , preferably using GUIDs. (the : in front denotes the namespace in which the identifier is placed, for example:
@prefix : <http://data.xyz.org/p1234/> . # just a fantasy URI for project p1234 of the XYZ inc.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> . # defines Literals (text, dateTimes, numbers, etc)
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> . # defines metadata
@prefix meta: <http://data.15926.org/meta/> . # defines ISO 15926-specific metadata
@prefix dm: <http://data.15926.org/dm/> . # defines the ISO 15926-2 data model
@prefix edm: <http://data.15926.org/edm/> . # defines an extension of the ISO 15926-2 data model
@prefix tpl: <http://data.15926.org/tpl/> . # defines the ISO 15926-7 templates
@prefix rdl: <http://data.15926.org/rdl/> . # defines the ISO 15926-4 reference data
@prefix xyzrdl: <http://data.xyz.org/rdl/> . # just a fantasy URI for an RDL extension of the XYZ inc.
Any person doing the mapping always works with tag numbers, or serial numbers, or asset numbers, etc, depending on the context; see TIP0001.
The TIP numbers ending on C are for Classes, and ending on T for Things (Individuals).
Any TIP is the top of its iceberg. TIPs are there to provide a link between an engineer with his software that has a lot of implicit information, and the world of explicit integrated lifecycle information, which at times is rather verbose.