[
Lists Home |
Date Index |
Thread Index
]
In the context of our applications, we have choose to use URN as the
standard form of our generated documents identifier. Here is an example:
<document id="urn:hsc:EFECD0FF-C0A8021C08DEE071-D030940E">
<blabla></blabla>
</document>
This form is not compatible with ID/IDREF type provided by XML schema but is
compatible with key/keyref mechanism. In the context of our schema we
defined it as follow:
<xs:key name="DocIdentifier">
<xs:selector xpath="."/>
<xs:field xpath="@id"/>
</xs:key>
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?
Thanks for your answer
Yvan
Yvan Hess
Chief Software Architect
e-mail: yvan.hess@imtf.ch
phone : +41 (0)26 460 66 66
fax : +41 (0)26 460 66 60
Informatique-MTF SA
Route du Bleuet 1
CH-1762 Givisiez
Systemintegrators for eDocuments
http://www.imtf.com
DISCLAIMER
This message is intended only for use by the person to whom it is addressed.
It may contain information that is privileged and confidential. Its content
does not constitute a formal commitment by IMTF. If you are not the intended
recipient of this message, kindly notify the sender immediately and destroy
this message. Thank You.
|
