Difference between revisions of "Use of ID/IDREF"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
Line 1: | Line 1: | ||
+ | {{INM Finalized Workitem}} | ||
{{INM Approval|20060915|Motion that the construct of ID/IDREF should not be used at the ITS level, unless specific support for the controlled use of the concept is defined in the methodology. (Charlie McKay/Sandy Stuart,9-0-0)}} | {{INM Approval|20060915|Motion that the construct of ID/IDREF should not be used at the ITS level, unless specific support for the controlled use of the concept is defined in the methodology. (Charlie McKay/Sandy Stuart,9-0-0)}} | ||
Revision as of 18:44, 19 September 2006
ID/IDREF is a mechanism which can be used to remove duplication of data in XML instances.
The ID/IDREF mecahnism can be used by the ITS to minimize the size of messages on the wire. Whenever one encounters an IDREF one would have to process the thing being referenced. It is a potential ITS level feature. It turned out that this is not very robust, and hasn't been used substantially. Horrible for transforms. Stylesheets are basically impossible.
The XML SIG has studied the use of XML ID/IDREF. Based on the outcome of that they will move the motion during the upcoming WGM that ID/IDREF can't be used within the ITS (because of technical implementation reasons as will be stated above).
Q: (Joseph Waller) Is ID/IDRef model derived or not? and if so (or not) how does this end up in schema? A: The concept doesn't exist within the RIM.