W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > August 2007

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

From: Jeni Tennison <jeni@jenitennison.com>
Date: Thu, 02 Aug 2007 19:58:14 +0100
Message-ID: <46B22946.7020605@jenitennison.com>
To: public-xml-processing-model-wg@w3.org

Norman Walsh wrote:
> / Jeni Tennison <jeni@jenitennison.com> was heard to say:
> | 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.
> 
> Hmmm. I changed the first paragraph of 3.2 to read:
> 
>   The scope of the names of step types is the pipeline. Each pipeline
>   processor has some number of built in step types and may declare
>   (directly, or by reference to an external library) additional step
>   types. All the step types in a pipeline must have unique names: it
>   is a static error (err:XS0036) if two declarations for the same step
>   type name appear in the same scope.
> 
> I wonder if that helps.

Not really :) It focuses on the step types in a (single) pipeline rather 
than the step types in a pipeline *library*. Perhaps we can say (not 
necessarily in this section) that a pipeline document with a 
<p:pipeline> document element is equivalent to a <p:pipeline-library> 
with all <p:import>s and <p:declare-step>s (and so on) moved into the 
<p:pipeline-library>, and otherwise containing that (single) 
<p:pipeline>. Then every pipeline document can be considered a pipeline 
library, and we can say:

   The scope of the names of step types is the pipeline library. Each
   pipeline processor has some number of built in step types and a
   pipeline library may declare (directly, or by reference to an external
   library) additional step types using <p:declare-step> or by defining
   pipelines. All the step types in a pipeline library must have unique
   names: it is a static error (err:XS0036) if two declarations for the
   same step type name appear in the same scope.


The rest of the changes seem fine.

Cheers,

Jeni
-- 
Jeni Tennison
http://www.jenitennison.com
Received on Thursday, 2 August 2007 18:58:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:53 GMT