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
As I commented here a bit off-topic, if a pipeline author uses p:with-input/@select, the input document’s content-type, serialization and maybe base-uri properties might not be preservable even if the step says it will preserve all document properties.
Consider this:
<p:identityname="text">
<p:with-inputport="source">
<p:inline><doc/></p:inline>
</p:with-input>
</p:identity>
<!-- → Text document -->
<p:identityname="parse">
<p:with-inputport="source"select="parse-xml-fragment(/)">
</p:identity>
<!-- → XML document -->
Likewise, p:identity can turn an XML document into a text document using an appropriate p:with-input/@select.
This is not limited to p:identity. So I don’t think we can say for any step that it will preserve all document properties under all circumstances.
Should we say something about it in the steps spec introduction, after the bullet list below “Some aspects of documents are generally unchanged by steps:”?
The text was updated successfully, but these errors were encountered:
As I commented here a bit off-topic, if a pipeline author uses
p:with-input/@select
, the input document’scontent-type
,serialization
and maybebase-uri
properties might not be preservable even if the step says it will preserve all document properties.Consider this:
Likewise,
p:identity
can turn an XML document into a text document using an appropriatep:with-input/@select
.This is not limited to
p:identity
. So I don’t think we can say for any step that it will preserve all document properties under all circumstances.Should we say something about it in the steps spec introduction, after the bullet list below “Some aspects of documents are generally unchanged by steps:”?
The text was updated successfully, but these errors were encountered: