W3C home > Mailing lists > Public > spec-prod@w3.org > July to September 2012

validation problems with respec output

From: Michael[tm] Smith <mike@w3.org>
Date: Thu, 5 Jul 2012 20:10:00 +0900
To: Robin Berjon <robin@berjon.com>
Cc: spec-prod@w3.org
Message-ID: <20120705110959.GA17855@sideshowbarker>

There are a couple problems with current respec that cause respec-generated
specs to not conform to requirements in the HTML5 spec.

1. <acronym> elements in parts of the generated boilerplate. For better or
worse <acronym> is not a valid element per the HTML5 spec. So respec should
instead be using the <abbr> element for those cases ( if the goal is to have
output conform to the HTML5 spec).

2. rel="biblioentry" in bibliography links. The HTML5 spec requires all rel
values to either be defined in the HTML5 spec itself or to be registered as
a valid values at http://microformats.org/wiki/existing-rel-values

"biblioentry" is listed there, but in the "dropped" section
http://microformats.org/wiki/existing-rel-values#dropped which says "In
general, you should not use any dropped values." And the reason biblioentry
is listed in that section is because it was once listed in a pre-HTML4
non-normative "Proposed Relationship Values" draft but never actually ended
up being included in the HTML4 specification. So there is actually no
normative specification for biblioentry anywhere.

If you prefer to keep the rel=biblioentry output (because there are tools
you know of and are targeted that actually consume that rel=biblioentry
data and do something with it) then I propose adding a user option to
suppress it, and I'm happy to contribute a patch to do that (though lacking
any normative spec for what it's supposed to mean, I'd really prefer to
just see it dropped).


Michael[tm] Smith http://people.w3.org/mike
Received on Thursday, 5 July 2012 11:10:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:19 UTC