cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <vadim.gritse...@verizon.net>
Subject Re: Relax NG validation for Cocoon
Date Thu, 15 Aug 2002 19:30:00 GMT
Ian Atkin wrote:

> it was forrest that woke me up to relaxng, but i'm up to a number of 
> things atm - this wasn't top of the list...
>
> i'm completely lost where cocoon ends and forrest starts, i'd like to 
> see validation first and worry about project boundaries second imho
>
> as for cocoon components (brainstorm):-


:)


> - does validation ocur at the parser level or the sitemap level or both?


Parser only. BTW, current 2.0.4-dev can show '/' page ("welcome") with 
treeprocessor and validation mode turned on. The main issue is XSLT 
stylesheets: writing DTDs for them is PITA.


> a quick win could be:-
> - use the XNIConfigurableFileGenerator from forrest
> - add Andy Clark's JingConfiguration and Jing ( 
> http://www.apache.org/~andyc/neko/doc/index.html )
> - configure in sitemap:-
>
>  <map:match pattern="[pattern]">
>    <map:generate src="[filename]" type="xni">
>       <map:parameter name="config-class" 
> value="org.cyberneko.relaxng.JingConfiguration" />
>       <map:parameter name="grammar" value="[grammar-filename]" />
>    </map:generate>
>       ....
>  </map:match>
>
> would require some hacking, but i think this generator needs a 
> clean-up anyway 


I don't like this idea.


> but then again, this would only work at start of pipeline...
>
> a win all round could be:-
>
> "validator" components, with variants of "doctype|schema|relaxng" 
> (would xpath be handy as well?)


This makes more sence, and may be used in more scenarios.

Vadim


> - definitions passed in through sitemap could override those in files 
> (spec says these are only hints)
> - errors cause redirection to error page or logging or whatever is 
> configured
> - i could see XNI being the saviour here, we could provide 
> doctype/schema from xerces and relax from neko + jing, also allows 
> anyone else to define their own validation components if they need them
> - issues are reliance on xerces and pre-sitemap validation (perhaps 
> multiple parser configs in cocoon.xconf? but how does code choose 
> which to use?)
> - don't know enough technicalities about mid-pipeline components
>
> what do you think?
>
> ian
>
.....




---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message