W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > March 2004

RE: Can XInclude Processors Rewrite IDs and References?

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 29 Mar 2004 13:37:48 -0800
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA2031411AF@RED-MSG-30.redmond.corp.microsoft.com>
To: <ekimber@innodata-isogen.com>, <www-xml-xinclude-comments@w3.org>

That section talks about rewriting the [references] property to match up
with duplicate IDs, not ID rewriting.  XInclude does not provide
specifically for ID rewriting, in fact a conformant processor should not
perform any.

However, if you want to perform ID rewriting or some other infoset
transformation either before inclusion or after XInclude processing, you
are free to do so.  I'd just ask you to document it as outside the
bounds of XInclude so your users understand where interoperability
"guarantees" leave off.

> -----Original Message-----
> From: www-xml-xinclude-comments-request@w3.org
[mailto:www-xml-xinclude-
> comments-request@w3.org] On Behalf Of Eliot Kimber
> Sent: Saturday, March 13, 2004 8:49 PM
> To: www-xml-xinclude-comments@w3.org
> Subject: Can XInclude Processors Rewrite IDs and References?
> 
> 
> I am implementing XInclude processing in XSLT by generating a new
single
> result document in memory. This means that I'm not literally creating
a
> new info set.
> 
> In my use cases it is essentially a certainty that IDs will be
> duplicated among the member documents included (because otherwise it
> would be necessary to make IDs unique across all possible documents,
> which is neither practical nor, in the abstract, necessary).
> 
> Therefore I must rewrite IDs and their references.
> 
> I want to confirm that my reading of the 10 November Working Draft
> allows this processing. In particular, I intepret the 3rd bullet under
> 4.5.3:
> 
>    o The result infoset has ID clashes - that is, more than one
> attribute with attribute type ID with the same normalized value. In
this
> case, attributes with attribute type IDREF or IDREFS with the same
> normalized value might have different values for their references
> properties.
> 
> as indicating that the effective target of references to duplicated
IDs
> will be to the original elements (as included), that is, that "might
> have different values for their reference properties" is the infoset
> equivalent of ID rewriting.
> 
> Is my interpretation correct?
> 
> Thanks,
> 
> Eliot
> --
> W. Eliot Kimber
> Professional Services
> Innodata Isogen
> 9030 Research Blvd, #410
> Austin, TX 78758
> (512) 372-8122
> 
> eliot@innodata-isogen.com
> www.innodata-isogen.com
Received on Monday, 29 March 2004 16:38:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:57 UTC