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

[Bug 29024] fn:serialize needs clarification when method parameter set from a map

From: <bugzilla@jessica.w3.org>
Date: Wed, 09 Sep 2015 11:38:28 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29024-523-5G7n3wU6pY@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29024

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
I intend to resolve this by replacing rule 3 (a-g) with a reference to a table
which enumerates all the serialization parameters, which can then be merged
with the table in rule 4 giving default values. The table will give for each
parameter, the expected type, and the mapping of the supplied value to the
values as described in the serialization spec.

In all cases, an empty sequence is permitted as the value, and is equivalent to
omitting the parameter from the map; the fourth column gives the default value
that applies both when the parameter is omitted and when it is present with an
empty sequence as its value. The third column gives the interpretation of the
value in cases where further explanation is needed.

parameter name | required type | meaning | default

allow-duplicate-names | xs:boolean? | true->yes, false->no | "no"
byte-order-mark | xs:boolean? | true->yes, false->no | "no"
cdata-section-elements | xs:QName* | | ()
doctype-public | xs:string? | a zero-length string or () represents "absent" |
()
doctype-system | xs:string? | a zero-length string or () represents "absent" |
()
encoding | xs:string? | | "utf-8"
escape-uri-attributes | xs:boolean? | true->yes, false->no | "no"
html-version | xs:decimal? | | 5
include-content-type | xs:boolean? | true->yes, false->no | "yes"
indent | xs:boolean? | true->yes, false->no | "no"
item-separator xs:string? | | ()
json-node-output-method | union(xs:string, xs:QName)? | see Note 1 | "xml"
media-type | xs:string? | | (a media type suitable for the chosen method)
method | union(xs:string, xs:QName)? | see Note 1 | "xml"
normalization-form | xs:string? | "none"
omit-xml-declaration | xs:boolean? | true->yes, false->no | "yes"
standalone | xs:boolean? | true->yes, false->no, ()->omit | omit
suppress-indentation xs:QName* | | ()
undeclare-prefixes | xs:boolean? | true->yes, false->no | "no"
use-character-maps | map(xs:string, xs:string)? | see Note 2 | map{}
version | xs:string? | | "1.0"

Note 1: If a QName is supplied, then it must have a non-absent namespace URI.

Note 2: a map, whose keys are the characters to be mapped (as xs:string
instances), and whose corresponding values are the strings to be substituted
for these characters. The ·option parameter conventions· apply recursively to
this nested map.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 9 September 2015 11:38:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 September 2015 11:38:33 UTC