<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>1467</bug_id>
          
          <creation_ts>2005-05-19 19:30:15 +0000</creation_ts>
          <short_desc>[FO] Cleanup of argument cardinality</short_desc>
          <delta_ts>2005-09-29 11:22:09 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>XPath / XQuery / XSLT</product>
          <component>Functions and Operators 1.0</component>
          <version>Last Call drafts</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows XP</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>1422</blocked>
    
    <blocked>1468</blocked>
    
    <blocked>1469</blocked>
    
    <blocked>1470</blocked>
    
    <blocked>1471</blocked>
    
    <blocked>1472</blocked>
    
    <blocked>1473</blocked>
    
    <blocked>1474</blocked>
    
    <blocked>1475</blocked>
    
    <blocked>1476</blocked>
    
    <blocked>1477</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Michael Rys">mrys</reporter>
          <assigned_to name="Ashok Malhotra">ashok.malhotra</assigned_to>
          
          
          <qa_contact name="Mailing list for public feedback on specs from XSL and XML Query WGs">public-qt-comments</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>3109</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Rys">mrys</who>
    <bug_when>2005-05-19 19:30:15 +0000</bug_when>
    <thetext>Based on my action item at the F2F to provide a scrub of the FO document 
regarding bug 1422 to look for other places where we may need to consider 
allowing empty sequence to provide static typing implementations the ability 
to call the functions without forcing users through major hoops, I came across 
two categories of functions:

1. Positional arguments being wrong.
2. Recently introduced functions that have inconsistent parameters.

Note that the design has been that we do not allow empty for &quot;steering&quot; 
arguments that are most likely being given with a literal value. For all 
others, we should statically accept empty since the static type for the 
argument expressions will infer a type that allows empty in most cases.

I will file separate dependent bugs for each function.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>5101</commentid>
    <comment_count>1</comment_count>
    <who name="Mary Holstege">holstege</who>
    <bug_when>2005-07-21 20:58:38 +0000</bug_when>
    <thetext>The working group considered this comment at its meeting today
and decided not to accept it.

A number of divergent reasons were given for not accepting these changes, 
including:

For some of the specific cases, returning empty sequences instead of 
failing were regarded as unhelpful to users.  Providing errors improves
usability, it was felt, rather than undermining it.

The consistency argument was not compelling, in that consistency with some 
functions would speak to one decision, and consistency with other functions 
would speak to the opposite decision. The spec has a whole range of functions 
and operators, some of which accept empty sequences and some of which don&apos;t, so 
full consistency is not achievable.

For the &quot;class B&quot; functions, changing the semantics of well-settled and long-
standing functions in the absense of a compelling argument to change is 
disruptive.

 </thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>