microformats2-linting

(Difference between revisions)

Jump to: navigation, search
(-1 linting any <article>)
Current revision (14:57, 12 July 2015) (view source)
(Notes: response to tantek)
 
Line 15: Line 15:
* <code>&lt;article&gt;</code> in practice seems to serve no purpose in HTML5.
* <code>&lt;article&gt;</code> in practice seems to serve no purpose in HTML5.
** I've stopped using it for this reason. [[User:Tantek|Tantek]] 14:44, 12 July 2015 (UTC)
** I've stopped using it for this reason. [[User:Tantek|Tantek]] 14:44, 12 July 2015 (UTC)
 +
** I use it because it's the correct element for the job. There's a bit of a chicken and egg problem here: we ask for the new elements, WHATWG/W3C give them to us as blank slates to play with, then we complain that they don't do anything. And the semantics of an h-entry and an article match up pretty damn well. My view is that the point of a linter is to give people the hints to get better at writing not just microformats but at writing HTML too. You can ignore its advice if you choose though. —[[User:TomMorris|Tom Morris]] 14:57, 12 July 2015 (UTC)

Current revision

This page is to work out possible rules for a future microformats2 linter/validator.

The job of a linter or validator is to help the user correctly implement microformats2 on their site by making helpful (if somewhat pedantic) comments about the markup.

Possible linting rules

  1. If a document has an h-feed class, it shouldn't have any h-entry elements that are not children of the h-feed.
  2. A non-nested h-entry should be on an article.
    • -1 Tantek 14:44, 12 July 2015 (UTC) see below
  3. If the outer h-entry is an article element, arguably nested h-entrys should also be articles. This is explicitly recommended by §4.3.2 of HTML5.
    • -1 article tag is unnecessary extra markup / and or constraint for the semantics of h-entry. Tantek 14:44, 12 July 2015 (UTC)
  4. dt-created <= dt-published <= dt-updated.

Notes

microformats2-linting was last modified: Sunday, July 12th, 2015

Views