rel-license-issues

Jump to: navigation, search

Contents

rel-license issues

Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>

Issues

    1. How would I specify that there is no license for something, i.e. All Rights Reserved. There is no Creative Commons machine-readable license that says as much, but I want to support and use this microformat.
      • My own solution is that when a URL exists for the license to use both a <LINK> element and an <A> element to link to the license using rel="license DC.rights.license" (i.e. both the rel-license microformat plus Dubin Core), and when no such URL exists, to use a <META> element with name="DC.rights.license" and a content attribute containing a human readable licence description, such as content="All rights reserved." (The phrase "All rights reserved" also appears in the body of the page. Example usage TobyInk 01:53, 18 Feb 2008 (PST)

See also

rel-license-issues was last modified: Sunday, April 7th, 2013

Views