Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 95638 invoked by uid 500); 21 Mar 2001 03:13:40 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 95426 invoked from network); 21 Mar 2001 03:13:26 -0000 Date: Wed, 21 Mar 2001 14:15:46 +1100 From: Jeff Turner To: cocoon-users@xml.apache.org Cc: peter@clickdocs.com.au Subject: Re: Schema-validated XSP? (was: Re: C1 useless?) Message-ID: <20010321141541.E32560@socialchange.net.au> Mail-Followup-To: cocoon-users@xml.apache.org, peter@clickdocs.com.au References: <20010321114906.B31578@socialchange.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: ; from balld@webslingerZ.com on Tue, Mar 20, 2001 at 08:42:42PM -0500 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Tue, Mar 20, 2001 at 08:42:42PM -0500, Donald Ball wrote: > On Wed, 21 Mar 2001, Jeff Turner wrote: > > > Raises the question: why not take advantage of the XSP's XML syntax > > and do schema validation at each point in an XSP's transition to Java > > code? Eg, after each taglib is applied, validation could be done > > against that taglib's schema. > > i'm not aware that there _is_ a schema validator package that conforms to > the latest (final?) version of the schema spec. I did a search a week ago, and found nothing except Henry Thompson's code. Anyway, I doubt XML Schemas will ever be a huge success (unless w3c manages to tie other specs to it). So why not look elsewhere.. in particular, James Clark's TREX (http://www.thaiopensource.com/trex/) seems very simple and intuitive, cunningly sidesteps data typing (which Cocoon wouldn't use), and has a 150k Java implementation. --Jeff > - donald --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: