RE: a manifest structure note

[srh@us.ibm.com]

Dick,
I see your point. I suggest this be a discussion point next week..........?

Scott R. Hinkelman
IBM Austin
SWG Java Solutions
XML/Java Standards Architecture
Office: 512-823-8097 TL793-8097
Home: 512-930-5675
Cell: 512-940-0519
srh@us.ibm.com
Fax: 512-838-1074



"Dick Brooks" <dick@8760.com> on 03/30/2000 11:56:48 AM

To:   Scott Hinkelman/Austin/IBM@IBMUS,
      ebxml-transport@lists.oasis-open.org
cc:
Subject:  RE: a manifest structure note




Scott,

It appears to me the absence of a "document reference" (7.25.2) within the
Message Manifest (section 7.25) would indicate a null payload. I don't see
any reference to "payload manifest" in the ebXML header spec.

Dick Brooks
http://www.8760.com/

-----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org
[mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of
srh@us.ibm.com
Sent: Thursday, March 30, 2000 10:49 AM
To: ebxml-transport@lists.oasis-open.org
Subject: a manifest structure note




Transporters,
a note on manifest structure..........
In the 3/30 conference, manifest structure was briefly discussed.
A suggestion concerning the payload content is to have a payload-manifest
within the message-manifest. The absence of the payload-manifest
would quickly allow processing discovery of an empty-payload
message........

Scott R. Hinkelman
IBM Austin
SWG Java Solutions
XML/Java Standards Architecture
Office: 512-823-8097 TL793-8097
Home: 512-930-5675
Cell: 512-940-0519
srh@us.ibm.com
Fax: 512-838-1074