replace_uri API method                                                                                   latest update: 2008-02-20

The replace_uri API method:

• optionally adds a suffix to the ID of each thing to be handed over, and to references to same, as stored in the "handovers" section of the sending façade;

NOTE 1 - This suffix is denoting the source of the data and serving to avoid duplication of IDs in the destination façade; it is optional because internally one should consider to control uniqueness of IDs in other ways, such as adding a mnemonic per discipline (e.g. 'ves' for Vessel Engineering) and control number blocks per discipline on a project.

NOTE 2 - If suffixes are added, then the handover API method must, on the fly, place the suffixed IDs in the "blob" of the 'content' of the included instance(s) of rdf:XMLLiteral.

NOTE 3 - The IDs of to-be-handed over things are known, because any hand-over application must, by necessity, give the possibility to select them.

• creates, for each handed over thing, a quad in the "data" section of the sending façade, that links the old URI#fragID to the new URI#fragID by means of an owl:sameAs property. This provides for the data necessary for tracking the whereabouts of each and every thing.