Hi, 

I am forwarding yet another re-validation request we've received from
Cocoon.

Given the request from Xalan, we should think about designing generic
API for revalidation of some data structure in memory.

Thx,
-- 
Elena Litani / IBM Toronto

Torsten Curdt wrote:
> I'm a cocoon developer and I'm currently trying to improve cocoon's form
> handling. I'm trying to find a unified approach for validation of an
> abstract (or even just a small portion of a) DOM tree. So we can easily
> use different validation schemas (xsd,relaxng,schematron).
> I have a DOM structure in memory.
> We are building this DOM while going through a install-wizard-like
> webapp. So we usually start with an empty DOM add some nodes and want to
> validate those. Then we add some more nodes and want to validate only those
> added. I the end I want to validate the document again.
> 
> Now comes the tricky part: the result of the validation is supposed to be
> (1) not fail fast - but lenient (validate all - so we get all errors)
> (2) the validation result is a very detailed description of what is wrong. for
> content nodes e.g. the regexp that failed
> (3) the DOM might also be a bean - so we need an abstraction here, too. This
> should be keept in mind. But could be saved for later ;-)
> 
> Example:
> 
> first page:
>   *empty*
> 
> after first page:
> 
>   <doc>
> |      <user>
> |            <username>Torsten</username>
> |     </user>
>   </doc>
> 
> after second page:
> 
>   <doc>
>       <user>
>              <username>Torsten</username>
>       </user>
> |     <order>
> |            <item id="123"/>
> |     </order
>   </doc>
> 
> at the end:
> 
>   <doc>
> |     <user>
> |            <username>Torsten</username>
> |     </user>
> |     <order>
> |            <item id="123"/>
> |     </order
>   </doc>
> 
> | = validate
> 
> And I am wondering 
> 
> (1) if partial validation of the tree possible at all with the current 
>     Xerces API
> (2) if someone can give a little introduction (since I doubt the doc is
> already in place ;-) of the current PSVI API and related stuff :-)) *please*
> (3) have you guys thought about a more pluggable approach? since there are
> lot's of different validation techniques out there. Schematron, relaxng,...
> It would be great if someone could just drop that into xerces.
> 
> Regarding revalidation against RelaxNG, schematron
> I know it would be too much work to have all the different validation types in
> xerces (lot's of work!) but wouldn't it be useful to have an API so people or
> other projects can just plug-in their implementation?
> 
> cheers
> --
> Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to