[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: ebXML Headers Doc for Tokyo
Thank you for providing crucial information!! I have one question about TPAId, Generally, TPAId is the form "/<requestor-DUNS>/<responder-DUNS>/<TPAName>", right? Then, that is, every type of message has different TPAId. Since my understanding is that TPAId is for identifying TPA, namely one tpaML document, having different TPAId for every type of message means that we have distinct TPA for every type of message. This seems to be inconsistent with the sample TPA provided by Mark Hale (thank you!). IMHO, we should have one TPAId for a set of related ServiceInterfaces. Is this understanding correct? Or, if I've missed something, please let me know. Thanks in advance. ----- Original Message ----- From: "Hatem ElSebaaly" <firstname.lastname@example.org> To: <email@example.com> Sent: Thursday, October 26, 2000 6:39 AM Subject: ebXML Headers Doc for Tokyo > Attached is the word document that shows the header for the ebXML messages > for the retail and > automotive tracks. > Please let me know if there are issues. > This is the first cut.
Powered by eList eXpress LLC