[Bug 17579] New: Apply 'tag' (link type) to its nearest article or body element ancestor

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17579

           Summary: Apply 'tag' (link type) to its nearest article or body
                    element ancestor
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: res-html@untief.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


(if it's undesirable for a link type definition to differ from 'a'/'area' to
'link', dump this issue)

The spec about the 'rel' keyword 'tag' states:
"The tag keyword indicates that the tag that the referenced document represents
applies to the current document."

I think it would be useful if the tag (when linked with the 'a'/'area' element)
applies to its nearest article or body element ancestor, instead (which is the
case for the 'address' element, too).

Thereby a page listing several articles could make use of the 'tag' keyword:

<section>
  <h1>Recent articles</h1>

  <article>
    <h1>My first cooking lesson</h1>
    <p>… — <a href="/blog/cooking-lesson">Read
more</a></p>
    <footer>Tagged with <a href="/tags/cooking"
rel="tag">Cooking</a></footer>
  <article>

  <article>
    <h1>I scored two goals</h1>
    <p>… — <a href="/blog/two-goals">Read more</a></p>
    <footer>Tagged with <a href="/tags/football"
rel="tag">Football</a></footer>
  <article>

</section>

With the current definition, the tags "Cooking" and "Football" apply to the
whole page. 
With my proposed addition, the tag "Cooking" applies only to the first article
snippet, the tag "Football" only to the second.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 23 June 2012 00:10:24 UTC