XProc Editors Draft 2007-07-19: Section 3.2 Comments

I think this section needs to talk about the scope of pipeline type 
names in a pipeline library: say that each pipeline in a pipeline 
library must have a unique type, and talk about the scope of those 
pipeline names. A reference to another section that talks about this in 
detail would be sufficient.

The paragraph:

   The scope of option names is essentially the same as the scope of step
   names, with the following caveat: whereas step names must be unique,
   option names may be repeated. An option specified on a step shadows
   any specification that may already be in-scope.

is pretty confusing. Since option names can be repeated, does that mean 
it's OK to do:

   <p:group>
     <p:option name="foo" ... />
     <p:option name="foo" ... />
     ...
   </p:group>

The last sentence is about options within step invocations rather than 
options at the container step level, and I think it would be helpful to 
separate it into a different paragraph. At this level, can you have 
multiple options with the same name, as in:

   <p:load>
     <p:option name="href" ... />
     <p:option name="href" ... />
   </p:load>

(The same distinction might be useful with ports.)

Jeni
-- 
Jeni Tennison
http://www.jenitennison.com

Received on Monday, 23 July 2007 10:38:13 UTC