|
The send_message API method:
- completes an instance of template type &oim:ST-MESSAGE-0100-001, as stored in the "sentmsgs" section of the sending façade with the actual date-time of transmission;
- generates an RDF/XML file by:
- creating an owl:sameAs crossreference between the message ID in the context of the sending and of the receiving façade;
- unwrapping the included instances of rdf:XMLLiteral to RDF/XML format, and thereby changing their base URI from the one applying to the sending façade to the one applying to the receiving façade;
- pushes that message exchange file in the "recdmsgs" section of the destination façade;
- upon proper arrival of that message archives the message "payload" in the "sentmsgs" section of the sending façade;
- sends an e-mail with credentials to the custodian of that destination façade, informing him/her that a message has been sent to the "recdmsgs" section of his/her façade, with the ID of the message and the location(s) where the PDF file(s) is(are) stored; with the parse_message API method that custodian can obtain all PDF files and data;
- creates a "feedback" report, refers to this in an instance of template oim:ST-FACADE-2311-001, and stores this in the "sentmsgs" section (NOTE).
NOTE - In the instance of template type &oim:ST-MESSAGE-0100-001, as stored in the "sentmsgs" 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.
|
