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

[Bug 28486] New: [XQ 3.1] Lexical form of serialization parameters

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Apr 2015 08:47:10 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28486-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28486

            Bug ID: 28486
           Summary: [XQ 3.1] Lexical form of serialization parameters
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.1
          Assignee: jonathan.robie@gmail.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

XQuery section 2.2.4 defines XQuery serialization parameters ("declare output")
by reference to Serialization section 3.

But serialization section 3 describes only the value space of these parameters,
not their lexical form. It's up to the host language to specify the lexical
form, but it fails to do so.

For example, a number of serialization parameters are defined to contain (one
or more) expanded QNames. (method, cdata-section-elements,
suppress-indentation, json-node-output-method). The term "expanded QName" links
(indirectly) to the definition in XPath 3.1. The definition of "expanded QName"
describes the value space, not the lexical representation.

So it's unclear how expanded QNames are actually written in the declare output
declaration.  There needs to be a statement that a QName can be written as an
EQName; there should also be a statement about the default namespace that is
used when a name is written as a simple NCName (it should be the default
namespace for elements and types).

The problem applies to all serialization parameters, but it is particularly
acute for those containing QNames.

Another aspect of the lexical representation that is left underspecified is
boundary whitespace: it should say that for list-valued parameters such as
suppress-indentation that the list is whitespace-separated, and for all
parameters, it should say that leading and trailing whitespace is trimmed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 14 April 2015 08:47:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 April 2015 08:47:13 UTC