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

[Bug 28140] New: Options of fn:serialize

From: <bugzilla@jessica.w3.org>
Date: Wed, 04 Mar 2015 22:04:20 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28140-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28140

            Bug ID: 28140
           Summary: Options of fn:serialize
           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: christian.gruen@gmail.com
        QA Contact: public-qt-comments@w3.org

The fn:serialize function is used a lot in practice. However, our users report
back to us that the declaration of serialization parameters is perceived as
inconvenient, and the namespace URI is often forgotten.

It would be great if the last function signature of fn:serialize could be
extended such that it accepts both element(output:serialization-parameters)?
and map(*):

1) Existing syntax:

  fn:serialize(map { 'year': 1984 },
    <output:serialization-parameters
      xmlns:output="http://www.w3.org/2010/xslt-xquery-serialization">
      <output:method value="json"/>
    </output:serialization-parameters>
  )

2) Map syntax:

  fn:serialize(map { 'year': 1984 }, map { 'method': 'json })

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 4 March 2015 22:04:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:53 UTC