search

xproc / 1.0-specification

The 1.0 XProc specification and now abandoned drafts of a 2.0 XML specification
12 stars 6 forks source link

consider expand-text on p:declare-step #167

Closed xquery closed 9 years ago

xquery commented 9 years ago

In xslt, you can define expand-text at top level xsl:stylesheet and then you can selectively override behavior; wondering if we need to consider something similar with p:declare-step.

And it follows that we would need to define how overrides of expand-text works.

ndw commented 9 years ago

Probably needs to be allowed on any compound step.

ndw commented 9 years ago

Also: make explicit that if unspecified the value of expand-text is false.

ndw commented 9 years ago

The XSLT definition of expand-text doesn't require a default, it's worded as "above you"

ndw commented 9 years ago

From 10 June f2f: the context node is the default readable port for the step in which the p:inline occurs. AVTs are only on "shortcut" option values.

ndw commented 9 years ago

The spec needs to specify which variable bindings are in scope.

ndw commented 9 years ago

In an effort to avoid the question of having to enable TVTs, let's get rid of expand-text and just say that curly braces are TVTs in p:inline; if you don't like that, double them up.

ndw commented 9 years ago

Make sure the spec specifies the context node and more fully how expansion is performed (atomization, etc.)

ndw commented 9 years ago

New thinking: expand-text is true by default and can only occur on p:inline TVTs are not atomized, they copy content.