Lists Home |
Date Index |
- From: Wayne Steele <email@example.com>
- To: firstname.lastname@example.org
- Date: Tue, 08 Aug 2000 13:36:30 -0700 (PDT)
What we _REALLY_ want is for DTDs to "know about" namespaces; to treat
"p:foo", "p1:foo", and "foo" differently or indentically depending on the
namespace declarations in scope.
This is really hard, and probably impossible to do without reworking DTDs.
I think most people would accept, as a compromise, restricting
themselves to a one-to-one mapping of prefix to namespace, if they could
somehow inform the DTD of the proper prefix for each namespace (each
document gets to make its own mapping). It would be nice to allow a
The question then becomes: How do you "inform" the DTD of the proper
prefix for this instance document?
One solution that's been discussed here is using the internal
subset of the instance document, to "inform" the DTD through
redeclaration of certain Entities.
Careful use of Entity Refs in the DTD just barely allow you to get by with
This Just occured to me: The System Identifier! Since it's a
URI, it has lots of room for sneaking stuff into it.
Instead of having a URI like
you could use
The web server would have to:
a. get the ProtoDTD
b. send it through a ProtoDTD-to-DTD processor, with this param:
c. return the new DTD to the requestor.
For offline work, or without a whole web server:
Instead of using the System Identifier
I could set up a different URL handler, and use:
to do the same thing.
The only downsides I can think of are:
Someone has to actually write the code to do this (shouldn't be too hard)
Comparing the System Identifiers of XML documents becomes much more
It makes the System Identifier really verbose and ugly.
What do you think?
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com