<?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>20845</bug_id>
          
          <creation_ts>2013-02-01 11:21:29 +0000</creation_ts>
          <short_desc>[XT3TS] regex-syntax and XSLT 3.0</short_desc>
          <delta_ts>2015-05-17 21:09:43 +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 3.0 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>http://www.plam.cantech.bg</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="Abel Braaksma">abel.online</assigned_to>
          <cc>abel.braaksma</cc>
    
    <cc>mike</cc>
    
    <cc>plam</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>82472</commentid>
    <comment_count>0</comment_count>
    <who name="Tim Mills">tim</who>
    <bug_when>2013-02-01 11:21:29 +0000</bug_when>
    <thetext>A number of regex-syntax tests use new F&amp;O 3.0 regex syntax features.  When running of an XSLT 2.0 processor these tests generate an error (as is expected by the test case).

When a stylesheet is marked as XSLT 2.0, but the processor is XSLT 3.0, I presume the syntax accepted should be F&amp;O 3.0, and thus the test cases need to be forked.  Possibly affected tests are:

 regex-syntax-0766	
 regex-syntax-0845	
 regex-syntax-0846	
 regex-syntax-0847	
 regex-syntax-0848	
 regex-syntax-0849	
 regex-syntax-0850	
 regex-syntax-0851	
 regex-syntax-0852	
 regex-syntax-0853	
 regex-syntax-0855	
 regex-syntax-0856	
 regex-syntax-0857	
 regex-syntax-0858	
 regex-syntax-0859	
 regex-syntax-0860	
 regex-syntax-0861	
 regex-syntax-0864	
 regex-syntax-0865	
 regex-syntax-0866	
 regex-syntax-0877	
 regex-syntax-0878	
 regex-syntax-0880	
 regex-syntax-0883	
 regex-syntax-0942	
 regex-syntax-0943	
 regex-syntax-0944	
 regex-syntax-0945	
 regex-syntax-0946	
 regex-syntax-0947	
 regex-syntax-0948	
 regex-syntax-0949	
 regex-syntax-0950	
 regex-syntax-0951	
 regex-syntax-0952	
 regex-syntax-0953	
 regex-syntax-0954	
 regex-syntax-0955</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85602</commentid>
    <comment_count>1</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-04-05 13:49:13 +0000</bug_when>
    <thetext>A note mainly for myself: Saxon is passing these tests &quot;by accident&quot;, because a stylesheet defined as part of a shared test environment is always compiled/executed in 2.0 mode, regardless of the individual test dependencies.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>119335</commentid>
    <comment_count>2</comment_count>
    <who name="Abel Braaksma">abel.braaksma</who>
    <bug_when>2015-04-07 23:34:15 +0000</bug_when>
    <thetext>On Oct 10, 2013, Michael Kay fixed these tests to support XSLT 3.0, but with dropping XT3 test coverage support for XSLT 2.0.

Today I committed a forked version for XSLT 2.0 of these tests, which are in their own folder and test category. It is based on a version of this file from before the move and fixes required for XSLT 3.0.

Considered fixed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>119345</commentid>
    <comment_count>3</comment_count>
    <who name="Tim Mills">tim</who>
    <bug_when>2015-04-08 09:46:27 +0000</bug_when>
    <thetext>Since this change, our processor reports errors (FORX0002) in

 regex-syntax-xslt20-0056	
 regex-syntax-xslt20-0086	
 regex-syntax-xslt20-0102	
 regex-syntax-xslt20-0985

e.g. in the pattern &quot;^([^a-d-b-c])$&quot; the second &apos;-&apos; between &apos;d&apos; and &apos;b&apos; is invalid.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>119385</commentid>
    <comment_count>4</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2015-04-08 18:23:08 +0000</bug_when>
    <thetext>The rules for hyphens in constructs like &quot;^([^a-d-b-c])$&quot; in XSD 1.0 are pretty unfathomable. They have been considerably cleaned up in XSD 1.1. So I think this is an XSD 1.0/1.1 distinction rather than an XSLT 2.0/3.0 one.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120216</commentid>
    <comment_count>5</comment_count>
    <who name="Abel Braaksma">abel.braaksma</who>
    <bug_when>2015-05-06 21:31:28 +0000</bug_when>
    <thetext>As far as I know, these tests were present in the XSLT 2.0 version of the test suite and have not been altered. That is not to say that there isn&apos;t a bug in them, but I am unsure as what or how to fix them.

Should we mark the mentioned tests as XSD 1.1? Any other way forward?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120331</commentid>
    <comment_count>6</comment_count>
    <who name="Abel Braaksma">abel.braaksma</who>
    <bug_when>2015-05-17 21:09:43 +0000</bug_when>
    <thetext>I have fixed the tests provisionally with a dependency on XSD 1.1 (satisfies: false), assuming that if XSD 1.0 is used for regex syntax, this syntax is valid, but if XSD 1.1 is used, it is not.

Please reopen if this doesn&apos;t resolve the issue.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>