W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2004

Re: [XPath] 3.2.1 Steps: fn:get-namespace-uri-for-prefix

From: Don Chamberlin <chamberl@almaden.ibm.com>
Date: Mon, 20 Sep 2004 11:40:58 -0400
To: David Carlisle <davidc@nag.co.uk>
Cc: public-qt-comments@w3.org
Message-ID: <OFEB67EEF3.12A0440E-ON88256F15.0055F360-88256F15.005616AC@us.ibm.com>
I've corrected the function names in the "Steps" section of the XPath 
document as you suggested.
Thanks for submitting this correction.
--Don Chamberlin

David Carlisle <davidc@nag.co.uk> 
Sent by: public-qt-comments-request@w3.org
07/26/2004 03:50 AM


[XPath] 3.2.1 Steps: fn:get-namespace-uri-for-prefix

3.2.1 says:

Applications needing information about the in-scope namespaces of an
element should use the functions fn:get-in-scope-prefixes and

It would be helpful if the two function names were hyperlinked.
the names are (now) incorrect: it should be




The "inscope namespaces" feature is closely modelled on the facilities
offered by namespace nodes, however it could, I believe, be extended to
deal with a case that is rather problemtic to deal with in Xpath 1.

If attributes as well as elements had an in scope namespaces property
and attribute nodes could be supplied to fn:in-scope-prefixes then
prefixes contained in free standing attribute node values (such as
Xpath expressions) could be safely preserved. In the original mapping
from infoset/psvi the in-scope namespaces of an attribute would be that
of its parent element. On serialisation you (as language designers, not
the user) would have a choice of whether to just drop in scope
namespaces from attributes, or whether to make "namespace fixup" ensure
that an element always had namespaces in scope if they are in scope on
an attribute.

You'll probably say that it's too late for new features.


This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
Received on Monday, 20 September 2004 15:41:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:59 UTC