Re: [ubl-dev] UBL Processes

["Stephen Green" <stephengreenubl@gmail.com>]

Jan,

Yes, this is how UBL was designed. Wherever appropriate these
application layer and message transport details were deferred to those
layers to avoid duplication and redundancy. Both ebXML-MS and WS-*
were in mind and anything else that might come along. There was some
work done outside UBL to standardise a 'standard business document
header'  (CEFACT's SBDH) but I couldn't find a reference to it using
a Web search - it might have what you need. Can you not use the ebMS
header? If all else fails maybe you should resort to the Extension point
in UBL documents but that seems a little awkward since the document
itself is ideally packaged inside or attached to the messaging layer and
not the other way round. If it was me I'd start by trying to use the ebMS
header (3.0) to wrap the document. Failing that I'd send both document
and ebMS header as separate instances (if the transport supports two
instances that is - I don't know much about Atom). All very interesting.
Maybe some of the rest of the ebXML stack might be useful for this too.

Best regards


> In UBL, are there elements that provide the information to a document
> receiver
> where to send the next message in the overall process to? I suppose
> this is
> subject to the actual cordination framework in use and deliberately
> out of scope
> for UBL itself, yes?
>
> IOW, if I received an UBL Order via email the sender's email address
> would be
> the target for my Order Reply. There is nothing in the UBL Order
> itself that I
> should (or: am allowed to) look at to find the target to reply to. Yes?
>
> Thanks - all this is helping a lot.
>
> Jan
>



-- 
Stephen D. Green

Partner
SystML, http://www.systml.co.uk
Tel: +44 (0) 117 9541606

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice