Support shorthand syntax in `p:pipe`

[JDziurlaj]

I was converting a bunch of p:output statements to p:pipe equivalents in order to iterate over the documents in a p:for-each statement. p:output supports the shorthand port@step using the @pipe attribute, while p:pipe does not. E.g. <p:output port="oscal-full-profile" pipe="result@oscal-full-profile" /> vs. <p:pipe step="oscal-full-profile" port="result" />.

My suggestion is to allow CDATA in the p:pipe element such that the shorthand can be used, e.g. <p:pipe>oscal-full-profile@result</p:pipe>

[ndw]

I’d be more inclined to allow @pipe on p:pipe, but what’s the context where you find p:pipe necessary?

[JDziurlaj]

The use case is gathering a set of documents and validating them against the schema.

<p:for-each>
	<p:with-input>
		<p:pipe step="oscal-full-profile" port="result"/>
		<p:pipe step="legacy-to-oscal" port="result"/>
		<p:pipe step="resolve-profile" port="resolved-profile"/>
		<p:pipe step="oscal-mapping" port="result"/>
	</p:with-input>
	<p:validate-with-xml-schema message="{$prefix} Validating {document-uri(.)} with XML Schema" report-format="xvrl" assert-valid="false">
		<p:with-input port="schema" href="http://csrc.nist.gov/ns/oscal/1.0"/>
	</p:validate-with-xml-schema>
</p:for-each>

[ndw]

<p:for-each>
  <p:with-input pipe="result@oscal-full-profile result@legacy-to-oscal
                      resolved-profile@resolve-profile result@oscal-mapping"/>
  ...
</p:for-each>

?

(I'm not opposed to providing it on p:pipe in principle, but I don't think it should be necessary.)

[JDziurlaj]

That's it! I'm happy to close if the feature isn't needed.