W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2016

[Bug 29631] New: [FO31] fn:serialize options map

From: <bugzilla@jessica.w3.org>
Date: Tue, 17 May 2016 10:27:34 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29631-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 29631
           Summary: [FO31] fn:serialize options map
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: tim@cbcl.co.uk
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

The specification says in 14.7.3 fn:serialize

"The key of the entry is an xs:string value in the cases of parameter names
defined in these specifications, or an xs:QName (with non-absent namespace) in
the case of implementation-defined serialization parameters."

and test case serialize-xml-120

let $params := map { QName("","indent") : true() }
return serialize(., $params)

expects SEPM0017.

However, in 1.5 Options we read

"It is not an error if the options map contains options with names other than
those described in this specification. Implementations may attach an
·implementation-defined· meaning to such entries, and may define errors that
arise if such entries are present with invalid values. Implementations must
ignore such entries unless they have a specific ·implementation-defined·
meaning. Implementations that define additional options in this way should use
values of type xs:QName as the option names, using an appropriate namespace."

which seems to say this option can be ignored, or handled in an
implementation-defined way.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 17 May 2016 10:27:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 17 May 2016 10:27:39 UTC