W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2000

RE: [DR008] - passing arbitrary content

From: Dick Brooks <dick@8760.com>
Date: Tue, 5 Dec 2000 21:57:50 -0600
To: "Andrew Layman" <andrewl@microsoft.com>, <xml-dist-app@w3.org>
Message-ID: <NDBBIOBLMLCDOHCHIKMGKEAEEKAA.dick@8760.com>
Andrew,

Thanks for clarifying the point regarding hex/base64, Base64 is certainly
more appropriate in this context.

I want to explore one of your comments more thoroughly:
> Base64 is a supported type within XML Schemas.  The main point is
> that it is
> easily possible to carry small amounts of binary data inline in XML.

Does this mean there is an "upper limit" for the amount of binary data that
XP should be
expected to carry? For example, one of our clients, an electric company,
regularly provides
a "profile" of its entire customer base, totaling 150 MB, to marketing
companies that are interested in this
information. Would you consider a 150 MB binary payload beyond XP's intended
use?

> Regarding referencing data using a URI, the URI does not need to reference
> remote data.  It can reference another part within a
> multipart-MIME package.
> See
>

I agree, this is the same technique used by ebXML. ebXML manifest entries
"reference" local (in the same MIME package) MIME body parts via URI's
containing MIME Content-ID's. Perhaps it would be
worthwhile to define the requirements of local and remote references so that
both are covered in XP's requirements doc.

Thanks,

Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@8760.com
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions
Received on Tuesday, 5 December 2000 23:01:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:57 GMT