Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Upayavira" <uv@upaya.co.uk>
To: cocoon-dev@xml.apache.org
Date: Wed, 04 Jun 2003 11:20:52 +0100
MIME-Version: 1.0
Subject: Re: ValidatingTransformer (WAS RE: TidySerializer)
Message-ID: <3EDDD614.6968.DAA3B24@localhost>
Priority: normal
In-reply-to: <000701c32a1f$7e82f410$d9784fcb@insurgentes.local>
References: <3EDD172C.1010900@gmx.de>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

On 4 Jun 2003 at 10:28, Conal Tuohy wrote:

> Joerg Heinicke wrote:
> 
> > Ok, reason accepted :) But what about an extra validating
> > transformer as
> > last pipeline step? Seems to make more sense IMO.
> 
> YES! This could be VERY useful: a transfomer that could validate the
> output of some pipeline stage against a DTD or other schema could be a
> great help for debugging. You wouldn't have to download the file and
> validate it with an external tool. It might even have a role in
> production systems for validating input from forms, web services etc?
> 
> <map:transform type="dtd-validator">
>  <map:parameter name="dtd" value="dtd/stage-1.dtd"/>
> </map:transform>
> 
> 
And then you add that transformer into a view, so you can access 
page.html?cocoon-view=validate 
to find out whether the page validates. That'd be neat.

Upayavira