Re: [Bug 11716] Identity constraints: grammatical typo

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Kay writes:

> Secondly, I think it's almost certainly intended that the key
> sequence for each selected node should contain one value (or absent)
> for each field in the constraint, and the rules fail to ensure this,
> especially in the case where the field expression selects an empty
> node-sequence.

So I think we disagree here about a matter of substance, which
none-the-less, curiously, doesn't affect any visible aspect of
processor behaviour (I don't think).

Consider the following key (from the spec.):

 <xs:element name="root">
  . . .
  <xs:key name="regKey">
   <xs:selector xpath=".//vehicle"/>
   <xs:field xpath="@state"/>
   <xs:field xpath="@plateNumber"/>
  </xs:key>
 </xs:element>

and an instance which looks like this

 <root>
  . . .
  <vehicle plateNumber="N895JTS">....</vehicle>
  . . .
 </root>

I believe the *key-sequence* for this, per both 1.0 and 1.1, is

 ("N895JTS")

whereas I take it you believe it is

 (???, "N895JTS")

at least for 1.1 (where I'm not at all sure what you have in mind for
the ???).

I suppose it doesn't matter, except insofar as it confuses readers,
since I _think_ both of us believe that clause 4 of the rule under
discussion will rule the node corresponding to the <vehicle... above
_out_ of the *qualified node set*, so the document will not be
schema-valid. . .

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFNLdnLkjnJixAXWBoRAqnvAJ9mrzPtHAtL0FCIhIYwa9R1ZjW5IQCfTSMH
dIVMSGuV6faGUH8soPsQ/Ms=
=nWsA
-----END PGP SIGNATURE-----

Received on Wednesday, 12 January 2011 16:42:17 UTC