This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I think a new error code is needed for the case that the 2nd arg $params of fn:serialize() is supplied as a map, but the map contains parameter values which are not of the required type. The error conditions section currently says: 'If any serialization error occurs, including the detection of an invalid value for a serialization parameter, this results in the fn:serialize call failing with a dynamic error.' But I don't think this should cover the case above.
The decision just made on 28836 means that this should result in XPTY0004.
Note of further explanation: being of the wrong type here means, for example supplying a value for standalone that is not of type xs:boolean?. We're not validating against the schema definitions of the serialization parameters here. Specifying method="yaml" is not a type error in this sense, it is an invalid value for the parameter, and gives the SEPM error code for invalid serialization parameter values.
Applied the changes.