This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
Hi Dennis please may you comment on this bug issue. Thanks
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?
Bug fixed. Thanks Dennis
Confirmed fixed.