Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Mon, 29 Aug 2005 12:15:51 +0200
From: Ferdinand Soethe <ferdinand@apache.org>
Reply-To: Ferdinand Soethe <ferdinand@apache.org>
Message-ID: <1756232779.20050829121551@soethe.net>
To: dev@forrest.apache.org
Subject: Re: Forrest Tuesday (Was: Bug Days (Was Re: better use of Jira for
 Forrest))
In-Reply-To: <4311FDA3.5020202@apache.org>
References: <20050318082334.GA23935@igg.indexgeo.com.au>
 <200508182203.04267.diwaker@apache.org>
 <20050828053315.GA23150@igg.indexgeo.com.au>
 <200508281034.25439.diwaker@apache.org> <4311FDA3.5020202@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Ross Gardler wrote:

> The *implementation* of the move to XHTML2 would be eased considerably
> by refactoring our sitemaps to use the locationmap.

Why is that? In my limited understanding lm allows to specify the
location of a resource in more sophisticated ways, where is the
connection?

> Tim reports that the
> project locationmap mount doesn't work properly yet, but unless he tells
> us otherwise I think we can safely move forward with this refactoring.

Not sure this kind of lazy consensus is the right approach here. I
understand is that Tim has pointed out a problem with the lm
implementation. Should it not be up to us now to demo that this
problem has been solved (us of course including Tim :-) rather than
expecting Tim to object?

> I am +1 on the move to XHTML2 being a primary goal for Forrest Tuesday,
> but with the provision that w work in a top down approach. That is, we
> start by creating the stylesheets, templates etc. We should *not* work
> on the core sitemaps, instead we should focus on a single path through
> the sitemap and build it as an internal plugin. I'd suggest the path
> should be DocumentV1.3 as the input format.

... so that using this plugin Forrest will translate any documentv1.3
to xhtml2 and from there create html4 and pdf?

Can we also include direct support for the subset of xhtml2 that we
are gonna use?

--
Ferdinand Soethe