[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [xml] Potential wrong usage of xmlIsID() in tree.c
- From: Daniel Veillard <veillard redhat com>
- To: Kasimier Buchcik <K Buchcik 4commerce de>
- Cc: Rob Richards <rrichards ctindustries net>, ML-libxml2 <xml gnome org>
- Subject: Re: [xml] Potential wrong usage of xmlIsID() in tree.c
- Date: Mon, 20 Feb 2006 13:56:24 -0500
On Mon, Feb 20, 2006 at 06:43:34PM +0100, Kasimier Buchcik wrote:
> > line with how XInclude works and imo would make it easy for a user to
>
> I took a look at the XInclude spec, but it seems - to me - to make no
> explicit mention of what happens with ID attributes. It does say what
> to do with IDREF attributes though.
>
> In the "Fragment Inclusion Example" of this spec, the included
> fragment has some ID attributes, which are converted to non-ID
> attributes in the resulting infoset. So I wonder if this example
> is just broken, or is preserving IDness from XIncluded fragments
> just a myth? Did I miss something?
> http://www.w3.org/TR/xinclude/#fragment-example
Not an error. It is intended.XInclude works at the infoset level,
i.e. IDNess is computed at parse time but a property of the node
(or rather the attribute on the node), and that property is maintained
when genertaing the resulting XIncluded tree.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
veillard redhat com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]