At 12:33 99/04/05 +0900, MURATA Makoto wrote:
Paul Hoffman / IMC wrote:
OK, we've got about 30 people who signed up for the list. I think the first
order of business is for someone to say what is incorrect and/or lacking in
RFC 2376.
Here it is. I will also post my summary of the discussion at the xml-dev
mailing list very soon.
(3) A new parameter "externalid" for text/xml and application/xml
This parameter specifies the externalID from the DOCTYPE of the XML
document (if the DOCTYPE is present). Examples would be:
Content-type: text/xml;
externalid="http://www.foo.com/whizzy.dtd"
or
Content-type: application/xml; charset="utf-16be";
externalid="-//IETF//DTD vCard v3.0//EN"
Note: None of the above proposals handle non-monolithic XML documents very
well,
since different islands of non-monolithic XML documents belong to different
namespaces and thus different schemata. For example, the MIME parser cannot
invoke vCard applications if the vCard is embeded by the namespace mechanism.
I think this will become more and more important, and we should try to find
a solution that doesn't exclude it. On first sight, it doesn't look so
difficult:
Define one parameter, maybe named "namespaces", that lists, comma-separated,
all the namespaces used in the document. The DOCTYPE, if present, counts as
one. The DOCTYPE, or the namespace of the root element, is listed first.
If other description mechanisms (schemas,...) are defined, the URIs used
for them can also be used.
If I'm overlooking something, please tell me.
Regards, Martin.
#-#-# Martin J. Du"rst, World Wide Web Consortium
#-#-# mailto:duerst(_at_)w3(_dot_)org http://www.w3.org