W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2015

[Bug 28948] New: [QT3TS] K2-Serialization-29: whitespace in option declarations

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Jul 2015 22:52:32 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28948-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28948

            Bug ID: 28948
           Summary: [QT3TS] K2-Serialization-29: whitespace in option
                    declarations
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3 & XPath 3 Test Suite
          Assignee: oneil@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

Test K2-Serialization-29 tests that leading and trailing whitespace is
permitted in option declarations, e.g.

declare option output:indent "    yes    ";

and assumes that it is permitted. But I can't see anything in the spec that
allows one to assume this. Certainly in the serialization parameter file, the
schema derives the yesNo type as an enumeration restricting xs:string, and
xs:string does not normalize whitespace.

Another example is

declare option output:method "  Q{}xml&#x9;"

The spec is clear that character references are allowed and that EQName syntax
is allowed, but there's nothing that explicitly allows the whitespace. The
EQName syntax itself doesn't.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 14 July 2015 22:52:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 July 2015 22:52:35 UTC