RE: ebXML Headers Doc for Tokyo

["Patil, Sanjay" <Spatil@netfish.com>]

1> For Ack messages, the MessageType attribute of ebXMLHeader 
   would be "Acknowledgement" (not "Normal")
2> The TPAId would not change for a set of messages ex. TPAId
   for ItemCreate, ItemCreateAck, ItemAlign and ItemAlignAck 
   will remain same.
3> Same as 2 above for context attribute of ConversationId
4> Can we have a generic value for the Action element of 
   Ack messages ex. "Receipt Acknowledgement".
5> Can we have a single rule for relation betwen DocumentLabel
   and Action values ex. 
   Action = DocumentLabel + "Action"
   Use of "create" and "receive" delve into the semantics of
   the business process and does not necessarily cover all 
   possibilities ex. "change" for changing an existing Purchase Order
6> We will need the header definition for the TPA proposal and
   acceptance core process in Track 1.  I can work on this.

thanks,
Sanjay Patil
----------------------------------------------------------------------------
------------------------------
Work Phone: 408 350 9619
http://www.netfish.com


-----Original Message-----
From: Hatem ElSebaaly [mailto:hatem@ipnetsolutions.com]
Sent: Wednesday, October 25, 2000 2:40 PM
To: 'ebxml-poc@lists.ebxml.org'
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.


 <<ebXMLTokyoPOCHeader.doc>>