ISO 15926-7 Template Specification

Version: 2008-02

Status: CD-TS

Template number - 0098
Name - Information about a document
Intent -

Representation of (meta-)information about a document.

Description -

A document is an instance of DocumentDefinition. It has five classes of relationship, viz:

  • it has a description that is an XmlSchemaString;
  • its information content of all its document cells is valid at a given date-time (see NOTE 1);
  • it refers to one or more template instances that provide a context for its own information (see NOTE 2);
  • it has a presentation script;
  • it has a URI reference to a PDF file, generated by the gendoc API method.

NOTE 1 - This date-time is used as a parameter for the query scripts of all document cells.

NOTE 2 - The information content of these templates constitutes the difference between the "implicit" information about the Things listed in this document, and their full "explicit" information.

Analysis diagram -  

Scope graph -  

Longhand and shorthand graph

-  

 

NOTE 1 - When designing a document type this template class is specialized whereby instances of the following classes are fixed ("hasValue"):

  • R-900394, defining the type of description(s) (e.g. title) of the document;
  • R-900303, defining the applicable context template class(es);
  • R-900393, defining the applicable presentation script(s);
  • R-900403, defining description by reference to a URI.

NOTE 2 - The following class instances are fixed for this generic template class:

  • R-900289, defining the role of the XmlSchemaDateTime as "Effectivity".
LT elements -

1   http://rdl.rdlfacade.org/data#R-900003                   

2   http://rdl.rdlfacade.org/data#R-900093                   

3   http://rdl.rdlfacade.org/data#R-900094                   

4   http://rdl.rdlfacade.org/data#R-900098                   

5   http://rdl.rdlfacade.org/data#R-900289                   

6   http://rdl.rdlfacade.org/data#R-900303                   

7   http://rdl.rdlfacade.org/data#R-900393                   

8   http://rdl.rdlfacade.org/data#R-900394                   

9   http://rdl.rdlfacade.org/data#R-900403                   

10  http://rdl.rdlfacade.org/data#XmlSchemaAnyUri            

11  http://rdl.rdlfacade.org/data#XmlSchemaDateTime          

12  http://tpl.rdlfacade.org/data#LT-0098.ClassOfDescription1

13  http://tpl.rdlfacade.org/data#LT-0098.ClassOfDescription2

14  http://tpl.rdlfacade.org/data#LT-0098.ClassOfDescription3

15  http://tpl.rdlfacade.org/data#LT-0098.Classification1    

16  http://tpl.rdlfacade.org/data#LT-0098.Classification2    

17  http://tpl.rdlfacade.org/data#LT-0098.Classification3    

18  http://tpl.rdlfacade.org/data#LT-0098.Classification4    

19  http://tpl.rdlfacade.org/data#LT-0098.Classification5    

20  http://tpl.rdlfacade.org/data#LT-0098.OtherRelationship1

21  http://tpl.rdlfacade.org/data#LT-0098.OtherRelationship2

OWL listing -

http://tpl.rdlfacade.org/data#0098

Specification in FOL

-

http://www.rdlfacade.org/files/iso15926-7/ts/0098_rules.pdf

Sample ST  instance -

    <part2:MultidimensionalObject rdf:ID="ST-549856">

        <rdf:type rdf:resource="http://www.xyz-corp.com/doc#DOC-123"/>

        <part7:describes rdf:resource="#COIR-094300"/> <!--the described document-->

        <part7:hasDescription rdf:resource="#XSST_409442"/> <!--"Required capabilities"-->

        <part7:isValidAt rdf:resource="#XSDT_20080107T1813Z"/>

        <part7:hasAsContext rdf:resource="#ST-326334"/> <!--E-101 is a part of plant HC-01-->

        <part7:hasPresentationScript rdf:resource="#XSST_970082"/> <!--the presentation script that converts all this in a real data sheet-->

        <part7:isPresentedOn rdf:resource="#XSURI_450822"/> <!--the URI of the PDF rendering of the document type-->

    </part2:MultidimensionalObject>

 

    <part2:ClassOfInformationRepresentation rdf:ID="XSDT_20080107T1813Z">

        <rdf:type rdf:resource="http://rdl.rdlfacade.org/data#XmlSchemaDateTime"/>

        <part2:content rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2008-01-08T18:13.00Z</part2:content>

    </part2:ClassOfInformationRepresentation>

 

    <part2:ClassOfInformationRepresentation rdf:ID="XSST_409442">

        <rdf:type rdf:resource="http://rdl.rdlfacade.org/data#R-901563"/> <!--English description (subclass of R-900094)-->

        <part2:content rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Data sheet for shell & tube heat exchanger</part2:content>

    </part2:ClassOfInformationRepresentation>

 

    <part2:ClassOfInformationRepresentation rdf:ID="XSST_970082">

        <rdf:type rdf:resource="http://rdl.rdlfacade.org/data#R-901195"/> <!--XSLT Script (subclass of R-900095)-->

        <part2:content rdf:datatype="http://www.w3.org/2001/XMLSchema#string">[XSLT script]</part2:content>

    </part2:ClassOfInformationRepresentation>

 

    <part2:ClassOfInformationRepresentation rdf:ID="XSURI_450822">

        <rdf:type rdf:resource="http://rdl.rdlfacade.org/data#XmlSchemaAnyUri"/>

        <part2:content               

              rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.pqr-ltd.com/p4502/edms#VS-43782-r2</part2:content>

    </part2:ClassOfInformationRepresentation>

 

NOTE - The (fictitious) data correspond with those used in the above analysis diagram.

 

Definition of properties for shorthand template:
Property   Description of the rdf:object
describes - a particular document (NOTE 1).
hasDescription -

an XmlSchemaString describing the document (NOTE 2)

isValidAt - an XmlSchemaDateTime that is a given date-time at which the information content of all the document cells of this document is valid.
hasAsContext -

zero or more shorthand templates that represent the context of the information contained in this document (NOTE 3).

hasPresentationScript - an XmlSchemaString that is the presentation script, as designed by the designer of this document type.
isPresentedOn - zero or one instance of XmlSchemaAnyUri that belongs to a PDF rendering of this document (NOTE 4).
     
NOTE 1 - The valid class is determined by means of the fixed ClassOfClassOfComposition.
NOTE 2 - Fixed for any particular document.
NOTE 3 - The class of these templates can be found via the classifying ClassOfRelationshipWithSignature that refers to a set of context templates.
NOTE 4 - See the gendoc API method of the generating facade.