rel-license-issues - Revision history

Tantek: Reverted edits by ABIDEEN10 (Talk) to last version by TobyInk

2013-04-07T04:54:05Z

Reverted edits by ABIDEEN10 (Talk) to last version by TobyInk

Show changes

ABIDEEN10 at 03:40, 7 April 2013

2013-04-07T03:40:29Z

Show changes

TobyInk: /* Issues */

2008-02-18T09:56:54Z

Issues

← Older revision		Revision as of 09:56, 18 February 2008
Line 22:		Line 22:

	* {{OpenIssue}} 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">		<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>		* {{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">		<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."		*# ''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)		# 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>

TobyInk: /* Issues */

2008-02-18T09:55:51Z

Issues

← Older revision		Revision as of 09:55, 18 February 2008
Line 22:		Line 22:

	* {{OpenIssue}} 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">		<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>		* {{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">		<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.		*# "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)		# 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>

TobyInk: /* Issues */

2008-02-18T09:54:46Z

Issues

← Older revision		Revision as of 09:54, 18 February 2008
Line 28:		Line 28:
	<div class="description">		<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.		*# 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)		# 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>
	</div>		</div>

TobyInk: /* Issues */

2008-02-18T09:54:02Z

Issues

← Older revision		Revision as of 09:54, 18 February 2008
Line 28:		Line 28:
	<div class="description">		<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.		*# 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)		** 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>
	</div>		</div>

TobyInk: /* Issues */

2008-02-18T09:53:34Z

Issues

← Older revision		Revision as of 09:53, 18 February 2008
Line 28:		Line 28:
	<div class="description">		<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.		*# 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>
	</div>		</div>

Adollar28cents: /* Issues */

2008-01-27T06:10:27Z

Issues

← Older revision		Revision as of 06:10, 27 January 2008
Line 23:		Line 23:
	* {{OpenIssue}} 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.
			</div>
			</div>

	==See also==		==See also==
	* [[rel-faq]]		* [[rel-faq]]

AndyMabbett: Template; headings

2008-01-14T10:47:55Z

Template; headings

← Older revision		Revision as of 10:47, 14 January 2008
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><link rel="copyright></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><link rel="copyright></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?

	==See also==		==See also==
	* [[rel-faq]]		* [[rel-faq]]

DrErnie: /* Issues */

2007-07-19T22:34:36Z

Issues

← Older revision		Revision as of 22:34, 19 July 2007
Line 17:		Line 17:

	* 2006-07-19 raised by [[User: DrErnie \|DrErnie]]		* 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?

	==See also==		==See also==
	* [[rel-faq]]		* [[rel-faq]]