Altova Mailing List Archives

Re: [xml-dev] IDs considered harmful or why keys might be better thanIDs...

From: "Jonathan Borden" <jborden@--------.--->
To: "Simon St.Laurent" <simonstl@--------.--->, <xml-dev@-----.---.--->
Date: 11/13/2001 1:10:00 PM
Simon St.Laurent wrote:

> >> Maybe that should be fixed in XSLT, not in XML?
> >>
> > It would be easier to fix it in XSLT if it was first fixed in the
> Ouch.
> Maybe it's time to abandon any notion of type specification, and just
> stick to the small bit of information that can be gleaned from a
> document instance minus DOCTYPE, even if it rules out certain
> possibilities.

Being too quick to discard DTDs is the perfect example of the premature
ejection of a core part of XML 1.0, at the same time piling on new
'features' for XML. The whole point is that one can _already_ implement
in-line ID attribute declarations (using the internal DTD subset). As I
recall, we have _already_ gone though a long process in an attempt to
replace DTDs with some type of XML syntax, yet today we still are having
these discussions. The ability to define an identifier unique within a
document seems like a straightforward and reasonable requirement. Do XML
Schema or RELAXNG solve this apparently simple problem in an equivalent
fashion to the DTD?

I think that XML 1.0 _taken as a whole_ is far better designed than most
people realize, and what some people see as a feature to be discarded with
their left hand, they seem to ask for in another form with their right hand.
It is time to better use what we already _have_ which should get around the
global problem of too many XML specifications that sort of but don't
completely work together.



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.