- From: Daniel Veillard <daniel@veillard.com>
- Date: Fri, 7 Dec 2007 10:05:16 +0100
- To: "Grosso, Paul" <pgrosso@ptc.com>
- Cc: public-xml-core-wg@w3.org
On Thu, Dec 06, 2007 at 11:09:52PM -0500, Grosso, Paul wrote: > > > > > -----Original Message----- > > From: public-xml-core-wg-request@w3.org > > [mailto:public-xml-core-wg-request@w3.org] On Behalf Of Norman Walsh > > Sent: Thursday, 2007 December 06 16:47 > > To: public-xml-core-wg@w3.org > > Subject: XInclude and fragids for parse=text > > > > XInclude says an xpointer is forbidden when parse=text. > > > > We should fix that. This will become an RFC: > > > > http://www.ietf.org/internet-drafts/draft-wilde-text-fragment-09.txt > > I suppose we could do something if we wanted to, > but at present, we say that value of the xpointer > attribute is an XPointer, not an arbitrary fragment > identifier, and the RFC you quote about defines a > fragment identifier for plain text, but that's not > an XPointer. > > So I don't think we're saying anything inaccurate. > > Changing XInclude so that parse=text references > allow a fragment identifier is an enhancement > request, and not something we necessarily have to do. > > All the same, we could consider it. As you say, it > would seem to require a 1.1 version. Agreed it's sad to not be able to include text chunk when this becomes a final RFC. The problem is as the spec stands we would need a syntactic extension, allowing 'xpointer' on parse='text' would be a bit weird. So that woudl mean an extra attribute definition. Still I think this is worth doing, and if we plan this I may even take the time of an implementation as the RFC looked sane to me when I quickly looked at it, Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/
Received on Friday, 7 December 2007 09:04:38 UTC