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 17223 - [QT3TS] Serialization-018
Summary: [QT3TS] Serialization-018
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Dennis Knochenwefel
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-28 13:58 UTC by Tim Mills
Modified: 2012-06-01 10:47 UTC (History)
2 users (show)

See Also:

Attachments

Description Tim Mills 2012-05-28 13:58:15 UTC 
This test expects the wrong error code.

"INVALID_VALUE" is a valid string, and is therefore a valid value for normalization-form.  However, it may not be a _supported_ normalization form.  The error should therefore be SESU0011, not SEPM0016.

declare namespace output = "http://www.w3.org/2010/xslt-xquery-serialization";
declare option output:normalization-form "INVALID_VALUE";
<result>ok</result>

Incidentally, XSLT requires such normalization-form values to be nmtokens.  The serialization spec seems to make no such restriction.
Comment 1 O'Neil Delpratt 2012-05-29 08:52:06 UTC 
Hi Dennis please may you comment on this bug issue. Thanks
Comment 2 Dennis Knochenwefel 2012-05-29 09:23:03 UTC 
The bug report makes sense to me. Will fix this. Thanks.

The requirement to use nmtokens could be an improvement for the spec for most string-param-type serialization-parameter-element. Why isn't xs:token used here?
Comment 3 O'Neil Delpratt 2012-06-01 07:42:40 UTC 
Bug fixed. Thanks Dennis
Comment 4 Tim Mills 2012-06-01 10:47:52 UTC 
Confirmed fixed.