[Bug 21568] New: Incorrect expected result for FOTS tests function-decl-reserved-function-names-001,function-decl-reserved-function-names-003,...

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21568

            Bug ID: 21568
           Summary: Incorrect expected result for FOTS tests
                    function-decl-reserved-function-names-001,function-dec
                    l-reserved-function-names-003,...
    Classification: Unclassified
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3 & XPath 3 Test Suite
          Assignee: oneil@saxonica.com
          Reporter: nbrinza@gmail.com
        QA Contact: public-qt-comments@w3.org

A number of tests in the FOTS testsuite in the prod-FunctionDecl set have
incorrect results. E.g. the function-decl-reserved-function-names-001:

declare default function namespace
"http://www.w3.org/2005/xquery-local-functions";
declare function attribute() { fn:true()};
local:attribute()

expects the result "true()", i.e. it considers the query to be syntactically
correct with respect to the XQuery 1.0 specification. Yet the XQuery 1.0
specification, just as 3.0, has a list of reserved function names:
http://www.w3.org/TR/xquery/#id-reserved-fn-names , and "attribute" is among
them.

The lists of tests that have this problem is:
function-decl-reserved-function-names-001
function-decl-reserved-function-names-003
function-decl-reserved-function-names-005
function-decl-reserved-function-names-007
function-decl-reserved-function-names-009
function-decl-reserved-function-names-013
function-decl-reserved-function-names-015
function-decl-reserved-function-names-019
function-decl-reserved-function-names-021
function-decl-reserved-function-names-023
function-decl-reserved-function-names-025
function-decl-reserved-function-names-029
function-decl-reserved-function-names-031

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 3 April 2013 14:03:56 UTC