Lists Home |
Date Index |
Title: Why make namespaces so complicated?
about that last one. Key combinations are deadly.
1. Yes, they are both just strings. urn:publicId is also a
2. PublicIDs can contain rubbish, but so can a URI.
3. PublicIDs are as meaningful as the registration system makes
them. That is a choice. Conserve options.
4. Owner, Class, Version and Language don't change it being
name. They make it a name with structured parts. Used
designed, that can be useful information if one cares to use it.
choice. Explore options.
5. I understand the notion of immediate self-resolution. But
also confuses people. I can work with it. Yes, a PublicID
some thought, but it also opens up the potential to
the public registries and be very clear who owns a definition,
what class and version of that definition is asserted to be
effect for this content.
have value in contract processes. Assertions in the
content about the contract under which it operates have
6. Because a PublicID can be a namespace name value, we
to include it in our discussions. Otherwise, the decisions
by the TAG based on XML-Dev can deprive us of meaningful
where what is meaningful is chosen locally. Conserve
options. It is there. Why?
other words, for those who say a namespace name should
be a name, the public ID is fairly clear. (it won't get turned
and become clickable AFAIK). Given an OASIS catalog,
things can be done with it beyond resolution.
Namespaces are better than packing the schema in the element.
a lot of gymnastics to get around shipping a schema
and preserve well-formedness.
Understand all these things about public IDs, the
point I was trying to make is that at the end of the day both a public ID and
a URI are Just A String. URIs can be resolved by indirection just as well as
public IDs and public IDs can contain essentially meaningless rubbish. Yes,
they can carry some very useful registered information, but (correct me if I'm
wrong) that's only really meaningful if you have an ISO registration code of
some kind. I am no great authority, but by carrying things like Owner, Class,
Version and Language, suddenly they are not really Just A Name anymore, so I
can see the "information" conveyed by a public id also going stale. What do I
do when I get a document with a public ID whose owner has gone out of
business? I can't see it being any more useful to me than a dead URL
advantage of URLs, as a particular subset of URIs, is that they have the
flexibility to be "self-resolving" as a default behaviour, which is surely
quite handy in some circumstances. They don't have to be used on the
big advantage of public IDs is that you simply can't do much with them without
a resolving mechanism (implicit or explicit), which forces people to think
about it a little more. This is surely not a Bad Thing.