I think the snippet below illustrates the construct required that would be used to define the GH structure for use in a document exchange...I don't think it fills the position of a GH. -matt Duane Nickull wrote: > 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-hea der-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 > > > ---------------------------------------------------------------- > The ebxml-dev list is sponsored by OASIS. > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.ebxml.org/ob/adm.pl> ---------------------------------------------------------------- The ebxml-dev list is sponsored by OASIS. To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.ebxml.org/ob/adm.pl>
<<attachment: winmail.dat>>