This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29943 - [FO31] fn:transform serialization parameters
Summary: [FO31] fn:transform serialization parameters
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-18 10:49 UTC by Tim Mills
Modified: 2016-12-16 19:55 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2016-10-18 10:49:48 UTC 
There's an inconsistency between fn:serialize and fn:transform in the handling of serialization parameters.

fn:serialize can take a map of serialization parameters in which

"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."

whereas in the case of fn:transform, the serialization parameters map

"Standard parameters such as method and indent are supplied as QNames in no namespace."

Could we please choose one convention for the two functions?

See related bug

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29373
Comment 1 Tim Mills 2016-10-18 11:16:09 UTC 
Furthermore, fn:serialize gives a table describing the serialization parameters.  It would be nice if fn:transform referenced this table.
Comment 2 Michael Kay 2016-10-18 16:01:15 UTC 
The WG agreed that we should bring fn:transform into line with fn:serialize.
Comment 3 Michael Kay 2016-10-19 08:47:34 UTC 
Resolved as described in bug #29940