Transfer File from Facade #1 to Facade #2                    latest update: 2008-02-18

Below is a Transfer File sent from Facade #1 to Facade #2, with explanations at the righthand side.

It results from execution of the handover_export API method of Façade #1.

The colors mean:

    the standard heading
    the transmission data
    the payload

  

 

<rdf:RDF

Opening

        xml:base="http://www.pqr-ltd.com/4502/ves"

        xmlns="http://www.pqr-ltd.com/4502/ves#"

        xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

        xmlns:xsd="http://www.w3.org/2001/XMLSchema#"

        xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"

        xmlns:owl="http://www.w3.org/2002/07/owl#"

        xmlns:part2="http://dm.rdlfacade.org/data#"

        xmlns:part4="http://rdl.rdlfacade.org/data#"

        xmlns:part7="http://tpl.rdlfacade.org/data#"

        xmlns:oim="http://oim.rdlfacade.org/data#">

Transfer from the "me03" façade to the "ves" façade

The standard heading, where the "baseURI" is that of the sending façade.

NOTE - The endpoint of the addressee façade is in the rdf:XMLLiteral below.

        <owl:Ontology rdf:about="">

                <owl:imports rdf:resource="http://dm.rdlfacade.org/data"/>

                <owl:imports rdf:resource="http://rdl.rdlfacade.org/data"/>

                <owl:imports rdf:resource="http://tpl.rdlfacade.org/data"/>

                <owl:imports rdf:resource="http://oim.rdlfacade.org/data"/>

                <owl:imports rdf:resource="http://www.pqr-ltd.com/p4502/me03"/>

        </owl:Ontology>

"Imports" means that a SPARQL query can get at the data as if they were residing in the façade with the baseURI (see above).

       <part2:ClassOfInformationRepresentation rdf:ID="RXL-ves234451">

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

                <part4:containedIn

                        rdf:resource="http://www.pqr-ltd.com/p4502/me03#ST-TRANSFER-ves20080126T170000Z"/>

                <part4:archiveLocation rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">

                        http://www.pqr-ltd.com/4502/me03/archive/RXL-ves234450.xml</part4:archiveLocation>

                <part2:content rdf:parseType="Literal">

                    <rdf:RDF

                        xml:base="http://www.pqr-ltd.com/4502/ves"

                        xmlns="http://www.pqr-ltd.com/4502/ves#"

                        xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

                        xmlns:xsd="http://www.w3.org/2001/XMLSchema#"

                        xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"

                        xmlns:owl="http://www.w3.org/2002/07/owl#"

                        xmlns:part2="http://dm.rdlfacade.org/data#"

                        xmlns:part4="http://rdl.rdlfacade.org/data#"

                        xmlns:part7="http://tpl.rdlfacade.org/data#"

                        xmlns:oim="http://oim.rdlfacade.org/data#">

                        <owl:Ontology rdf:about="">

                                <owl:imports rdf:resource="http://dm.rdlfacade.org/data"/>

                                <owl:imports rdf:resource="http://rdl.rdlfacade.org/data"/>

                                <owl:imports rdf:resource="http://tpl.rdlfacade.org/data"/>

                                <owl:imports rdf:resource="http://oim.rdlfacade.org/data"/>

                                <owl:imports rdf:resource="http://oim.xyz-corp.com/data"/>

                        </owl:Ontology>

This is a special construct that is called rdf:XMLLiteral. In the Reference Data Library it has been defined as RdfXmlLiteral, a subclassOf &part2:ClassOfInformationRepresentation.

In the 'containedIn' property reference is made to the transmittal that is stored in the sending façade.

In the 'archiveLocation' a URL is given in which the "payload" is archived after successful transfer.

In the 'content' property we now "wrap" the listing that is the actual "payload" of this Transfer File (all the above is necessary overhead). The rdf:parseType="Literal" is being used for that.

 

When this Transfer File is being parsed, this 'content' can simply be fetched and converted to quads in the Data section of the receiving façade. This is a task of the populate API method.

 

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

                                <rdf:type rdf:resource="http://oim.rdlfacade.org/data#ST-THING-1601-001"/>

                                <rdfs:label xml:lang="en">vessel V-6060 is classified as horizontal vessel</rdfs:label>

                                <part7:temporalWhole rdf:resource="http://www.pqr-ltd.com/p4502/cons#FPO-pcs347621"/>

                                <part7:classifiedIndividual rdf:resource="#FPO-ves347621-20080121T102634Z"/>

                                <part7:context rdf:resource="http://www.pqr-ltd.com/p4502/cons#COTWP-438800"/>

                                <part7:beginning rdf:resource="#XSDT_20080121T162634Z"/>

                                <part7:incidentalClass rdf:resource="http://www.15926.org/2006/02/rdl#RDS292004"/>

                        </part2:MultidimensionalObject>

This is the template instance "vessel V-6060 is classified as horizontal vessel", as has been sent in the first transfer file from the ME03 application to its "me03" facade. It is now further shifted "up the information chain" to the "ves" facade.

Note that it is completely unchanged

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

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

                                <part2:content rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">

                                      2008-01-21T10:26:34Z

                                </part2:content>

                        </part2:ClassOfInformationRepresentation>

The date-time that the above template started to be valid.

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

                                <rdf:type rdf:resource="http://oim.rdlfacade.org/data#ST-VESSEL-3401-002"/>

                                <rdfs:label xml:lang="en">

                                      vessel V-6060 has a nominal volume capacity of 60 m3

                                </rdfs:label>

                                <part7:temporalWhole rdf:resource="http://www.pqr-ltd.com/p4502/cons#FPO-pcs347621"/>

                                <part7:possessor rdf:resource="#FPO-ves347621-20080120T100500Z"/>

                                <part7:context rdf:resource="http://www.pqr-ltd.com/p4502/cons#COTWP-438800"/>

                                <part7:beginning rdf:resource="#XSDT_20080120T100500Z"/>

                                <part7:propertyType rdf:resource="http://rdl.rdlfacade.org/data#RDS658578"/>

                                <part7:numericalValue rdf:resource="#XSFL_60"/>

                                <part7:unitOfMeasure rdf:resource="http://rdl.rdlfacade.org/data#RDS994572"/>

                        </part2:MultidimensionalObject>

Shorthand template instance ST-ves267723 is a member of an OIM specialization of generic template class ST-3401.

The "temporalWhole" is defined in the Project Façade ("cons"), and referred here. The temporal part is defined here, on the fly. It shall not be explicitly declared.

The (optional) "context" is some change order or the like.

The information represented by this template instance began to be valid on January 20th 2008 at 10:05:00am "Zulu" time (= UTC, = GMT (give or take a few microseconds)).

RDS658578 = Nominal Volume Capacity (faked ID, still)

XSFL_60 is a (XML Schema)float of 60  

RDS994572 = m3 (faked ID, still)

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

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

                                <part2:content rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">

                                      2008-01-20T10:05:00Z

                                </part2:content>

                        </part2:ClassOfInformationRepresentation>

The date-time that the information, represented by above template instance ST-ves267723, became valid.

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

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

                                <part2:content rdf:datatype="http://www.w3.org/2001/XMLSchema#float">60

                                </part2:content>

                        </part2:ClassOfInformationRepresentation>

The XML Schema float that quantifies the property in template ST-ves267723.

Note that the underscore, used for all XSxx, serves to allow for negative values (e.g. XSFL_-10.5).

                    </rdf:RDF>

                </part2:content>

        </part2:ClassOfInformationRepresentation>

The closing of the 'content' property of RXL-ves234451, and of that RXL-ves234439 itself.

</rdf:RDF>

Closing