Return-Path: <cstrong@arielpartners.com>
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list forrest-dev@xml.apache.org
Delivered-To: moderator for forrest-dev@xml.apache.org
Received: (qmail 93027 invoked from network); 3 Jun 2002 05:04:12 -0000
Received: from arielpartners.com (65.105.97.36)
  by daedalus.apache.org with SMTP; 3 Jun 2002 05:04:12 -0000
Received: (qmail 8130 invoked from network); 3 Jun 2002 04:51:28 -0000
Received: from unknown (HELO arielpartners.com) (65.105.97.38)
  by 0 with SMTP; 3 Jun 2002 04:51:28 -0000
Message-ID: <3CFAF8D5.1050202@arielpartners.com>
Date: Mon, 03 Jun 2002 01:04:21 -0400
From: Craeg K Strong <cstrong@arielpartners.com>
Organization: Ariel Partners LLC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Steven Noels <stevenn@outerthought.org>
CC: forrest-dev@xml.apache.org
Subject: Re: adding catalog support to the XMLValidate Ant task
References: <OKEDLKGMIPDOCJHOEDEFOEOBDLAA.stevenn@outerthought.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hello:

Yes.  My intentions are indeed to add support for external OASIS catalogs
to Ant, both for <xslt> (aka <style>) and <xmlvalidate>.

It was alot of work and lots of changes, so I chopped the original
patch I submitted to ant-dev into two pieces.

The first piece (which _has_ been committed and is in 1.5Beta2)
updated the docs to point at the OASIS standard, added mucho tests,
and severely refactored the code so that adding in support for
OASIS catalogs will be a snap!

Now that this is in there, I will prepare a patch for the remainder
(ie 2 of 2) sometime in the next week.

The problem is that because we are in the "final beta" stage of 1.5
(to be released July 1) ordinarily ONLY bug fixes would be accepted.

Support for external OASIS catalogs will probably be viewed as
an enhancement, not a bug fix.  (heh, not by me :-)

However, if enough people from enough other projects would make
their wishes known, perhaps we could persuade the ant-dev committers
to let this enhancement into 1.5?

I personally think it is worth a try, b/c otherwise it gets committed
in the 1.6alpha which means that until 1.6 is released (god knows when)
you have to either use a daily build or download from CVS and build
your own.  yuk.

I already have the code ready; it is just a matter of applying it against
the latest CVS, testing the heck out of it, making patches, and submitting
them.

If you like, I will CC you (and forrest-dev?) on the actual patch submission
email when I make it.  That way you can reference the URL from
mail-archives in any correspondence...

Regards,

--Craeg

Steven Noels wrote:
>>From: Bruno Dumon [mailto:bruno@outerthought.org]
>>To: forrest-dev@xml.apache.org
>>Subject: Re: adding catalog support to the XMLValidate Ant task
> 
> 
>>On Sun, 2002-06-02 at 11:31, Steven Noels wrote:
>>
>>>Hi all,
>>>
>>>>From reading the documentation of the XMLValidate task
>>>
>>
>>(http://jakarta.apache.org/ant/manual/OptionalTasks/xmlvalidate.html),
>>
>>>there seems to be support for entity catalogs - which is
>>
>>nice. I've been
>>
>>>trying however to have this target pointing to our catalog, and it
>>>appears to me that Ant wants to have its own catalog
>>
>>syntax, inside the
>>
>>>build file itself. Nicola, Stefan, is it possible to have this task
>>>refer to an externally defined entity catalog file
>>
>>following the OASIS
>>
>>>conventions?
>>>
>>
>>There recently was a thread about this on xml-commons:
>>http://marc.theaimsgroup.com/?t=102071790600001&r=1&w=2
>>
>>Apperently, someone's looking to integrate the resolver, but it isn't
>>there yet.
> 
> 
> Thanks, Bruno ;-)
> 
> Craeg, any progress yet? Having 'real' catalog support in Ant would be
> very helpful for Forrest (http://xml.apache.org/forrest).
> 
> </Steven>
>