Re: [check] Status and Progress

Olivier Thereaux <> wrote:

>>Going forward I'm thinking we'll call a public beta ASAP.

Ok. Since nobody is yelling "WAIT", I'll move ahead with that at some point
during the next 24-48 hours.

>>I'll advertize the hell out of it anywhere I can think of
>>(mailinglists, newsgroups, etc.) and hopefully we'll get all the
>>"Dude, you *suck*!" messages _before_ we update :80 with the new
>>version this time. :-)
>I wonder if it will benefit from an "official" voice (e.g calls for
>reviews sent with a W3 address) and if it needs any "coverage", i.e if
>we should ask the comm to talk about it. I'm tempted to think the
>answer to the former might be "yes", whereas comm coverage can wait
>for the "real update". I'm wishing to hear other opinions, though.

I don't want to involve Comms in this for the beta, but anything coming
from is going to catch more eyes then so if you want to
take on that bit it would be great. My initial thought of where to send an
announcement includes:


with specially adapted notes to:

The MathML list
The WAI ER IG list
Zeldman (since people keep quoting him at me)

In addition, I was thinking of dropping a personal note to the following
people and groups:

Todd Fahrner |
Eric Meyer   |- (All of whom I've talked Validator with off-list)
Tantek Çelik |
.no web design newsgroups
BBSW Web Authoring list

If anyone has more ideas then please do holler! The more of these places
(apart from the latter group) get a note from the better, but if
you're not a USENET kind of guy, I'm sure we could persuade Nick to post to
ciwah (right Nick?).

Below is a first cut of a release announcement:

-- cut here
 |                        Public Beta Test of The                      |
 |                     W3C MarkUp Validation Service                   |

After about a year of saying "Real Soon Now[tm]", a new version of the
W3C MarkUp Validation Service is now available for testing.


This is a public beta test of the new version before it is released in
production. This implies that the code is _not_ ready for use in a
production environment. If you have somehow managed to find a "Mission
Critical" use for the MarkUp Validator you are insane and should probably
be restrained to prevent doing harm to yourself. :-)

There is no fixed schedule for the final release of this new version, but
we sincerely hope to get it out the door before the end of the year; much
sooner if we can manage it. Depending on the amount and nature of the
feedback we recieve the release may be dubbed "Final Release" in a matter
of weeks!

We are looking for feedback on all aspects of the MarkUp Validator, but we
are in particular interested to hear from people who experience problem
with the new version that do not exist in the current stable release. Other
specific areas we are particularly interested in feedback on include:

    * Problems with the current stable release that are fixed in
      the new version.

    * The new design for the web interface and the website.

    * Any and all problems related to the Accessibility of the web
      interface and website[0].

    * The documentation (Yes, Virginia, there really _is_ documentation
      for the MarkUp Validator!).

    * Missing features[1] etc.

But don't let that hold you back! We are looking for any and all feedback
-- good or bad! -- for all aspects of the service. Don't hesitate to drop
us a note no matter how little the issue. In particular, don't assume
something is so obvious that we're surely aware of it! Send it in anyways.

C O N T A C T:

    The main contact point for feedback on the W3C MarkUp Validation
    Service is the publically archived mailinglist <>.
    You can subscribe to this list by sending a message to


    with the word "subscribe" in the Subject field. To view the archives of
    this list you can visit


    Several of the developers also frequent the IRC channel #validator
    on OPN (

W H A T ' S  N E W

    The majority of changes in this new version are either bug fixes or
    internal restructuring to facilitate future development. Significant
    changes include:

    * Valid Result Pages now show more human readable results and less
      technical detail. This behaviour may be changed if significant
      negative feedback surfaces (so don't forget to send us feedback!).

    * Character Encoding issues are more fully handled and the majority of
      the Character Encoding related code has been rewritten. This should
      mean better and more robust handling of Character Encodings --
      particularly for non-US/European Encodings -- but is also stricter
      with sloppy encoding declarations and malformed encoded documents
      (Windows-1252 users take note!).

    * Source Code is now always displayed if a page contains errors.

    * More error message now have explanations, and the explanations have
      been improved. We are still looking for contributions of more
      explanations and improvements of the existing explanations.

    * Many more Document Types are supported, and many DTDs have been
      updated to more recent versions.

    * An ecclectinc assortment of minor tweaks and changes that have
      accumulated over the past year; too numerous and finicky to be
      mentioned. :-)


    The W3C MarkUp Validator was created by Gerald Oskoboiny and is
    now maintained by members of the W3C QA Activity Team and external
    collaborators. The W3C Team Contacts for the W3C MarkUp Validator
    are Olivier Thereaux <> and Dominique Hazaël-Massieux
    <>. Much of the i18n code was written from scratch by
    Martin Dürst <>.

    Significant external contributions were made by many, including:

      * Aaron Swartz      * Jim Ley         * Nick Kew
      * Christian Smith   * Karl Dubost     * Olivier Thereaux
      * Dan Connolly      * Liam Quinn      * Sean Palmer
      * Hugo Haas         * Martin Dürst    * Ville Skyttä

    In addition, the developers would like to acknowledge the following
    people who have contrubuted suggestions, bug reports, and feeback:

    * Björn Hörhmann
    * Peter K. Sheerin

    As well as the many many good people on www-validator who have
    contributed of their time and experience to help improve the
    Validator. Many thanks to you all!

[0] - Please note that while we've made some advances towards making the
      MarkUp Validator Accessible, there are still likely to be many issues
      remaining and they probably will not be dealt with this time around.
      If you can volunteer any time towards helping us with this, please
      drop us a note to that effect. When we start the work -- in a future
      version -- we'll need help with the Accessibility aspects from the
      early development work and close cooperation with testers and
      collaborators with Accessibility experience.

[1] - Please note that the featureset for this release of the MarkUp
      Validator is largely frozen -- with a few key exceptions -- and
      any feedback on new features will go into the development effort
      for the next version (which will happen in paralell with
      maintenance releases).
-- cut here
Editor's note: in the last update,   we noted that Larry Wall would "vomment"
on existing RFCs. Some took that to be a cross between "vomit" and "comment."
We are unsure of whether it was a subconscious slip or a typographical error.
We are also unsure of whether or not to regret the error.      --

Received on Monday, 21 October 2002 16:04:07 UTC