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

Re: Requirements Document Updated

From: Alessandro Vernet <avernet@orbeon.com>
Date: Thu, 9 Feb 2006 12:51:41 -0800
Message-ID: <4828ceec0602091251pfc8011eh3650669df5bac7b7@mail.gmail.com>
To: public-xml-processing-model-wg@w3.org

1) In the definition for Step (in Terminology), we say: "A step is a
specification of how a component is used in a pipeline that includes
inputs, outputs, and parameters". As the term "parameters" is not well
defined and I would prefer to talk here about "inputs and outputs"
only, "parameters" falling under the broad category of "inputs".

2) In the definition of "XML pipeline" we also use the term
"parameters". Here I assume it means "inputs and outputs". If this is
the case, I suggest we replace in this definition "parameters" by
"inputs and outputs".

3) In "4.6 Standard Names for Step Inventory", we say that "the XML
Pipeline Specification Document must have standard names for steps"
and then list some examples like XSLT or XQuery. I think that here we
meant "names for components" (instead of steps).

4) In "4.8 Validation of XML Pipeline Documents by a Schema", we say
that an "XML Pipeline Specification Document must be able to be
validated by both W3C XML Schema and RelaxNG". First, there is a
reference to the XML Processing Model Requirements document, but I
don't see this requirement there. Second, it is not clear to me what
the intent of this requirement is. Do we want to say that we'll create
a schema (even non-normative, like XSLT 2.0 does), or that the
language should be designed so it can be fully validated with XML
Schema (I hope not!), or something else?

5) Requirement "4.10 Allow Naming of Pipelines": there is no
corresponding use case, and before we can discuss this, I think this
should be clarified.


On 2/2/06, Alex Milowski <alex@milowski.org> wrote:
> I've updated the document from today's call:
>   * Removed detect bit from 4.2
>   * Added definition of streaming
>   * Restricted 4.6 to a standard inventory of names for specs
>   * Added an issue about fallback
>   * Added a requirement for a minimal set of components to be required
> I've also added the following:
>   * A table that maps requirements to use cases
>   * New use cases that support fallback and streaming
> --
> --Alex Milowski

Blog (XML, Web apps, Open Source):
Received on Thursday, 9 February 2006 20:51:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:39 UTC