cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Jelliffe" <>
Subject Re: [Schematron-love-in] Re: [Announcement] Fast Schematron Validation Here !
Date Sat, 30 Mar 2002 03:33:28 GMT
From: "Ivelin Ivanov" <>
> I mean browser, client. Different browsers (PC, PDA, cell-phone, etc.) may
> support different human interfaces and therefore the document may be split
> into different pieces which are gathered and put together at the end.
> The validation of the pieces at each stage is device/client dependent.
> Is the question more clear?

Yes, certainly you could use Schematron <phase>s to validate 
device-dependent constraints. 

<Phase>s reconstruct the conditional section features of XML DTDs,
("INCLUDE/IGNORE marked sections") which allow you to customize 
a DTD to get variants.  XML Schemas and RELAX do not have any equivalent.

The kinds of uses I imagine for phases include
  * versions (e.g. parallel variants)
  * pipe-line processing (e.g. serial variants)
  * variant processing (e.g. device-dependencies and fan-outs)
  * partial processing (e.g. documents under construction)
  * state-dependent processing (e.g. where the results of one
       phase are used by some proprietary system to switch to
       a different phase for further validation)

Critics of phases bleat that one can do the same thing with
different schemas, but the point is that with Schematron
<phase>s they become first-class objects capable of being
manipulated rather than proprietory handwaving :-)

In Topologi's freebie Schematron Validator (and in our
forthcoming Collaborative Markup Editor) we just make
a popup menu for the user to select the particular phase
to run when validating. Very straight-forward to use.

All in all, I think phases are a useful mechanism which
are trivial to implement and write, so they fit into
Schematron's `low-hanging fruit' approach well. 

Rick Jelliffe

To unsubscribe, e-mail:
For additional commands, email:

View raw message