W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > October 2011

RE: Extending XInclude

From: Grosso, Paul <pgrosso@ptc.com>
Date: Tue, 4 Oct 2011 12:02:16 -0400
Message-ID: <9B2DE9094C827E44988F5ADAA6A2C5DA03C05C63@HQ-MAIL9.ptcnet.ptc.com>
To: <public-xml-core-wg@w3.org>


> -----Original Message-----
> From: public-xml-core-wg-request@w3.org [mailto:public-xml-core-wg-
> request@w3.org] On Behalf Of Norman Walsh
> Sent: Monday, 2011 October 03 16:12
> To: public-xml-core-wg@w3.org
> Subject: Extending XInclude
> 
> "Grosso, Paul" <pgrosso@ptc.com> writes:
> > Extending Xinclude
> > ------------------
> [...]
> > ACTION to Norm:  Try to implement Jirka's proposals using
XSLT+XProc.
> 
> I believe this posting discharges my action.
> 
>    http://norman.walsh.name/2011/10/03/transclusion

I understand the bottom line of your experiments to be that,
if one defines xinclude processing to include copying certain
attributes on the xinclude element to the included root element,
it is possible to define id-fixup.

Is that a fair statement?

I didn't understand what cx:id="refid1" was doing, and (perhaps
related) I didn't understand how idref fixup worked (no, I didn't
study the XSLT to figure this out).

Finally, if adding attributes to the xinclude element (and defining
their processing) is sufficient to allow specification of id-fixup,
is this something we as a WG might want to write up, perhaps as a
WG Note?

paul
Received on Tuesday, 4 October 2011 16:04:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 October 2011 16:04:54 GMT