[dsdl-discuss] Re: Interoperability framework: getting started again

Eric

Re

 <framework>
  <rule>
   <instance>
    <split split="document('split.xxx')"/>
   </instance>
   <assert>
    <isValid schema="document('schema1.rng')" instance="instance[1]"/>
    <isValid schema="document('schema1.rng')" instance="instance[2]"/>
   </assert>
  </rule>
 </framework>

and

>Alternatively, transformation results can be stored in variables:

 <framework>
  <variable name="mySchema">
    <transform instance="document('master.rng')"
transformation="document('getstage.xsl')">
     <with-param name="stageName" select="'post-floob'"/>
    </transform>
  </variable>
  <rule>
   <assert>
    <isValid schema="$mySchema"/>
   </assert>
  </rule>
 </framework>

>These are just some few initial examples, but I'd like to get your
feelings at this stage!

My initial feeling is that you need to be careful about identification of
variables, assertions, their inputs and outputs. It is one thing to allow
sequences where the output of one process is passed on to the next process
*at the same level or defined as an ancestor*. It is another thing to allow
arbitrary creation of output subsets and then reapply them, particularly if
they are to be reapplied at multiple places, as the first example seems to
imply.

Some specific questions. In the split example, where do instance[1] and
instance[2] come from? How to they get named? Which tree are they counted
in, and how is that tree identified? (There is only one instance element in
this framework, so instance[2] is a mystery to me!)

What happens if the contents of a variable is to be used as the input for a
subsequent transformation? Can it be written back to a variable with the
same name? If so, what controls which version an assertion works with? Is it
always to be the last version of the variable defined before the rule is
invoked? If so can I have <variable>...<rule>...<variable>...<rule>
sequences?

Martin Bryan

--
DSDL members discussion list
To unsubscribe, please send a message with the
command  "unsubscribe" to dsdl-discuss-request@dsdl.org
(mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)