Created on: Feb 5, 2012 Author: pvde This XSLT stylesheet is a non-normative part of the OASIS AS4 specification. It shows how AS4 receipt messages can be derived from AS4 user messages. The messageid to use on the AS4 receipt signal message The timestamp to set on the AS4 receipt signal message someuniqueid@receiver.example.com 2012-02-05T19:43:11.735Z When generating a receipt for a signed message, the receipt will be signed as well. We generate an identifier for the empty SOAP Body of the AS4 receipt for the WS-Security module. The empty body of receipt signal receipt for an unsigned message does not need an identifier There are two templates for eb3:Messaging element. This first template is for an AS4 user message that may have been exchanged over a multi-hop network. The receipt for such a message has WS-Addressing headers and a routing parameter based on the user message content. http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultMPC http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/part2/200811/icloud http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/oneWay.receipt This second template for the eb3:Messaging element covers AS4 point-to-point messages. The AS4 receipt is generated based on eb3:UserMessage and ds:Signaturecontent. A receipt for a signed AS4 message references the message parts using ds:References in the WS-Security header of that message A receipt for an unsigned AS4 message references the message using the eb3:UserMessage structure of the AS4 message.