 |
 |
 |
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jack Lindsey writes:
> Why was [XPath in Identity Constraints] so restricted and is that a
> good thing in your opinion?
>
> I mean it is not very orthogonal when compared to XPointer, XSLT,
> XQuery and Schematron.
The decision was based, IIRC, on a desire to minimize complexity, both
for readers and for implementors.
There was a particular concern to ensure that a streaming schema
validator could be built, something which a richer XPath subset would
have precluded.
ht
=2D --
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@i...
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged sp=
am]
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFD0MBykjnJixAXWBoRAu0sAJ9Ngt0BSSSqpLaTp7phvCH9oTSMwQCdERlk
s5hA3ZplTgcyL2/yM6oyL9U=
=qAPd
=2D----END PGP SIGNATURE-----
From kohsuke.kawaguchi@s... Tue Jan 24 04:56:28 2006
Received: from w
|
 | 



|  |
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.
|  |
| |
 |
 |
 |