John M. Dlugosz wrote: > After getting a second opinion in a different validator, and fiddling a bit, > I get the idea that you are not handling the case where the refer child of a > keyref is naming a <unique> rather than a <key>. I get errors on every one, > "referenced key not found or not a "key" identity-constraint > [c-props-correct.2]" but if I change one from a <unique> to <key>, that one > no longer errors, so it's not a scoping issue with the name or something like > that. > > Am I missing something?
No. The W3C XML Schema validator of XXE simply does not handle the case where the refer child of a keyref is naming a <unique> rather than a <key>. This omission will be fixed in next release.
