Re: [ebxml-dev] Re: [ubl-lcsc] Re: [ubl-ndrsc] UN/CEFACT ATG 'Gen ericHeader' Project

[Duane Nickull <duane@xmlglobal.com>]

Assaf Arkin wrote:
...
> The information exchanged between the processes is described in one place.
> Let's call it 'input' for a second. If the process needs to know when the
> request was made than it's input will include some property 'tns:createdAt'.
> 
> The manner in which that information is contained in the message is defined
> elsewhere. 
 >>>>>>>
Assaf:

Yes - we also do that.  In fact, a party knows exactly what the content 
is before they look at the payload.  This is determined by a number of 
artifacts.

In ebXML architectures, the BPSS + state, along with the assertions of 
CPA ID and Conversation ID in the incoming message can alone determine 
the exact content.   If someone uses the entire ebXML arch, there is no 
need for an additional Generic Header.

The need for this arises out of partners who do not use the stack.  They 
would identify a requirement for the GH then include it in the payload, 
where it belongs.

Duane

-- 
VP Strategic Relations,
Technologies Evangelist
XML Global Technologies
****************************
ebXML software downloads - http://www.xmlglobal.com/prod/