Re: General or Specific Pipeline Vocabulary?

Alex Milowski wrote:

 > ...which comes back to a *requirement* of extensibility.  If I were to
 > refine that requirement, I'd want to allow embedding of custom
 > vocabularies for pipeline steps.

A quick note in passing: using a generic vocabulary has some benefits,
like the fact that you can more easily validate the vocabulary, and
also that tools that produce the vocabulary are more easily written.

This does not preclude:

1. Embedding XML infosets in pipeline step inputs so as to avoid
    creating too many external documents.

2. Allowing the schema for the pipeline language to be open and accept
    foreign, user- or implementation-defined elements.

-Erik