Re: key/keyref problem and XSV

Eric van der Vlist <vdv@dyomedea.com> writes:

> Just a very minor comment, though :) ...the error message (no key) when the
> key is duplicated such as in:
> 
> 
> <doc>
>   <section>
>    <key id="1"/>
>    <key id="2"/>
>   </section>
>   <section>
>    <key id="3"/>
>    <key id="2"/>
>   </section>
>   <ref ref="1"/>
>   <ref ref="2"/>
> </doc>
> 
> is misleading:
> 
> <invalid char='2' code='cvc-identity-constraint.2.3.2' line='11'
> resource='key-keyref-wrong.xml'>no key in {None}:key for 2</invalid>

That will take some work to fix -- as implemented, the collision means 
that at the level of the <doc>, there _is_ no key in {None}:key.  It's 
possible to leave a trace so the error can be different. . .

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/

Received on Monday, 24 September 2001 11:27:21 UTC