W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > December 2007

RE: XInclude and fragids for parse=text

From: Grosso, Paul <pgrosso@ptc.com>
Date: Thu, 6 Dec 2007 23:09:52 -0500
Message-ID: <CF83BAA719FD2C439D25CBB1C9D1D30209A7DC6A@HQ-MAIL4.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: 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.

paul
Received on Friday, 7 December 2007 04:10:48 UTC

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