AW: Use Case "Create Document"

 
| Re: Use Case "Create Document" (...)
|
|/ Daniel.Gabi@bk.admin.ch was heard to say:
|| I propose to add the use case "create a document from a schema". The 
|| idea is to get an minimal instance that is populated with the 
|| required, fixed and defaulted data structures within a chosen root
element.
|
| While that's no doubt useful functionality, and might even be a
candidate 
| for a component, it doesn't seem like pipeline functionality exactly.
| Can you explain why you would want a pipeline to do this, and 
| what else you might want the pipeline to do?
|
|                                      Be seeing you,
|                                        norm
|

Depending on the mechanisms for conditional processing of inputs (s.
4.6) the pipeline "create document" and sub-pipelines might flow as
follows:

1. Receive a RelaxNG schema or W3C XML Schema together with an optional
parameter(-document) indicating a root element.
2. If the schema itself is not valid, abort.
3. If the paramater is not set, call a sub-pipeline to get all possible
root elements and call a sub-pipeline to get the user-selection of a
root element.
4. If the selected root element is possible according to the schema,
apply an XSLT transformation or execute an XQuery on the schema to get a
valid "empty" instance corresponding to the selected schema.

But at the moment I'm not able to tell you if there should or could be
such a pipeline functionality or why not.

daniel