XPointer extensions

I'm looking at the XPointer "extensions" section.

I don't understand the need for "/", "id()". Are they maybe historical?

range::, string:: and unique() could go into XPath (2.0?). They are as
useful there as they are in XLink.

Re: origin()

Don't we also need target(), linking-element() and so forth?

My big concern is that this origin() thing is closely related to how we
handle behavior, style sheets, the whole kit-n-kaboodle. If we defined
XPointer to allow extension functions as XPath does then we could lift
origin() into XLink and figure it out with everything else.

Should here be here() or $here? And couldn't it (for the sake of
argument) go in XPath and provide a way of looking things up in the XSLT
stylesheet itself? For instance an <author> in the colophon?

 Paul Prescod

Received on Wednesday, 11 August 1999 13:49:10 UTC