Hess Yvan <yvan.hess@imtf.ch> writes:
> <xs:key name="DocIdentifier">
> <xs:selector xpath="."/>
> <xs:field xpath="@id"/>
> </xs:key>
This does not have the desired effect, it will always be true, as
there is only ever one id attribute on a 'document' element. To have
this do useful work, you need to change it to
<xs:key name="DocIdentifier">
<xs:selector xpath=".//my:document"/>
<xs:field xpath="@id"/>
</xs:key>
and move it to within an element declaration for an element which
scopes all your 'document' nodes.
> It works fine, but I don't know the future impacts/limitation of such
> choice, specially concerning the usage of URN as unique identifier in
> conjunction with others XML technologies. Does anybody have any comments,
> suggestions or best practices about this subject? Can you see future
> limitation?
I don't foresee any future problems with this -- the actual _type_ of
the attribute you call 'id' is completely within your control.
ht
--
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@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]