Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: References to a value of an element in another element?

From: "Michael Kay" <mike@--------.--->
To: "'Michael Kay'" <mike@--------.--->, "'Boris Kolpackov'" <boris@-------------.--->, <noah_mendelsohn@--.---.--->
Date: 2/4/2007 9:38:00 AM
> On the other hand, it might be that everyone ends up 
> implementing the whole of XPath 2.0 because it's too much of 
> a pain to implement a subset. That's certainly what I intend to do.


On this subject, I do hope that the WG won't end up deciding to require a
subset "for the convenience of implementors". That's almost always a bad
thing to do. The current spec has an example of it - the rules for defining
valid derivation of xs:all types require the processor to treat the order of
the xs:all particles as significant, and the spec is quite explicit that
this rule is there only for the convenience of implementors. Well, I found
it really inconvenient to impose this restriction, so what am I supposed to
do? Impose the restriction anyway, despite the fact that it means writing a
lot of extra code?

Michael Kay
http://www.saxonica.com/


From pau.carre@g... Mon Feb 05 15:37:32 2007
Received:


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent