rel-license-issues

(Difference between revisions)

Jump to: navigation, search
(RFC 4946)
Current revision (04:54, 7 April 2013) (view source)
m (Reverted edits by ABIDEEN10 (Talk) to last version by TobyInk)
 
(9 intermediate revisions not shown.)
Line 1: Line 1:
 +
=rel-license issues=
 +
 +
== Template ==
 +
{{issues-format}}
 +
==Issues==
==Issues==
Line 11: Line 16:
*#* ACCEPTED. MOVE TO FAQ. The HTML 4.01 spec defines the 'copyright' rel value as: "Refers to a copyright statement for the current document."  Indeed this is very similar to the license provision, however not exactly the same.  Often documents have a their own local copyright statement which includes links to one or more licenses.  See the [http://gmpg.org/xfn/ XFN home page] for example, which uses both a <code>&lt;link rel="copyright&gt;</code> in the header to reference a local copyright statement, and within that, links to a Creative Commons license with rel="license".
*#* ACCEPTED. MOVE TO FAQ. The HTML 4.01 spec defines the 'copyright' rel value as: "Refers to a copyright statement for the current document."  Indeed this is very similar to the license provision, however not exactly the same.  Often documents have a their own local copyright statement which includes links to one or more licenses.  See the [http://gmpg.org/xfn/ XFN home page] for example, which uses both a <code>&lt;link rel="copyright&gt;</code> in the header to reference a local copyright statement, and within that, links to a Creative Commons license with rel="license".
-
* 2006-04-07 raised by [[User:Evan|Evan]]
+
* {{OpenIssue}} 2006-04-07 raised by [[User:Evan|Evan]]
*# ''Issue 1: It's not clear how to associate a license with part of a page, such as an image or embedded object in the page, or a single news entry on a news page. A typical use-case would be a [http://flickr.com/photos/mauve_porno_rod/4458687/ Flickr page], for which the image is licensed under a CC license but the page itself is not.''
*# ''Issue 1: It's not clear how to associate a license with part of a page, such as an image or embedded object in the page, or a single news entry on a news page. A typical use-case would be a [http://flickr.com/photos/mauve_porno_rod/4458687/ Flickr page], for which the image is licensed under a CC license but the page itself is not.''
-
*# ''Issue 2: there's not a clear explanation of how/when to use a <link> element with rel='copyright' (as definied in the [http://www.w3.org/TR/REC-html40/types.html#type-links HTML spec]) and an <a> element with rel='license'.''
+
*# ''Issue 2: there's not a clear explanation of how/when to use a <link> element with rel='copyright' (as defined in the [http://www.w3.org/TR/REC-html40/types.html#type-links HTML spec]) and an <a> element with rel='license'.''
*# ''Issue 3: the [http://www.dublincore.org/documents/dcmi-terms/ Dublin Core] 'license' element seems to have the exact same semantics as this standard. There's an [http://www.dublincore.org/documents/dcq-html/ encoding standard for Dublin Core in <meta> and <link> elements], which seems like it would be an easy extension to rel attributes in <a> elements. Can we find some compatibility between the Dublin Core 'license' and rel='license'?''
*# ''Issue 3: the [http://www.dublincore.org/documents/dcmi-terms/ Dublin Core] 'license' element seems to have the exact same semantics as this standard. There's an [http://www.dublincore.org/documents/dcq-html/ encoding standard for Dublin Core in <meta> and <link> elements], which seems like it would be an easy extension to rel attributes in <a> elements. Can we find some compatibility between the Dublin Core 'license' and rel='license'?''
-
* 2006-07-19 raised by [[User: DrErnie |DrErnie]]
+
* {{OpenIssue}} 2006-07-19 raised by [[User: DrErnie |DrErnie]]
-
* Now that  [http://www.ietf.org/rfc/rfc4946.txt RFC 4946] specifies rel-license for Atom, should we adopt that as a normative reference?  
+
*# ''Now that  [http://www.ietf.org/rfc/rfc4946.txt RFC 4946] specifies rel-license for Atom, should we adopt that as a normative reference?''
 +
 
 +
<div class="vevent">
 +
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-26</span> raised by <span class="fn">[[User:Adollar28cents|Adollar28cents]]</span></span>
 +
<div class="description">
 +
*# ''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. [http://tobyinkster.co.uk/blog/2008/01/15/gnocchi-allamatriciana/ Example usage] [[User:TobyInk|TobyInk]] 01:53, 18 Feb 2008 (PST)
 +
</div>
 +
</div>
==See also==
==See also==
* [[rel-faq]]
* [[rel-faq]]

Current revision

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