RE: XInclude @xpointer when parse="text"

> -----Original Message-----
> From: Grosso, Paul [mailto:pgrosso@ptc.com]
> Sent: Wednesday, 2011 November 16 11:44
> To: public-xml-core-wg@w3.org
> Subject: XInclude @xpointer when parse="text"

> At the f2f, we outlined three possible choices:
> 
> 1.  allow use of the @xpointer attribute when parse=text
> 2.  add a new "@textptr" attribute to use when parse=text
> 3.  add a new "@fragid" attribute to use in all cases and
>     possibly deprecate the @xpointer attribute

What would be the value of the attribute in any of these cases
when parse=text?  Would it be just a single fragment identifier
conforming to RFC 5147?  Or would it follow some sort of
xpointer syntax that allows for multiple schemes?  And if the
latter, do we need to have a scheme name for the RFC 5147 syntax?

If there is only one way (5147) to address into a text resource,
then I'm not sure there's a point to allowing multiple schemes,
but then #1 would appear problematic unless we say that the
@xpointer attribute has different syntax depending on the value
of @parse.  That would cause me to prefer #2.

paul

Received on Wednesday, 16 November 2011 18:11:31 UTC