<?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>6093</bug_id>
          
          <creation_ts>2008-09-18 14:25:41 +0000</creation_ts>
          <short_desc>[XSLT 2.0] Incorrect inline schema example</short_desc>
          <delta_ts>2008-10-02 16:46:28 +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>XSLT 2.0</component>
          <version>Recommendation</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows NT</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Michael Kay">mike</reporter>
          <assigned_to name="Michael Kay">mike</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>21936</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2008-09-18 14:25:41 +0000</bug_when>
    <thetext>Ken Holman has pointed out in private email that the example in section 3.14 is incorrect:

&lt;xs:variable name=&quot;condition&quot; select=&quot;&apos;yes&apos;&quot; as=&quot;local:yes-no&quot;/&gt;

It should read

&lt;xs:variable name=&quot;condition&quot; select=&quot;local:yes-no(&apos;yes&apos;)&quot; as=&quot;local:yes-no&quot;/&gt;

Because declaring the type of a variable does not by itself force a cast to that type.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>21937</commentid>
    <comment_count>1</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2008-09-18 14:37:27 +0000</bug_when>
    <thetext>&gt; declaring the type of a variable does not by itself force a cast to that type.

Which raises the question, as an enhancement suggestion, whether this rule really improves the usability of the language.

What adverse consequences would follow if the XPath function conversion rules were changed so that if the required type is derived by restriction from the supplied type, an implicit cast takes place?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22058</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2008-09-28 10:21:40 +0000</bug_when>
    <thetext>Erratum E28 has been created to correct this error.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>