Question
eDelivery assures a payload can travel safely from AccessPoint A to AccessPoint B.
What happens next? What application/service (or process) needs to be launched or triggered based upon the payload content, does the business on the sending side needs a business answer as well (additional to the the eDelivery acknowledgment)?
I'm pretty sure many of the eDelivery adopters have been faced with similar questions, but how was this approached? Did anyone use SBDH (Standard Business Document Header) or ended up building their own specification?
In case someone has being using SBDH, can I please be enlighten on the meaning of and "e-Document"? The term is used in the e-SENS wiki (http://wiki.ds.unipi.gr/display/ESENS/PR+-+SBDH) but I'm not quite certain of its meaning. Is it the payload of an AS4 message? Which means it can be anything (not necessarily a document, like a .word file or pdf, etc.).
Author: João NEVES
Answer
Q: Does the business on the sending side needs a business answer as well (additional to the the eDelivery acknowledgment)?
The eDelivery acknowledgment of AS4 is a proof that Corner 3 (C3) received the message but not that the message was delivered to Corner 4 (C4). Consequently it's common practise to have such a business answer in addition to the AS4 acknowledgment. Typically these messages are generated by the receiving backend (C4) and the project can decide the content of such message.
Q: I'm pretty sure many of the eDelivery adopters have been faced with similar questions, but how was this approached?
In the eProcurement domain, they use the Universal Business Language (UBL) standard which includes a business level response called 'Application Response':
http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#T-APPLICATION-RESPONSE
This message is used to confirm receipt by C4.
In the eJustice domain, they use a more complex set of evidences based on ETSI REM:
http://www.etsi.org/deliver/etsi_ts/102600_102699/10264002/02.02.01_60/ts_10264002v020201p.pdf
Other projects have created their own business response schema inspired in the above specs.
Q: Did anyone use SBDH (Standard Business Document Header) or ended up building their own specification ?
In the eProcurement domain, PEPPOL, they use this business level header which can be used to route messages once they arrive in C3:
We know that the NL has adopted SBDH to ensure the routing of messages. Other projects have also shown interest in SBDH and we will create guidelines about it next year.