TIP0001 - Declaration and Identification

latest update: 2017-02-26    

TIP0001 - Declaration and Identification

NARRATIVE

All things, that are involved in any information, shall first be declared and identified as "Ur" objects (see https://en.wiktionary.org/wiki/ur-). The idea can be explained using the pump P-101 as an example.

We start with declaring a PUMP, and identifying it with "P-101". This object will exist until it is ended (individuals) or deprecated (classes), and it will not have any information attributed to it other than through its temporal parts. It can be qualified as an immutable "anchor".  The identifier may, at a later time, be changed, although this is an exception. For that reason this identification at declaration time is done with a template rather than with an rdfs:label.

NOTE - The fact that this anchor object is made a variable in all templates in which actually one of its temporal parts plays a role is because those temporal parts are being hidden in the internals of the templates. The reason for that is that commercial software doesn't know of temporal parts. These temporal parts can only be made explicit by means of a "lifted" template, as defined in Part 12.

It is like a car with a chassis number "1HG CM8263 3A004352" . Even when, during its lifetime, all parts have been replaced, that car remains "1HG CM8263 3A004352" , the anchor object, where these replacements are being attributed to temporal parts of that Ur object. The license plate number of that car, however, can be replaced with another one.

In case the Ur object is deprecated, all its temporal parts are ended | deprecated (in case this wasn't already the case) and all templates in which these ended | deprecated temporal parts play a role are being deprecated (in case this wasn't already the case).

All objects, including the Ur objects, shall have an immutable ID that always stays with that object. It is advisable to use GUIDs for that, because these are globally unique, with a neglecible chance of duplication, even more so because they are used inside a, guaranteed unique, namespace.

There are many flavors of UUID/GUID. A GUID without hyphens has an advantage of being accepted as bookmark in HTML applications.

Next to the GUID many things get one or more user-memorizable identifiers, such as tag number, serial number, asset number, line number, equipment number, etc. These identifiers are, in the context of ISO 15926, of utmost importance, because they are the starting point of most queries. Therefore a consistent format of them is important. This is why the identification is "classified" with an "identification type" that can be found in an RDL, but most probably in a local RDL extension, where the identifier format rules of the owner company are being spelled out.

The GUID can easily be fetched with a simple SPARQL query using an identifier as search criterium and hence doesn't have to be stored in the source system.

The "Declaration Class" is important and shall be selected carefully. It is the class of which the declared OOI (Object Of Interest) is a subclass (if the OOI is a class) or a member (if the OOI is an Individual). It is the class that is ALWAYS valid as long as the OOI hasn't been deprecated. If the Declaration Class is changed the OOI is no longer valid and all information is frozen. So use PUMP and not CENTRIFUGAL PUMP, because it may change to POSITIVE DISPLACEMENT PUMP. Granted, it isn't likely to happen, but better safe than sorry. Later the specialization or classification with CENTRIFUGAL PUMP can be done with a template which can, when necessary, be deprecated and changed to POSITIVE DISPLACEMENT PUMP with a new template. The anchor remains PUMP then.

In the RDL (Reference Data Library) a set of generic identification types has been defined and may be extended if needed.

INPUT

ISO 15926-2 entity type: var_EntityType  (from picklist per detailed TIP0001 variant below)

OOI is a specialization (if class) or a member (if individual) of the "Declaration Class": var_ObjectType

Value of identifier: var_IdentOfOOI  (e.g. B14-V101 )

Identification type: var_IdentType  (from picklist, see below)


TIP0001C - Declaration and Identification (Classes)

NARRATIVE

All instances of ClassOfIndividual have one or more user-memorizable identifiers, although this not (yet) customary. In the topics of this website we have adopted prefixing the identifier of a member individual with CO_ , meaning ClassOf_ . But other prefixes are possible.

A(n instance of a subtype of) ClassOfIndividual gets a user-memorizable identifier of a var_IdentType that is selected from the picklist.

The OOI (Object Of Interest) that is identified shall be of the var_EntityType and var_ObjectType given in the picklist.

NOTE - This identification is purely of the class, not of its members.

SIGNATURE

PICKLIST

Select var_IdentType from the following (add or delete per application):

IDENTIFICATION BY

var_IdentType

use

OOI shall be a

var_EntityType

OOI shall be a

subclass of

var_ObjectType

label ofvar_ObjectType   (for information only)

ACTIVITY NUMBER

rdl:RDS2229905

dm:Activity & dm:ActualIndividual

 

(Individual only)

ACTIVITY TAG

rdl:RDS2229976

dm:ClassOfActivity

dm:Activity

Activity

ASSET NUMBER

rdl:RDS2221102

dm:ClassOfInanimatePhysicalObject

rdl:RDS422594

ARTEFACT

BUILDING NUMBER

rdl:RDS2221098

dm:ClassOfInanimatePhysicalObject

rdl:RDS9691217

BUILDING

CABLE NUMBER

rdl:RDS2221103

dm:ClassOfInanimatePhysicalObject

rdl:RDS2229989

CABLE

CONSTRUCTION AREA NUMBER

rdl:RDS2221097

edm:ClassOfSpatialLocation

rdl:RDS2229165

CONSTRUCTION AREA

DOCUMENT NUMBER

rdl:RDS2221088

dm:ClassOfInformationObject

rdl:RDS3333040

DOCUMENT

EMPLOYEE NUMBER

rdl:RDS2223095

dm:ClassOfPerson

rdl:RDS2229218

EMPLOYED PERSON

MODEL NUMBER

rdl:RDS2229916

dm:ClassOfInanimatePhysicalObject

rdl:RDS422594

ARTEFACT

ORGANIZATION NAME

rdl:RDS2229785

dm:ClassOfOrganization

edm:Organization

Organization

PLANT NUMBER

rdl:RDS2221095

dm:ClassOfInanimatePhysicalObject

rdl:RDS7151797

PLANT

PROCESS UNIT NUMBER

rdl:RDS2221096

dm:ClassOfInanimatePhysicalObject

rdl:RDS2229214

PROCESS UNIT

PROJECT CODE

rdl:RDS2229781

dm:ClassOfActivity

rdl:RDS9629

PROJECT

PROJECT NAME

rdl:RDS2229780

dm:ClassOfActivity

rdl:RDS9629

PROJECT

ROAD NUMBER

rdl:RDS2221100

dm:ClassOfInanimatePhysicalObject

rdl:RDS2229219

ROAD

SERIAL NUMBER

rdl:RDS2221101

dm:MaterializedPhysicalObject

 

(Individual only)

SOCIAL SECURITY NUMBER

rdl:RDS2223096

edm:Person

 

(Individual only)

STATEMENT NUMBER

rdl:RDS2229909

dm:ClassOfInformationRepresentation

rdl:RDS2229083

STATEMENT

STRUCTURAL FRAMEWORK NUMBER

rdl:RDS2221099

dm:ClassOfInanimatePhysicalObject

rdl:RDS815080531

STRUCTURAL FRAMEWORK

TAG NUMBER

rdl:RDS2221089

dm:ClassOfInanimatePhysicalObject

--- *)

 

          COATING LAYER TAG

rdl:RDS2229901

dm:ClassOfInanimatePhysicalObject

rdl:RDS738306981

COATING LAYER

          ELECTRICAL TAG

rdl:RDS2221091

dm:ClassOfInanimatePhysicalObject

rdl:RDS497678601

ELECTRICAL APPARATUS

          PROCESS EQUIPMENT TAG

rdl:RDS2221090

dm:ClassOfInanimatePhysicalObject

rdl:RDS422594

ARTEFACT

          FUNCTION TAG

rdl:RDS2229975

dm:ClassOfFunctionalObject

edm:FunctionalObject

FunctionalObject

          HEAT TRACING SYSTEM NUMBER

rdl:RDS2229903

dm:ClassOfInanimatePhysicalObject

rdl:RDS267434

 HEAT TRACING SYSTEM

          INSTRUMENT TAG

rdl:RDS2221092

dm:ClassOfInanimatePhysicalObject

rdl:RDS934064

PROCESS INSTRUMENTATION ITEM

          INSULATION TAG

rdl:RDS2229902

dm:ClassOfInanimatePhysicalObject

rdl:RDS328094

INSULATION TAG

          LINE NUMBER

rdl:RDS2221093

dm:ClassOfInanimatePhysicalObject

rdl:RDS270359

PIPING NETWORK SYSTEM

          NOZZLE NUMBER

rdl:RDS2229955

dm:ClassOfInanimatePhysicalObject

rdl:RDS415214

NOZZLE

          STREAM NUMBER

rdl:RDS2221094

edm:ClassOfStream

dm:Stream

Stream

          SUPPORT NUMBER

rdl:RDS2229904

dm:ClassOfInanimatePhysicalObject

rdl:RDS6728598

SUPPORT

--- *) do not use, but use a specialization  

 

GENERATED CODE

  

# DECLARED OBJECTS (check existence and if not existing: declare)

  

# Declaration of identified class of individual

  

<CGUID1>  rdf:type <var_EntityType> ; # from Picklist

    rdfs:subClassOf <var_ObjectType ; # from Picklist

    rdfs:label  "var_IdentOfOOI" ;

    meta:valEffectiveDate "var_dateTime"^^xsd:dateTime .

  

<TGUID2> rdf:type tpl:ClassifiedIdentificationOfClassOfIndividual ;

    tpl:hasIdentified <GUID1>;

    tpl:valIdentifier "var_IdentOfOOI" ;

    tpl:hasIdentificationType <var_IdentType> ; # from picklist

    meta:valEffectiveDate "var_dateTime"^^xsd:dateTime .  

  

MAPPING TO TRIPLES

  

<CGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <var_EntityType> .

<CGUID1> <http://www.w3.org/2000/01/rdf-schema#subClassOf> <var_ObjectType> .

<CGUID1> <http://www.w3.org/2000/01/rdf-schema#> "var_IdentOfOOI" .

<CGUID1> <http://data.15926.org/meta/valEffectiveDate> "var_dateTime"^^<http://www.w3.org/2001/XMLSchema#dateTime> .

  

<TGUID2> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://data.15926.org/tpl/ClassifiedIdentificationOfClassOfIndividual> .

<TGUID2> <http://data.15926.org/tpl/hasIdentified> <CGUID1> .

<TGUID2> <http://data.15926.org/tpl/valIdentifier> "var_IdentOfOOI" .

<TGUID2> <http://data.15926.org/tpl/hasIdentificationType> <var_IdentType> .

<TGUID2> <http://data.15926.org/meta/valEffectiveDate> "var_dateTime"^^<http://www.w3.org/2001/XMLSchema#dateTime> .

CHECKING WHETHER AN OBJECT HAS ALREADY BEEN DECLARED

Procedure

  • take the identifier "var_IdentOfOOI" and launch a SPARQL 'ASK' query for the GUID from the project federated endpoints
  • if it exists do nothing
  • else the code as shown above shall be in the export file.

TIP0001T1 - Declaration and Identification of an imagined Individual

NARRATIVE

Imagined is the opposite of Actual (see TIP0001T2). Example: the instances of FunctionalPhysicalObject, that are being represented on a P&ID, are imagined, whereas the instances of MaterializedPhysicalObject, such as the products coming out of the factory, are Actual. Part 2 defines an ActualIndividual as "a PossibleIndividual that is a part of the space-time continuum that we inhabit. It exists in the present, past, or future of our universe, as opposed to some imagined universe.".

Any (instance of a subtype of) PossibleIndividual gets a user-memorizable identifier of a type that is selected from a picklist.

The OOI (Object Of Interest) that is identified shall be of the type given in that picklist.

SIGNATURE

PICKLIST

Select var_IdentType from the following (add or delete per application):

IDENTIFICATION BY

var_IdentType

use

OOI shall be a

var_EntityType

OOI shall be a

member of

var_ObjectType

label ofvar_ObjectType   (for information only)

ACTIVITY NUMBER

rdl:RDS2229905

dm:Activity & dm:ActualIndividual

N/A

 

ACTIVITY TAG

rdl:RDS2229976

dm:Activity

N/A

 

ASSET NUMBER

rdl:RDS2221102

edm:InanimatePhysicalObject

rdl:RDS422594

ARTEFACT

BUILDING NUMBER

rdl:RDS2221098

edm:InanimatePhysicalObject

rdl:RDS9691217

BUILDING

CABLE NUMBER

rdl:RDS2221103

edm:InanimatePhysicalObject

rdl:RDS2229989

CABLE

CONSTRUCTION AREA NUMBER

rdl:RDS2221097

edm:ClassOfSpatialLocation

rdl:RDS2229165

CONSTRUCTION AREA

DOCUMENT NUMBER

rdl:RDS2221088

dm:ClassOfInformationObject

 

(Class only)

EMPLOYEE NUMBER

rdl:RDS2223095

dm:Person

rdl:RDS2229218

EMPLOYED PERSON

MODEL NUMBER

rdl:RDS2229916

dm:ClassOfInanimatePhysicalObject

 

(Class only)

ORGANIZATION NAME

rdl:RDS2229785

dm:Organization

edm:Organization

Organization

PLANT NUMBER

rdl:RDS2221095

edm:InanimatePhysicalObject

rdl:RDS7151797

PLANT

PROCESS UNIT NUMBER

rdl:RDS2221096

edm:InanimatePhysicalObject

rdl:RDS2229214

PROCESS UNIT

PROJECT CODE

rdl:RDS2229781

dm:Activity

rdl:RDS9629

PROJECT

PROJECT NAME

rdl:RDS2229780

dm:Activity

rdl:RDS9629

PROJECT

ROAD NUMBER

rdl:RDS2221100

edm:InanimatePhysicalObject

rdl:RDS2229219

ROAD

SERIAL NUMBER

rdl:RDS2221101

dm:MaterializedPhysicalObject

N/A

 

SOCIAL SECURITY NUMBER

rdl:RDS2223096

edm:Person

N/A

 

STATEMENT NUMBER

rdl:RDS2229909

dm:ClassOfInformationRepresentation

rdl:RDS2229083

STATEMENT

STRUCTURAL FRAMEWORK NUMBER

rdl:RDS2221099

dm:ClassOfInanimatePhysicalObject

rdl:RDS815080531

STRUCTURAL FRAMEWORK

TAG NUMBER

rdl:RDS2221089

dm:FunctionalPhysicalObject

--- *)

 

          COATING LAYER TAG

rdl:RDS2229901

dm:FunctionalPhysicalObject

rdl:RDS738306981

COATING LAYER

          ELECTRICAL TAG

rdl:RDS2221091

dm:FunctionalPhysicalObject

rdl:RDS497678601

ELECTRICAL APPARATUS

          PROCESS EQUIPMENT TAG

rdl:RDS2221090

dm:FunctionalPhysicalObject

rdl:RDS422594

ARTEFACT

          FUNCTION TAG

rdl:RDS2229975

edm:FunctionalObject

edm:FunctionalObject

FunctionalObject

          HEAT TRACING SYSTEM NUMBER

rdl:RDS2229903

dm:FunctionalPhysicalObject

rdl:RDS267434

 HEAT TRACING SYSTEM

          INSTRUMENT TAG

rdl:RDS2221092

dm:FunctionalPhysicalObject

rdl:RDS934064

PROCESS INSTRUMENTATION ITEM

          INSULATION TAG

rdl:RDS2229902

dm:FunctionalPhysicalObject

rdl:RDS328094

INSULATION TAG

          LINE NUMBER

rdl:RDS2221093

dm:FunctionalPhysicalObject

rdl:RDS270359

PIPING NETWORK SYSTEM

          NOZZLE NUMBER

rdl:RDS2229955

dm:FunctionalPhysicalObject

rdl:RDS415214

NOZZLE

          STREAM NUMBER

rdl:RDS2221094

dm:Stream

dm:Stream

Stream

          SUPPORT NUMBER

rdl:RDS2229904

dm:FunctionalPhysicalObject

rdl:RDS6728598

SUPPORT

--- *) do not use, but use a specialization  

 

GENERATED CODE

  

# DECLARED OBJECTS (check existence and if not existing: declare)

  

# Declaration of identified individual

  

<TGUID1> rdf:type <var_EntityType> , <var_ObjectType> , dm:WholeLifeIndividual 

    rdfs:label  "var_IdentOfOOI" ;

    meta:valEffectiveDate "var_dateTime"^^xsd:dateTime .

  

<TGUID2> rdf:type tpl:ClassifiedIdentificationOfIndividual ;

    tpl:hasIdentified <TGUID1> ;

    tpl:valIdentifier "var_IdentOfOOI" ;

    tpl:hasIdentificationType <var_IdentType> ;

    meta:valEffectiveDate "var_dateTime"^^xsd:dateTime .  

  

MAPPING TO TRIPLES

  

# DECLARED OBJECTS (check existence and if not: declare)

  

<TGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <var_EntityType > .

<TGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <var_ObjectType> .

<TGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://data.15926.org/dm/WholeLifeIndividual> .

<TGUID1> <http://www.w3.org/2000/01/rdf-schema#> "var_IdentOfOOI" .

<TGUID1> <http://data.15926.org/meta/valEffectiveDate> "var_dateTime"^^<http://www.w3.org/2001/XMLSchema#dateTime> .

  

<TGUID2> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://data.15926.org/tpl/ClassifiedIdentificationOfIndividual> .

<TGUID2> <http://data.15926.org/tpl/hasIdentified> <TGUID1> .

<TGUID2> <http://data.15926.org/tpl/valIdentifier> "var_IdentOfOOI" .

<TGUID2> <http://data.15926.org/tpl/hasIdentificationType> <var_IdentType> .

<TGUID2> <http://data.15926.org/meta/valEffectiveDate> "var_dateTime"^^<http://www.w3.org/2001/XMLSchema#dateTime> .

 


TIP0001T2 - Declaration and Identification of Actual Individual

NARRATIVE

For an explanation of Actual Individual see TIP0001T1 above.

A(n instance of a subtype of) PossibleIndividual that is also an ActualIndividual (i.e. exists in our universe) gets a user-memorizable identifier of a type that is selected from a picklist.

The OOI (Object Of Interest) that is identified shall be of the type given in that picklist.

SIGNATURE

PICKLIST

Select var_IdentType from the following (add or delete per application):

IDENTIFICATION BY

var_IdentType

use

OOI shall be a

var_EntityType

OOI shall be a

member of

var_ObjectType

label ofvar_ObjectType   (for information only)

ACTIVITY NUMBER

rdl:RDS2229905

dm:Activity & dm:ActualIndividual

N/A

 

ACTIVITY TAG

rdl:RDS2229976

dm:Activity

N/A

 

ASSET NUMBER

rdl:RDS2221102

edm:InanimatePhysicalObject

rdl:RDS422594

ARTEFACT

BUILDING NUMBER

rdl:RDS2221098

edm:InanimatePhysicalObject

rdl:RDS9691217

BUILDING

CABLE NUMBER

rdl:RDS2221103

edm:InanimatePhysicalObject

rdl:RDS2229989

CABLE

CONSTRUCTION AREA NUMBER

rdl:RDS2221097

edm:ClassOfSpatialLocation

rdl:RDS2229165

CONSTRUCTION AREA

DOCUMENT NUMBER

rdl:RDS2221088

dm:ClassOfInformationObject

 

(Class only)

EMPLOYEE NUMBER

rdl:RDS2223095

dm:Person

rdl:RDS2229218

EMPLOYED PERSON

MODEL NUMBER

rdl:RDS2229916

dm:ClassOfInanimatePhysicalObject

 

(Class only)

ORGANIZATION NAME

rdl:RDS2229785

dm:Organization

edm:Organization

Organization

PLANT NUMBER

rdl:RDS2221095

edm:InanimatePhysicalObject

rdl:RDS7151797

PLANT

PROCESS UNIT NUMBER

rdl:RDS2221096

edm:InanimatePhysicalObject

rdl:RDS2229214

PROCESS UNIT

PROJECT CODE

rdl:RDS2229781

dm:Activity

rdl:RDS9629

PROJECT

PROJECT NAME

rdl:RDS2229780

dm:Activity

rdl:RDS9629

PROJECT

ROAD NUMBER

rdl:RDS2221100

edm:InanimatePhysicalObject

rdl:RDS2229219

ROAD

SERIAL NUMBER

rdl:RDS2221101

dm:MaterializedPhysicalObject

N/A

 

SOCIAL SECURITY NUMBER

rdl:RDS2223096

edm:Person

N/A

 

STATEMENT NUMBER

rdl:RDS2229909

dm:ClassOfInformationRepresentation

rdl:RDS2229083

STATEMENT

STRUCTURAL FRAMEWORK NUMBER

rdl:RDS2221099

dm:ClassOfInanimatePhysicalObject

rdl:RDS815080531

STRUCTURAL FRAMEWORK

TAG NUMBER

rdl:RDS2221089

dm:FunctionalPhysicalObject

--- *)

 

          COATING LAYER TAG

rdl:RDS2229901

dm:FunctionalPhysicalObject

rdl:RDS738306981

COATING LAYER

          ELECTRICAL TAG

rdl:RDS2221091

dm:FunctionalPhysicalObject

rdl:RDS497678601

ELECTRICAL APPARATUS

          PROCESS EQUIPMENT TAG

rdl:RDS2221090

dm:FunctionalPhysicalObject

rdl:RDS422594

ARTEFACT

          FUNCTION TAG

rdl:RDS2229975

edm:FunctionalObject

edm:FunctionalObject

FunctionalObject

          HEAT TRACING SYSTEM NUMBER

rdl:RDS2229903

dm:FunctionalPhysicalObject

rdl:RDS267434

 HEAT TRACING SYSTEM

          INSTRUMENT TAG

rdl:RDS2221092

dm:FunctionalPhysicalObject

rdl:RDS934064

PROCESS INSTRUMENTATION ITEM

          INSULATION TAG

rdl:RDS2229902

dm:FunctionalPhysicalObject

rdl:RDS328094

INSULATION TAG

          LINE NUMBER

rdl:RDS2221093

dm:FunctionalPhysicalObject

rdl:RDS270359

PIPING NETWORK SYSTEM

          NOZZLE NUMBER

rdl:RDS2229955

dm:FunctionalPhysicalObject

rdl:RDS415214

NOZZLE

          STREAM NUMBER

rdl:RDS2221094

dm:Stream

dm:Stream

Stream

          SUPPORT NUMBER

rdl:RDS2229904

dm:FunctionalPhysicalObject

rdl:RDS6728598

SUPPORT

--- *) do not use, but use a specialization  

 

GENERATED CODE

  

# DECLARED OBJECTS (check existence and if not existing: declare)

  

# Declaration of identified individual

  

<TGUID1> rdf:type <var_EntityType> , <var_ObjectType> , dm:WholeLifeIndividual, dm:ActualIndividual 

    rdfs:label  "var_IdentOfOOI" ;

    meta:valEffectiveDate "var_dateTime"^^xsd:dateTime .

  

<TGUID2> rdf:type tpl:ClassifiedIdentificationOfIndividual ;

    tpl:hasIdentified <TGUID1> ;

    tpl:valIdentifier "var_IdentOfOOI" ;

    tpl:hasIdentificationType <var_IdentType> ;

    meta:valEffectiveDate "var_dateTime"^^xsd:dateTime .  

  

MAPPING TO TRIPLES

  

# DECLARED OBJECTS (check existence and if not: declare)

  

<TGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <var_EntityType > .

<TGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <var_ObjectType> .

<TGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://data.15926.org/dm/WholeLifeIndividual> .

<TGUID1> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://data.15926.org/dm/ActualIndividual> .

<TGUID1> <http://www.w3.org/2000/01/rdf-schema#> "var_IdentOfOOI" .

<TGUID1> <http://data.15926.org/meta/valEffectiveDate> "var_dateTime"^^<http://www.w3.org/2001/XMLSchema#dateTime> .

  

<TGUID2> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://data.15926.org/tpl/ClassifiedIdentificationOfIndividual> .

<TGUID2> <http://data.15926.org/tpl/hasIdentified> <TGUID1> .

<TGUID2> <http://data.15926.org/tpl/valIdentifier> "var_IdentOfOOI" .

<TGUID2> <http://data.15926.org/tpl/hasIdentificationType> <var_IdentType> .

<TGUID2> <http://data.15926.org/meta/valEffectiveDate> "var_dateTime"^^<http://www.w3.org/2001/XMLSchema#dateTime> .