- From: Philip Taylor <P.Taylor@Rhul.Ac.Uk>
- Date: Sat, 27 Jun 2020 10:28:16 +0100
- To: Steve Faulkner <faulkner.steve@gmail.com>, Wayne Campbell <asa.rand@gmail.com>
- Cc: "www-validator@w3.org" <www-validator@w3.org>
- Message-ID: <1aa24810-80bd-90e1-c9db-cf46231a1601@Rhul.Ac.Uk>
Steve Faulkner wrote: Hi Wayne, this may help: Will there be a valid HTML5 icon? No, there won’t be a Valid HTML icon any time soon and likely not ever. The reason is basically that “This is valid” icons/badges promote the idea that there’s significant value in making public claims of pass/fail document-conformance requirements in standards. But the HTML5 checker is by design not intended to encourage anybody to use it as a means to make public assertions of simple pass/fail conformance of any documents to any particular specifications; it’s intended solely as a checker — for people to use to catch unintended mistakes in documents and fix them — not as a pass/fail certification mechanism. There won’t be any proper Valid HTML5 icon forthcoming, so if you’d like to use one in your content, you’ll probably need to create one on your own. source: http://html5doctor.com/html5-check-it-before-you-wreck-it-with-miketm-smith/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fhtml5doctor.com%2Fhtml5-check-it-before-you-wreck-it-with-miketm-smith%2F&data=02%7C01%7CP.Taylor%40Rhul.Ac.Uk%7C678c315e9eb045e9136708d81a787749%7C2efd699a19224e69b601108008d28a2e%7C0%7C0%7C637288452006108501&sdata=dnHsuJUmiUooMZM6TVK4pW5QF8N%2FSVq55o%2FkLQe8NPI%3D&reserved=0> -- Regards SteveF I realise that those are not your words, Steve, but rather the words of Michael Smith, but I nonetheless wish to registered my objection to the sentiment(s) expressed therein. Where the author writes : "“This is valid” icons/badges promote the idea that there’s significant value in making public claims of pass/fail document-conformance requirements in standards", I completely disagree. “This is valid” icons/badges promote the idea that there is significant value in ensuring that documents conform to standards", and that is surely a statement with which no-one, I believe, would seek to disagree. The real problem lies in the fact that, with the advent of HTML 5, one can no longer ensure that one's (HTML 5) documents do conform to a given standard, since the whole concept of a "standard" in its traditional sense has been abolished and replaced by the insanity of the so-called "living standard" — something so evanescent that a document which might putatively claim to conform today might equally well fail to conform tomorrow. And of course this is reflected in the "HTML 5 Checker" — no longer a validator, because there is no longer anything against which to validate. Even the DOCTYPE directive, which until the advent of HTML 5 uniquely and unambiguously specified the variant of HTML to which the document purported to conform, has been abolished and replaced with the totally meaningless <!DOCTYPE html> which basically says "What follows is HTML, but which HTML is totally undefined". Philip Taylor This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certain circumstances, it may also be subject to legal privilege. Any unauthorised use, disclosure, or copying is not permitted. If you have received this email in error, please notify us and immediately and permanently delete it. Any views or opinions expressed in personal emails are solely those of the author and do not necessarily represent those of Royal Holloway, University of London. It is your responsibility to ensure that this email and any attachments are virus free.
Received on Saturday, 27 June 2020 09:28:36 UTC