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

RE: TPAC topic: Extending XInclude

From: Grosso, Paul <pgrosso@ptc.com>
Date: Mon, 31 Oct 2011 09:32:19 -0400
Message-ID: <9B2DE9094C827E44988F5ADAA6A2C5DA03EEE596@HQ-MAIL9.ptcnet.ptc.com>
To: <public-xml-core-wg@w3.org>

> -----Original Message-----
> From: Norman Walsh [mailto:ndw@nwalsh.com]
> Sent: Sunday, 2011 October 30 21:18
> To: public-xml-core-wg@w3.org
> Subject: Re: TPAC topic: Extending XInclude
> "Grosso, Paul" <pgrosso@ptc.com> writes:
> > Paul said we could say that all attributes on the xinclude element
> > that are in the xinclude namespace should be copied to the "root"
> > included node(s).  That one thing would allow a follow up process
> > such as Norm's XSLT to do the necessary fixup.  If one did xinclude
> > processing after validation, one could give those extra attributes
> > defaults in the schema so that they didn't need to be authored.
> I still feel like it might be better to say that all attributes in
> *any* namespace get copied over. That avoids any contention over the
> local names of the attributes. DocBook can have db:transclusion-policy
> without walking on anyone else.

Maybe, but then what do you do when the xinclude element
has an attribute of the same name as the root included
element.  Say, like id.

Received on Monday, 31 October 2011 18:12:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:43 UTC