OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

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

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. 

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 

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.


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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC