"data" section of Facade #2                                                                           latest update: 2008-02-20

The contents of a "data" section of a façade is the result of a kind of bookkeeping, with data flowing in (populate method) and flowing out (handover method), with a few sets of data that entered the "data' section in another way.

These are:

• by the populate method: the creation of instances of the specialization of template class ST-1004 called &oim:ST-FACADE-1004-001, "ending" the temporal part of any possible individual that is involved in a template, when that template has been replaced with another one (e.g.  a temporal part of vessel V-6060 when its volume no longer is 50 m³ but 60 m³);
• by the handover method: the creation of quads that represent the owl:sameAs relation between an oldURI#fragment_identifier and the newURI#fragment_identifier, allowing tracking of handed-over things;
• by the gendoc method: the creation of instances of the specialization of template class ST-0802 called &oim:ST-FILE-0802-001, that represents the fact that a document file in PDF format can be found at a particular URL;
• by the parse_message method: the creation of instances of the specialization of template class ST-0050 called &oim:ST-FACADE-0050-001, representing the fact that in a received message things were found that are under the control of the receiving façade, and that any such thing has a relationship with the ID of the DocumentCell-derscribing template (of the type &oim:ST-DOCUMENT_CELL-0096-001) that referred to a template that made that reference (the detour via that document cell is necessary for security reasons).

In the example below only the second of these extra types of data is shown.

The contents of the "data" section of Facade #2 after the execution of the populate API method is as shown below.

It contains the following information:

• Vessel V-6060 has a nominal volume capacity of 60m³, with its date-time and float value;
• Vessel V-6060 is a horizontal pressure vessel, with its date-time value;
• Vessel V-6060 is an XYZ Corp. Model 123 vessel, with its date-time value (this is based on an earlier population).

NOTE - If you are an attentive reader you may discover that there is something strange going on with the above data.

By executing the handover API method we move the information that:

• Vessel V-6060 has a nominal volume capacity of 60m³, with its date-time and float value;
• Vessel V-6060 is an XYZ Corp. Model 123 vessel, with its date-time value.

from this Façade #2 (the "ves" group façade) to a façade of another company (such as the plant owner/operator). The main reason for this is to show the effect of adding a suffix to the IDs of the handed over things (see replace_uri API method).

After successful hand-over the "data" section of Façade #2 looks like:

http://www.gamuth-oil.com/fac#ST-ves267818__875

http://www.gamuth-oil.com/fac#FPO-ves347621-20080116T130825Z__875

http://www.gamuth-oil.com/fac#XSDT_20080116T130825Z__875

http://www.gamuth-oil.com/fac#ST-ves267723__875

http://www.pqr-ltd.com/4502/ves#FPO-ves347621-20080120T100500Z

http://www.gamuth-oil.com/fac#FPO-ves347621-20080120T100500Z__875

http://www.gamuth-oil.com/fac#XSDT_20080120T100500Z__875

http://www.gamuth-oil.com/fac#XSFL_60__875

Note that seven sameAs quads have been added in the bottom, created by the replace_uri API method, and that here the handed over IDs got a suffix __875 , as dictated by the custodian of the receiving façade.

Whenever some template somewhere in the CPF (Confederation of Participating Façades) refers a handed over thing, for example to:

http://www.pqr-ltd.com/4502/ves#ST-ves267723  being the rdf:object of the 'hasAsInfo' property of an instance of oim:ST-DOCUMENT_CELL-0096-001,

and it would be queried as such, the above sameAS can be used to redirect that query to http://www.gamuth-oil.com/fac#ST-ves267723__875 .