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

[Bug 28540] New: [FO30] [FO31] defaults for serialization parameters with fn:serialize not defined

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

            Bug ID: 28540
           Summary: [FO30] [FO31] defaults for serialization parameters
                    with fn:serialize not defined
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3 & XPath 3 Test Suite
          Assignee: oneil@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

The function fn:serialize (section 14.7.3 9 FO31 and 14.9.3 in FO30) does not
enlist what the defaults are for the serialization. It stands to reason that it
takes similar defaults as defined in XSLT for the xsl:output method, but I
couldn't find this referenced in the text.

The reference to XDM 3.0 and 3.1 respectively does not solve this issue either,
specifically, that specification says:

   There are a number of parameters that influence how serialization is 
   performed. Host languages MAY allow users to specify any or all of these 
   parameters, but they are not REQUIRED to be able to do so. However, the 
   host language specification MUST specify how the values of all applicable 
   parameters are to be determined.

The crux is in the last sentence, which I understand such that the host
language (XPath F&O) should define these defaults, esp. since no defaults are
mentioned in XDM.

I figured for a moment that booleans should default to "no", method to "xml",
but for instance escape-uri-attributes should probably default to "yes" and
there are other enumerations with unclear defaults, like encoding and
omit-xml-declaration (default for a file is probably "no", as with XSLT, but
default for inlining, as the most common use-case, should probably be "yes").

Perhaps any and all of these settings are supposed to be implementation
dependent (which would make calls to this function non-interoperable unless you
provide a fully filled set of serialization options), but if so, I think we
should say so in the spec.

Other perhaps: if the idea is that the host language of XPath (i.e., XSLT or
XQuery) should define these defaults, then also, I think we should emphasize
that, and specify it in the host languages.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 22 April 2015 22:48:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 22 April 2015 22:48:06 UTC