RE: ISSUE-140 CPP — no conformance versions

What you've described below is a "profile" of some specification (HTML in this case).   A specific set of requirements based on one or more "standards" to define your specific goals and needs.

Now you have a choice...

Now you give that "profile" a formal name so that others can also refer to it and know that they are compatible with you.  And Mazal Tov - you've got yourself an interoperable "specification".  This is what has been going on in numerous industries for years now (consider GeoTIFF, PDF/X Plus,. etc), because it is required in order to do business with enterprises & governments.

You have to have a named "profile" - whether it's "HTM5" or "Benjy's HTML" or simply "Fred" (Fred, works for pretty much anything)...It enables the customer to specify EXACTLY what they want w/o any question AND do so in a way that makes them compatible with others who pick that same name.

So either we get to do the naming _OR_ we leave it up to others.  Personally, I'd think WE would want that control....

Leonard

-----Original Message-----
From: public-html-request@w3.org [mailto:public-html-request@w3.org] On Behalf Of Benjamin Hawkes-Lewis
Sent: Sunday, February 06, 2011 12:43 PM
To: julian.reschke@gmx.de
Cc: Anne van Kesteren; HTML WG
Subject: Re: ISSUE-140 CPP — no conformance versions

On Sun, Feb 6, 2011 at 1:32 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> It's essential, when in the real world you need to communicate with another
> party about that kind of HTML you're using. For instance, try to write a SoW
> for a project and say "whatever works in the latest version of browsers".

Specifying "whatever works in the latest version of browsers" or
"HTML5" are not the only options, and neither is especially valuable
in a statement of work.

Useful information is more detailed and takes forms such as:

    1) Use markup patterns described in documents L, M, N.
    2) Validate using tool X using options Q and R. Ignore errors A, B, C.
    3) Lint using tool Y. Ignore warnings G, H, I.
    4) Test end result in user agents T, R, V.

--
Benjamin Hawkes-Lewis

Received on Sunday, 6 February 2011 18:55:12 UTC