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 28292 - [XP3.1] 2.4.3 Effective Boolean Value linking practice
Summary: [XP3.1] 2.4.3 Effective Boolean Value linking practice
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Linux
: P2 minor
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-23 00:52 UTC by Patrick Durusau
Modified: 2015-07-10 23:03 UTC (History)
1 user (show)

See Also:


Attachments

Description Patrick Durusau 2015-03-23 00:52:41 UTC
2.4.3 Effective Boolean Value

"[Definition: The effective boolean value of a value is defined as the result of applying the fn:boolean function to the value, as defined in [XQuery and XPath Functions and Operators 3.1].]"

An interesting case because the reference here points to the bibliography but if you go to [XQuery and XPath Functions and Operators 3.1].], the reference there, at

http://www.w3.org/TR/xpath-functions-31/#func-boolean points to: Section 2.4.3 Effective Boolean Value XP30, which is: link: http://www.w3.org/TR/xpath-30/#id-ebv

Precisely the behavior I have been arguing favors the reader. Which also happens at: 


2 Basics

***
[122]   	QName	   ::=   	[http://www.w3.org/TR/REC-xml-names/#NT-QName]Names
[123]   	NCName	   ::=   	[http://www.w3.org/TR/REC-xml-names/#NT-NCName]
***

I have not catalogued all the references with precise locations.
Comment 1 Jonathan Robie 2015-07-10 23:03:48 UTC
Done.