This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Many descriptions say that a function "backs up" an operator. For instance: <snip> 9.2.2 op:boolean-less-than op:boolean-less-than($arg1 as xs:boolean, $arg2 as xs:boolean) as xs:boolean Summary: Returns true if $arg1 is false and $arg2 is true. Otherwise, returns false. This function backs up the "lt" and "ge" operators on xs:boolean values. </snip> We should define this term or use a different term.
I agree that the term "backs up" is a very ugly one, unrelated to any usual English meaning of this verb, and this reflects the fact that the relationship of these function definitions to the operators they underpin is unclear to many readers. I propose to use the phrase "This function defines the semantics of the XX operator..." Note also, there are numerous occurrences of the phrase "This functions backs up" which should be "This function...". I have taken the liberty of classifying this as editorial. I am proposing to include this change with a package of similar editorial improvements to the spec.
(In reply to comment #1) > I propose to use the phrase "This function defines the semantics of the XX > operator..." Perfect! Jonathan
This editorial issue is fixed in the current editor's draft of F+O 1.1.