> In effect, although the above interface is useful, it reduces
> interchange in that I can make a document with broken system
> identifiers work on my system. Essentially, I can make an
> *invalid* document valid!
You can do this in any case, though -- you can intercept URIs in the
system libraries (Java, for example, lets you register your own
schemes), or you can redirect them with a proxy server.
With URLs, file:// will almost always break on exchange, as will http:
system identifiers that refer to hostnames visible only within a
private network.
Your other points (which I omitted above) are well taken -- public
identifiers are a bit of a muddle right now, but since they're in XML
1.0, it makes sense to support them. The interface is not only for
public identifiers, however -- users can also remote URIs to
local/secure equivalents, and they can even screen out certain URIs if
necessary. I'd better copyright "XML-Nanny" before someone else
thinks of it.
All the best,
David
--
David Megginson ak117@freenet.carleton.ca
Microstar Software Ltd. dmeggins@microstar.com
http://home.sprynet.com/sprynet/dmeggins/
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)