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

[Duane Nickull <duane@xmlglobal.com>]

Dale:

How do you see the GH in the incoming message different from the CPA 
decalration of:

<tp:SimplePart tp:id="xmlglobal_msg_header" tp:mimetype="text/xml">
     <tp:NamespaceSupported 
tp:location="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"; 
tp:version="2.0">http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd 
</tp:NamespaceSupported>
   </tp:SimplePart>

Since an incoming message contains an assertion of a CPA ID,  wouldn't 
the above declaration along with the Conversation ID be able to pinpoint 
the payload?  IMO - the Generic Header, if not used in a payload 
envelope, could go in the CPA.  A simple, optional extension mechanism 
to the tp:SimplePart element could contain it, couldn't it?

Duane