This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6844 - [FO] Incorrect description of dm:base-uri in fn:base-uri
Summary: [FO] Incorrect description of dm:base-uri in fn:base-uri
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Recommendation
Hardware: PC Windows XP
: P5 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-24 16:11 UTC by Henry Zongaro
Modified: 2009-07-11 11:27 UTC (History)
1 user (show)

See Also:


Attachments

Description Henry Zongaro 2009-04-24 16:11:02 UTC
Some colleagues and I noticed a minor inconsistency in the description of the dm:base-uri accessor that appears in the definition of fn:base-uri with the actual definition of the accessor in the Data Model Recommendation.

Section 2.5.4 of the F&O PER [1] states:  "Returns the value of the base-uri URI property for $arg as defined by the accessor function dm:base-uri() for that kind of node....  Document, element and processing-instruction nodes have a base-uri property which may be empty. The base-uri property of all other node types is the empty sequence."  However, according to sections 6.3.2, 6.6.2 and 6.7.2 of the Data Model PER,[2,3,4] the value of the dm:base-uri accessor for attribute, comment and text nodes is not necessarily the empty sequence.


[1] http://www.w3.org/TR/2009/PER-xpath-functions-20090421/#func-base-uri
[2] http://www.w3.org/TR/2009/PER-xpath-datamodel-20090421/#AttributeNodeAccessors
[3] http://www.w3.org/TR/2009/PER-xpath-datamodel-20090421/#CommentNodeAccessors
[4] http://www.w3.org/TR/2009/PER-xpath-datamodel-20090421/#TextNodeAccessors
Comment 1 Michael Kay 2009-05-12 15:31:35 UTC
Noted that this was raised as bug #6340 against the F+O 1.1 spec.

Decided today that we should apply the same fix as an erratum to the 1.0 spec.
Comment 2 Jim Melton 2009-07-03 19:51:06 UTC
I am marking this RESOLVED FIXED because WG has made the decision. (The editor
will implement the solution on his own timetable.) If you're satisfied with
this resolution, please mark the bug CLOSED. 
Comment 3 Henry Zongaro 2009-07-11 11:27:41 UTC
Yes, satisfied.