<?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>21838</bug_id>
          
          <creation_ts>2013-04-26 09:06:03 +0000</creation_ts>
          <short_desc>[XQ3TS] require-feature-list-1-ns-1, 2, require-feature-list-1-s</short_desc>
          <delta_ts>2013-05-07 16:17:42 +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>XQuery 3 &amp; XPath 3 Test Suite</component>
          <version>Candidate Recommendation</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows NT</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</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>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Tim Mills">tim</reporter>
          <assigned_to name="Ghislain Fourny">g</assigned_to>
          <cc>oneil</cc>
          
          <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>86837</commentid>
    <comment_count>0</comment_count>
    <who name="Tim Mills">tim</who>
    <bug_when>2013-04-26 09:06:03 +0000</bug_when>
    <thetext>These tests import a module which is missing from the environment.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>87148</commentid>
    <comment_count>1</comment_count>
    <who name="O&apos;Neil Delpratt">oneil</who>
    <bug_when>2013-05-02 09:41:57 +0000</bug_when>
    <thetext>I think this might be the intent of the test case, but I am asking Ghislain to comment here.

Please observe:

&lt;dependency type=&quot;feature&quot; value=&quot;higherOrderFunctions&quot; satisfied=&quot;false&quot;/&gt;

This in affect switches off the HOF feature in the implementation so any call to require-feature on HOF should throw an error in the test case. However, I am still uncomfortable with this, I think we are over using the framework of the test suite somewhat. In our implementation we are not even running this test because the satisfied=false on the dependency.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>87149</commentid>
    <comment_count>2</comment_count>
    <who name="Tim Mills">tim</who>
    <bug_when>2013-05-02 09:45:39 +0000</bug_when>
    <thetext>(In reply to comment #1)

&gt; This in affect switches off the HOF feature in the implementation so any
&gt; call to require-feature on HOF should throw an error in the test case.

I&apos;m fairly sure that this isn&apos;t the expected behaviour.  If the implementation can enable a feature in response to a require-feature, it is free to do so, and only raise an error if it can&apos;t.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>87154</commentid>
    <comment_count>3</comment_count>
    <who name="Ghislain Fourny">g</who>
    <bug_when>2013-05-02 10:13:11 +0000</bug_when>
    <thetext>Good catch, I added the module dependency, awaiting your confirmation that it works for you.

I agree with Tim&apos;s comment 2, i.e., the WG made an explicit decision that it is okay for an implementation to activate a feature even if it had previously deactivated it following the dependency of false on that feature.

It comes down to saying that a dependency of false does not mean that the feature must be &quot;not supported&quot; for the test to be run, but that it must be &quot;not activated&quot; by default for the test to be run.

It is fine for an implementation that does support a feature to not run tests with a dependency of false on that feature, if it is unable to deactivate it, so I also agree with O&apos;Neil&apos;s last sentence in comment 1.

Does it make sense?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>87349</commentid>
    <comment_count>4</comment_count>
    <who name="O&apos;Neil Delpratt">oneil</who>
    <bug_when>2013-05-07 16:17:42 +0000</bug_when>
    <thetext>This makes sense. I confirm tests have been updated.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>