This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8747 - Defining how a license applies to elements
Summary: Defining how a license applies to elements
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y, a11y_semantics
Depends on:
Reported: 2010-01-14 15:18 UTC by Gez Lemon
Modified: 2010-10-05 13:03 UTC (History)
5 users (show)

See Also:


Description Gez Lemon 2010-01-14 15:18:10 UTC
The paragraph after the HTML example code states, "In this case, the license applies to just the photo, not the whole document." However, the example is not marked up in a way that can be determined by assistive technology. If license is meant to apply to anything other than the entire document, the specification should define rules to make the relationship determinable by assistive technology.
Comment 1 Michael Cooper 2010-02-11 17:18:36 UTC
The HTML Accessibility Task Force intends to track these issues, per the proposal at
Comment 2 Toby Inkster 2010-02-12 10:06:34 UTC
Not entirely sure why this is a11y-related.

However, the HTML+RDFa draft (and in XHTML, the XHTML+RDFa Rec) provides quite a simple solution.

    <a rel="license" href="licence-uri">...</a>


    <a about="thing-uri" rel="license" href="licence-uri">...</a>

Where thing-uri is the thing being licensed. So, if you wish to indicate the licence of an image:

    <a about="foobar.jpeg" rel="license" href="licence-uri">...</a>

Or, if you have a paragraph of text on a page that needs licensing:

    <p id="chunk">...</p>
    <a about="#chunk" rel="license" href="licence-uri">...</a>


Microdata is also able to provide a solution, though I think RDFa's is somewhat more elegant in this simple case.
Comment 3 Ian 'Hixie' Hickson 2010-02-12 10:16:09 UTC
If you have the image in the page, in RDFa it looks like:

   <img src="foobar.jpeg" alt="...">
   <a about="foobar.jpeg" rel="license" href="licence-uri">...</a>

With microdata it looks like:

   <div itemscope itemtype="">
     <img itemprop="work" src="foobar.jpeg" alt="...">
     <a itemprop="license" href="licence-uri">...</a>
Comment 4 Ian 'Hixie' Hickson 2010-02-23 07:14:57 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change
Rationale: Existing pages use rel=license as described in the spec. There isn't enough information in those pages for any algorithm (accessibility-related or otherwise) to identify the item to which the license applies. As Toby mentioned, that's why we have RDFa, or microdata, or other such solutions.

I'm not sure, therefore, how to address this bug. Please reopen the bug if there is something I can do to further help here.
Comment 5 Michael Cooper 2010-08-28 14:35:24 UTC

Close and remove Task Force from further following. Ask on the main HTML list if someone wants to take over this bug to pursue getting the RDFa suggestion in the bug into the spec.