markup validator short-term roadmap

Hi all,

I've been looking at what was keeping us from moving forward toward a  
new release of the markup validator, and eventually thought that  
although some are minor annoyances, none should be such obstacles  
that they stall our progress.

In particular:
- the fact that wmvs 0.8 depends on the cvs version of s:p:o is not  
extremely practical, but that can be documented, and the installation  
will remain feasible. So we can at least make an alpha/beta test of  
the new version. Bjoern, if you could list for us what you think is  
keeping you from release s:p:o 0.99, perhaps we could help?

- the lack of some "extras" such as the outline and parse tree, is  
something that I had been considering "unacceptable regression", but  
looking at some logs, it appears that the fraction of people using  
these options do not make them absolute necessities. Also,  
considering that we will keep them as "possible enhancement", we can  
get around to recoding them with the new architecture, or receive a  
patch to that effect, or keep in mind that it would be a good feature  
for when we eventually have a generic checker (such as what Jean-Gui  
and Damien are working on) - in any case, that's not a show stopper  
for the validator.


Given this, I propose to organize an alpha test of the HEAD version  
in the weeks to come. I'll be installing the latest s:p:o and opensp  
on the validator servers this week, and then we can perhaps use the  
wiki to build a changelog between 0.7.x and 0-8-alpha1 ?

Thoughts, objections?
-- 
olivier Thereaux - W3C - http://www.w3.org/People/olivier/
W3C Open Source Software: http://www.w3.org/Status

Received on Thursday, 8 June 2006 03:01:04 UTC