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

Requirements

From: Rui Lopes <rlopes@di.fc.ul.pt>
Date: Mon, 02 Jan 2006 13:02:01 +0000
Message-ID: <43B9243B.30401@di.fc.ul.pt>
To: XMLProc List <public-xml-processing-model-wg@w3.org>
>
>
>Here are some requirements to be discussed on the next meeting, based
>on the requirements gathered previously in the WG note.
>
>
>Rui
>
>
>-------
>
>Requirements for an XML Processing Model:
>-----------------------------------------
>
>- The model should define the interaction between processing stages
>   within a pipeline, especially when multiple inputs and outputs are
>   processed;
>
>- Mechanisms for pipeline composition must be provided, whether
>   dependency-based or sequence-based;
>
>- Different pipelines within a processing specification must have a
>   specific meaning:
>    . dependencies should be based on input/output specifications?
>    . all pipelines are independent from each other (thus able to be
>      executed in parallel)?
>
>- The model should allow pipelines to be explicitly named, enabling a
>   partial execution of a given specification.
>
>
>Requirements for an XML Processing Language:
>--------------------------------------------
>
>- The language must be conformant to the processing model;
>
>- The language must be as declarative as possible, providing the
>   smallest set of procedural elements possible (e.g., foreach,
>   if/switch, error/exception handling);
>
>- Given the same source documents and processing specification,
>   different XProc implementations must return the same results;
>
>- The language binding to initial processing sources should be as loose
>   as possible, enabling batch processing;
>
>- There should be only one standardized element for stage declaration
>   within a pipeline, lowering language specification maintenance costs;
>
>- Processing stage names should be standardized, with strict semantics
>   (i.e., declaring an XSLT task will run a conformant XSLT processor);
>
>- A set of core components must be implemented (e.g. XSLT, XInclude,
>   Schema Validation), otherwise conformant implementations will not
>   produce any practical result;
>
>- The language should allow composition of external pipelines,
>   lowering application maintenance costs.
>
>-- 
>Rui Lopes <rlopes@di.fc.ul.pt>                          Work: +351 21 750 05 32
>Junior Researcher                                       Fax:  +351 21 750 05 33
>quoted-printable
>Faculdade de Ci=C3=AAncias - Universidade de Lisboa
>HCIM/LaSIGE - Department of Informatics
>Campo Grande, Bloco C6 - Sala 6.3.29
>Lisboa, Portugal
--------------090206010106000908050900--
Received on Tuesday, 3 January 2006 13:18:17 GMT

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