forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams" <william...@gmail.com>
Subject Re: XHTML2 as forrest internal
Date Thu, 07 Aug 2008 11:10:17 GMT
On Wed, Aug 6, 2008 at 10:07 PM, David Crossley <crossley@apache.org> wrote:
> Ross Gardler wrote:
>> Carlos Tejo Alonso wrote:
>>
>> >>For a very long time we have intending to move to a subset of XHTML
>> >>2. But planning and doing are two different things. We need someone
>> >>with a suitably strong need to solve the problems posed by XDoc to
>> >> actually do it.
>> >
>> >Maybe, we should start to think to do it. Could somebody show the
>> >steps to move from xdoc to xhtml? I will try to do my bit.
>>
>> If it were that simple we would have done it by now ;-)
>>
>> There have been a number of false starts on this. My own effort was
>> aborted because a significant number of people in the community
>> disagreed with my approach.
>
> Wow. That is not my recollection. I thought that we had a
> little try, confirmed that it would take a co-ordinated
> approach, and left it for another day. I am talking about
> the re-working of all sitemaps and stylesheets (including
> plugins) to deal with XHTML2 internally, leaving everything
> else (e.g. cocoon) as it already is.
>
> Are you talking about something else, or do you recall
> it differently?

<blush> I reckon he's mostly referring to me:(

>> Gav made a start on an XHTML2 plugin (in whiteboard) but that also stalled.
>
> IIRC, the initial "internal.xhtml2" and "input.xdoc" were
> the result of Ross, Tim, and others around some of our
> Friday IRC sessions. I thought that was a fantastic step forward.
>
> I thought that it was just waiting for some group of people
> to get itchy again.

The details are forgotten with time, but I believe the sticking point
was an issue of "scope" of what it means to transition.  There were
two pieces of work to be done:
o) Data format - schema, updating input plugins, create xdoc->xhtml2
plugin, etc.
o) Pipeline refining - update pipelines to take advantage of xhtml2 + views

IIRC, I wanted them to be addressed separately to allow baby steps.
Ross preferred more holistic approach.  Part of my motivation at the
time was that views were still very much a moving target.  In the end,
no substantive steps were taken and I probably gave way too much merit
to how much any given approach really matters in the grand scheme.
Perhaps the only good news is that in the meantime the dispatcher has
matured, making the timing ripe for someone to re-engage.

If my memory has served me wrong, I apologize in advance, it's
definitely not my intent to be a revisionist historian:)

--tim

Mime
View raw message