Re: Proposed component list

On 1/24/07, Norman Walsh <Norman.Walsh@sun.com> wrote:
>
> In the interest of making progress on the list of components, I
> propose that we adopt the following core components for V1:
>
> xinclude - performs XInclude processing
> xslt     - performs XSLT 1.0
> xslt2    - performs XSLT 2.0
> validate - performs validation (XSD, RNG, Schematron, etc.)
> load     - read an XML document from a URI
> save     - serialize a document to a URI (supports XSLT 2.0 serialization
> params)
> identity - copies source to target
> httprequest - constructs a URI, performs the specified operation (using
> source as
>               the body if appropriate), returns the result as target
> aggregate - accepts an arbitrary number of input documents, produces a
> sequence of them
> subsequence - selects a subsequence from a sequence of documents
> wrap      - wraps elements
> insert    - inserts attributes/subtrees
> delete    - deletes attributes/subtrees
> rename    - renames attributes/elements
> ns-rename - rename namespaces
> label     - add unique xml:id attributes to all elements
> xproc     - run a pipeline



>From this list we are missing the 'serialize', 'parse', and 'set-attributes'
components that
we have in our current draft.

We have use cases for 'serialize' and 'parse' for handling RSS feeds.

The 'set-attributes' component is a necessary one that goes along with the
other
micro-operations components.


-- 
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."

Bertrand Russell in a footnote of Principles of Mathematics