Introduction
Figure 1 - Format of a Transfer File from a user application Figure 2 - Format of a Transfer File between two Façades
When data is transferred from one location to another, this is understood to be a physical removal from the sending side and a physical population of the receiving side. This also means that the custodianship, i.e. the responsibility for the data, moves to the custodian of the receiving side.
Transfer in ISO 15926-7 can be between:
- a file with the results of a mapping of application data to the RDF/XML format as defined in ISO 15926-7 to a Façade (usually called a System Façade, although it may be any other Façade as well, if that can be properly managed).
- a sending Façade and a receiving Façade.
File format
Figures 1 and 2 show the file format.
Rationale
The rationale of this set-up is that we:
- segregate the meta information about the transmission from the actual "payload";
- in case of transfer between two Façades we can store the data at both sides for audit trail, encapsulted at the non-owning side
- we can easily parse that payload by just fetching the 'content' of the RdfXmlLiteral;
- we can make a back-up of the transfer files, and in case of technical problems (e.g. disk crash or corrupt data) we can recreate the contents of the Façade until the date-time of those problems.
Example files
Click here for an example of a Transfer File between a User Application and its System Façade.
Click here for an example of a Transfer File between two Façades.
|
