Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 65789 invoked by uid 500); 13 Aug 2002 08:08:53 -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 65777 invoked from network); 13 Aug 2002 08:08:52 -0000 Subject: Re: cocoon is non-validating, any ideas why? From: David Crossley To: cocoon-users@xml.apache.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 13 Aug 2002 18:09:02 +1000 Message-Id: <1029226143.1406.399.camel@ighp> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Please do not give up, Ian. Cocoon can certainly do validation as an XML framework now using DTDs. Perhaps later using other schema (Relax NG anyone?). Vadim was just saying that it is not a "Concern" of Cocoon, but that of the parser. We put a lot of work in six (?) months ago to ensure that Cocoon could do validation. In fact, we had it working nicely during build docs. However, then Bug 6200 was uncovered. and we had to turn it off by default in cocoon.xconf Please help to get it available again. Can you add any insight to the Bugzilla description? http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6200 This is definitely a capability that i, for one, want to see in my XML Framework. Ian, you seem to be trying to trick the parser by supplying malformed SYSTEM identifiers and fake DTDs. That will never work. There is one way for small documents - add an internal DTD subset. See for example cocoon.roles --David --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: