W3C home > Mailing lists > Public > public-qa-dev@w3.org > April 2005

[wmvs] Requirements for "Valid" Badges

From: Terje Bless <link@pobox.com>
Date: Tue, 12 Apr 2005 19:01:18 +0200
To: Olivier Thereaux <ot@w3.org>
cc: QA Dev <public-qa-dev@w3.org>
Message-ID: <r02010500-1038-7D5671BEAB7411D9A253000D9348908C@[193.157.66.142]>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Dear Olivier,

as the W3C Team Contact for the Markup Validation Service team I'm writing you
to inform you of the technical, practical, and functional requirements we have
for the “Valid” badges that are used on, and which make up part of the source
code for, the Markup Validation Service.

I'm sure these are not exhaustive, but they should make up a good first
approximation of our concerns in this regard.


1. Badges must exist for all Markup languages and related standards that
   the Validation Service supports.

2. Badges must exist in SVG, GIF, and (MSIE-compatible) PNG format.
   Further formats may be needed in the future.

3. The SVG version must be Valid, and Accessible to the extent possible.

4. The fonts used must be embeddable — including optimization for download
   time by removing unused glyphs from badge files — and not encumbered by
   any “Intelectual Property” restrictions (since they will be part of the
   Validator source code and published under an OSS License) beyond the
   normal Logo and Trademark guidelines.

5. Updated versions — both to support new standards, and to correct
   reported bugs in the existing versions — must be available in a suitably
   short timeframe. Given beta test periods are generally quite amply
   sufficient for new badges to be generated, it is not acceptable for
   updated badges to delay a new release version.

   In particular, the request for SVG format badges was first made in
   September of 2000. When no response was received, by July 2001, members
   of the validator team created their own SVG versions.

   Since July of 2001 the process of attaining the Comms Team's permission
   to use these badges has been “ongoing”.

   Taking under advisement the report from your participation in the W3C
   Comms Team's recent Teleconference — from which I gather the Comms Team
   has settled on a path to resolve this issue — I expect the advertized
   “refresh” will also include steps to avoid future requests taking almost
   5 years to resolve.

   Failing that, the Comms Team would have to provide us with templates —
   or “bless” templates produced by the Validator team — from which updated
   badges could be generated.


Kind Regards,
Terje Bless, WMVS contributor


- -- 
> ...publicity rights, moral rights, and rights against unfair competition...
Well, you've got me there.   I have no idea what any of those have to do with
SGML. Next you'll be claiming that running NSGMLS constitutes an unauthorized
public performance of SGML.                                  -- Richard Tobin

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.2.2

iQA/AwUBQlv+3aPyPrIkdfXsEQISggCfRG8V8ddPseklUQOsUMStXkwigj8AoPBJ
OqgqPP/uU4+jZUfoMqYXfbJz
=5YEi
-----END PGP SIGNATURE-----
Received on Tuesday, 12 April 2005 17:01:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 19 August 2010 18:12:45 GMT