From df8be391bbd5edcae8a8f607ea9b03ae509a910b Mon Sep 17 00:00:00 2001 From: Michael Kay Date: Thu, 19 Dec 2024 16:23:53 +0000 Subject: [PATCH] 1659-drop-obsolete-rule --- specifications/xpath-functions-40/src/xpath-functions.xml | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/specifications/xpath-functions-40/src/xpath-functions.xml b/specifications/xpath-functions-40/src/xpath-functions.xml index 1b09ce306..5714a1127 100644 --- a/specifications/xpath-functions-40/src/xpath-functions.xml +++ b/specifications/xpath-functions-40/src/xpath-functions.xml @@ -817,12 +817,7 @@ for transition to Proposed Recommendation.

'> for this error are defined in the specification of each function.

It is the responsibility of each function implementation to invoke this conversion; it does not happen automatically as a consequence of the function-calling rules.

 -

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 cases where the value of an option is itself a map, the specification of the particular function must indicate whether or not these rules apply recursively to the contents of that map.