You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example @ndw provided in his mail to me raises another point with @select on p:with-input etc.:
Suppose I have a step which accepts say "text/plain" and I have an XML document containing a text node as child of a "section" element. Can I use <p:with-input select="//section/text">
with the XML document as default readable port or context node (if you prefer)?
The problem is at which point we will say, that the document to arrive on the text step does not match the expected content type "text/plain". If we do it before the evaluation @select an error has to be raised because there its "application/xml". If we consider the result of @select (as we do to assess whether its a sequence or not), no error should be raised.
I think you can make up the same kind of example for any XDM defined type as value of @select.
I hope, I made my point clear. If not, please tell me so and I try to provide an elaborated example.
The text was updated successfully, but these errors were encountered:
I think, practically, the input to the step has to be considered the result of evaulating the @select expression. We may need to say what conversions are allowed/required/standardized.
Can we close this or do we have to add some prose to the specs explicitly saying, that checking for the right content type has to be done after the "select" phrase is applied to the incoming document?
The example @ndw provided in his mail to me raises another point with @select on p:with-input etc.:
Suppose I have a step which accepts say "text/plain" and I have an XML document containing a text node as child of a "section" element. Can I use
<p:with-input select="//section/text">
with the XML document as default readable port or context node (if you prefer)?
The problem is at which point we will say, that the document to arrive on the text step does not match the expected content type "text/plain". If we do it before the evaluation @select an error has to be raised because there its "application/xml". If we consider the result of @select (as we do to assess whether its a sequence or not), no error should be raised.
I think you can make up the same kind of example for any XDM defined type as value of @select.
I hope, I made my point clear. If not, please tell me so and I try to provide an elaborated example.
The text was updated successfully, but these errors were encountered: