Lists Home |
Date Index |
> Just wondering (again) the consequences of XML 1.1 on other specs.
> The end-of-line stuff is done by the parser, will not be seen
> by the applications and shouldn't have a uge impact on the
> other specs...
> The modification of the defininition of a Name will create an
> incoherence between XML 1.1 and specs such as XSLT, XPath,
> CSS, W3C XML Schema part 2 or RDF (there are probably more of
> these which are just the ones I am using on a daily basis!):
> a XML 1.1 name won't be any longer a name for these specs.
> Is there any plan to ask (or kindly suggest) to these working
> groups to publish new releases of their specs?
This is part of what I referred to as the costs created by a
discontinuity. Yes, it creates enormous problems for the other specs.
For example, people will expect to use XSLT to convert XML 1.1 documents
to XML 1.0 documents, so we are going to have to have rules about what
happens if the names are invalid; and vice-versa, if the characters are
Very few users are going to be affected by these changes. In fact, I
suspect few XSLT/XPath processors will be affected, I suspect most of
them are already "liberal in what they accept". But the specs will
certainly get more complicated, at a time when Tim Bray and others are
campaigning for them to be simplified.
The same applies to XML Namespaces 1.1 (which, for good measure, has
reams of stuff about how a namespace name is supposed to be an IRI, but
still won't make up its mind whether parsers are supposed to reject
documents if the namespace name is an arbitrary string).