handover API method                                                                                          latest update: 2008-02-22

The handover API method:

• moves a selected set of nodes and templates, in the form of triples, from the "data" section to a buffer;
• invokes the replace_uri method that:
• optionally adds a suffix to the rdf:IDs of to-be-handed over things in the buffer;
• creates a quad for each changed URI#fragID in the "data" section.

NOTE - 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 per discipline on a project.

• moves the updated buffer contents to the "handovers" section of the source façade;
• creates the "transmission" part of the transfer file-to-be-sent;
• creates a "feedback" report, refers to this in an instance of template oim:ST-FACADE-2311-001, and stores this in the "handovers" section (NOTE).

NOTE - In the just-created instance of template type &oim:ST-TRANSFER_FILE-0099-001, as stored in the "populations" section of the sending façade, there is an instance of Activity listed. That is the transmitting activity. This "feedback" report is "involved_by_reference" in this activity. Generic template class ST-2311 represents involvement by reference in an activity.

In case the subsequent handover_export would fail, the handover transaction is rolled back entirely.