TRP Messaging Service Specification

[Shumpei NAKAGAKI <nakagaki@mxb.mesh.ne.jp>]

To ebxml-transport@lists.ebxml.org

My comment on TRP Messaging Service Specification.

Appendix B shows ebXML Message enveloped message example only.
This spec is for the envelope and header.

Line 801 thru line 803 and line 1064 thru line 1067 should be replaced with

     <MessageType>Normal</MessageType>
<Manifest>
      <DocumentReference>
            <DocumentLabel>Payroll</DocumentLabel>
            <Intent>RecordCommission</Intent>
      </DocumentReference>
</Manifest>
<Header>
      <From>
             <PartyId context="DUNS">12345</PartyId>
       </From>
       <To>
              <PartyId context="DUNS">67890</PartyId>
       </To>
       <TRAInfo>
              <TPAId context="tpadb">12345678</TPAId>
              <ConversationId context="tpadb">987654321</ConversationId>
              <ServiceInterface>RecordCommission</ServiceInterface>
              <Action>Newrecord</Action>
        </TPAInfo>
        <MessageData>
               <MessageId>123456789</MessageId>
               <TimeStamp>20000725T121905.000Z</TimeStamp>
               <RefToMessageId>987654321</RefToMessageId>
         </MessageData>
         <ReliableMessageInfo>
                <DeliverySemantics>"Unspecified"</DeliverySemantics>
         </ReliableMessageInfo>
</Header>

Regards,
Shumpei
       
**************************************
  Shumpei NAKAGAKI(NEC Corporation ) 
  E-Mail:s-nakagaki@bp.jp.nec.com 
        :nakagaki@mxb.mesh.ne.jp
 (Phone:+81 3 3798-0829)
 (Fax:  +81 3 3798-0841)
**************************************