- From: Dick Brooks <dick@8760.com>
- Date: Wed, 10 Jan 2001 07:51:38 -0600
- To: "Herriot, Robert" <Robert.Herriot@pahv.xerox.com>, <xml-dist-app@w3.org>
Robert, see responses inline. >an image and its reference. In the context of multipart/related This >constraint seems to imply that: > >a) the XML text data must be split into multiple fragments with one or more >images between each XML fragment, ebXML splits a message into two parts, a header and payload. The header contains metadata describing characteristics germane to the payload, if present or an "activity". An ebXML message may contain a header only, this allows the structure to be used for "acknowledgements", administrative functions (e.g. pings) and RPC functions. The header may reference adjunct body parts (fragments) within the message payload. >b) there must be a root object that references all of the XML fragments with >cid's An ebXML header contains a manifest that describes all the parts (documents) within a payload. An ebXML payload can contain any MIME media type, including binary, XML, multipart/*, et al. >c) images must be referenced with cid's within the XML fragments. ebXML supports this today. An ebXML manifest contains "Document References" that are specified using Xlink syntax. The document references refer to CID's within the payload. Dick Brooks (ebXML liaison to XML Protocol Activity) http://www.8760.com/
Received on Wednesday, 10 January 2001 08:47:37 UTC