[wp-trac] [WordPress Trac] #17632: HTML 5 Validation issues (theme independent)

[WordPress Trac]

#17632: HTML 5 Validation issues (theme independent)
--------------------------+------------------------------
 Reporter:  amirhabibi    |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  3.1.3
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |
--------------------------+------------------------------

Comment (by pbiron):

 [http://core.trac.wordpress.org/ticket/17632#comment:16 @Maventus]: I
 replied [1] to your questions in that support thread, before I saw your
 note here.  You've probably already seen it.

 [http://core.trac.wordpress.org/ticket/17632#comment:15 @WraithKenny]:
 thanx for the explanation about the relevance of the check for
 `$wp_request->using_permalinks()`!  That's '''very''' helpful background.

 However, the rel-tag spec [2] is no longer relevant, at least in the
 context of HTML5.  The fact that `@rel='tag'` is listed in the table in
 the ''formats'' section [3] of the microformats wiki (with a link to [2])
 doesn't make it normative for HTML5, which gives it's own definition for
 `@rel='tag'` that supersedes anything else and explicitly references the
 table in the ''HTML5 link type extensions'' section [4] as being normative
 for values not defined within itself.

 re: my concern about `@rel='tag'` being used for links within a document
 containing posts from many different categories, I see that the rel-tag
 spec contains the following language:

 {{{
 Note that a tag may just refer to a major portion of the
 current page (i.e. a blog post)
 }}}

 So, with that interpretation (and based on what you said about `?tag=foo`
 was in the mind of whoever wrote the code that generates `@rel='tag'`), I
 don't see (much of) a problem with `@rel='tag'` being used in a document
 containing posts from many different categories.

 But, as I said above, HTML5 does not rely on the rel-tag spec [2] for the
 semantics of `@rel='tag'`, it defines its own.  HTML5 also contains the
 following non-normative note after it's definition of `@rel='tag'`:

 {{{
 Note: Since it indicates that the tag applies to the current document,
 it would be inappropriate to use this keyword in the markup of a tag
 cloud, which lists the popular tags across a set of pages.
 }}}

 which is where my trepidation about it's use on a home page came from (and
 that trepidation extends to by-date or by-author archives and anywhere
 else posts from multiple categories could appear).

 Your point about it's use within the context of `article` is interesting,
 since the HTML5 spec says [5]:

 {{{
 The article element represents a self-contained composition in a
 document, page, application, or site and that is, in principle,
 independently distributable or reusable, e.g. in syndication.
 This could be a forum post, a magazine or newspaper article,
 a blog entry, a user-submitted comment, an interactive widget
 or gadget, or any other independent item of content.
 }}}

 Which, while non-normative, could be used to justify a request to the
 HTML5 WG that they loosen the definition of @rel='tag' to include not only
 `documents` but also such "self-contained compositions...".  I'll talk to
 folks on the W3C HTML5 WG about whether they think that would be
 appropriate.

 But even if they do make such a change (and hence,
 `article//a[@rel*='tag']` having the correct semantics when other
 `article`'s in the same document are assigned to different categories, my
 suggestion to parameterize `get_the_category_list()` still applies because
 there is nothing to prevent it being called outside of that context.

 But your point about opening another ticket about that is well taken and I
 didn't mean to co-opt this one on that point.  But, I'm tired and will
 open that other ticket tomorrow.

 My purpose in what I have said in this ticket (and the support thread [1])
 has only been to point out that `@rel='category'` is not, in your words,
 "obsolete and invalid in html5", if only it's use were documented and that
 the patch should '''not''' be applied, at least until the semantics of the
 use of `@rel='tag'` in a "multi-category" context are clarified: replacing
 one incorrect usage with another incorrect usage just to get validators to
 shut up is '''not''' the right thing to do.

 [1] http://wordpress.org/support/topic/wordpress-abuses-rel-
 tag?replies=29#post-2721386 [[BR]]
 [2] http://microformats.org/wiki/rel-tag#Tag_Spaces [[BR]]
 [3] http://microformats.org/wiki/existing-rel-values#formats [[BR]]
 [4] http://microformats.org/wiki/existing-rel-
 values#HTML5_link_type_extensions [[BR]]
 [5] http://dev.w3.org/html5/spec/single-page.html#link-type-tag [[BR]]

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17632#comment:18>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software