New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Step "p:parameters" needs some clarifications or should be removed #30

xml-project opened this Issue Dec 8, 2018 · 2 comments


None yet
2 participants
Copy link

xml-project commented Dec 8, 2018

p:parameters is defined with the following signature:

<p:declare-step type="p:parameters">
     <p:output port="result" content-types="application/xml"/>
     <p:option name="parameters" as="map(xs:QName,item()*)?"/>     

The description only says, that the value associated with a key in the map is represented as attribute value, but it does not say, what should happen, if:

  1. The map-value is a sequence of more than one element,

  2. The map-value is a node, and

  3. The map-value is an array, a map or a function.

All in all I am not sure we really need this step (except may be for legacy reasons), because p:cast-content-type can be used to convert maps into xml-documents using the specifications of `fn:json-to-xml()'.


This comment has been minimized.

Copy link
Contributor Author

xml-project commented Dec 13, 2018

@gimsieke and me talked about this on Dec. 13th call and we came to the conclusion, that it is better to cover this conversion with p:cast-content-type. We might use option $parameters to mark that we want a c:param-set representation of the map and not the XPath-representation. See also the issue on p:make-map() in the specification repo.


This comment has been minimized.

Copy link

ndw commented Feb 7, 2019

In February 2019, we decided to remove this step.

@ndw ndw closed this Feb 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment