11014 2010-10-12 14:46:53 +0000 Boolean literals? 2010-12-03 20:25:22 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.0 Member-only Editors Drafts PC Linux RESOLVED FIXED P2 normal --- 1 jonathan.robie jonathan.robie john.snelson josh.spiegel mike public-qt-comments oldest_to_newest 41107 0 jonathan.robie 2010-10-12 14:46:53 +0000 The following text in "3.1.1 Literals" implies, but does not state, that fn:true() and fn:false() can be used to represent Boolean literals: "The xs:boolean values true and false can be represented by calls to the built-in functions fn:true() and fn:false(), respectively." This comes immediately after a list of examples of literals, and immediately before this text: "Values of other atomic types can be constructed by calling the constructor function for the given type." Do we intend to allow these to be used as literals? The grammar does not support them. We need to clarify this text one way or another. 41112 1 mike 2010-10-12 14:59:38 +0000 The function calls true() and false() are not literals, but they fulfil the same role as literals, in that you can use them in an expression anywhere you can use a literal. I think that's what the text is trying to say. 41773 2 josh.spiegel 2010-10-26 17:31:00 +0000 Related to this, in section 4.15 Annotations it states: "An annotation always has a value. If no explicit value is provided, the value is fn:true(). " But the grammar for an annotation is: [27] Annotation ::= "%" EQName ("(" Literal ("," Literal)* ")")? So it seems that a user can not set the value of an annotation to fn:false() which is strange given the default value is fn:true()? 41967 3 jonathan.robie 2010-11-02 17:47:45 +0000 The Working Group decided to fix this by removing the last sentence in the following excerpt: (In reply to comment #2) > Related to this, in section 4.15 Annotations it states: > > "An annotation always has a value. If no explicit value is provided, the value > is fn:true(). " Editorially, the following may be clarified: "The xs:boolean values true and false can be represented by calls to the built-in functions fn:true() and fn:false(), respectively." 43034 4 john.snelson 2010-12-03 20:25:22 +0000 This has now been fixed.