List-valued options represented as arrays

[GuntherRademacher]

The specification of the of the option parameter conventions contains this:

In cases where an option is list-valued, by convention the function should accept either a sequence or an array: but this rule applies only if the specification of the option explicitly accepts either. Accepting a sequence is convenient if the value is generated programmatically using an XPath expression; while accepting an array allows the options to be held in an external file in JSON format, to be read using a call on the fn:json-doc function.

In particular, it says

...this rule applies only if the specification of the option explicitly accepts either...

However I could not find any option that explicitly makes use of "accepts either" in the specification. In the tests, I found two cases where arrays are passed as option values: numberformat-510 (here the option isn't even list-valued), and serialize-xml-106a.

I am wondering whether the above paragraph might be superfluous. The text preceding it says that option values are coerced to the required type, and that implies converting an array to its member sequence, doesn't it?

[michaelhkay]

the function should accept either a sequence or an array

I thought we had dropped that, but it seems not. Thanks for pointing it out.

[GuntherRademacher]

Fixed by #1664.