rellicense-issues-fr - Revision history

Brian: Reverted edits by RolliCpasr (Talk) to last version by Tantek

2008-12-20T22:18:14Z

Reverted edits by RolliCpasr (Talk) to last version by Tantek

← Older revision		Revision as of 22:18, 20 December 2008
Line 1:		Line 1:
	~~novarcnaaco~~		==Problématiques==
	==~~ProblÃ©matiques~~==

	~~ProblÃ©matiques soulevÃ©es~~ par le microformat [[rel-license-fr\|rel-license]] :		Problématiques soulevées par le microformat [[rel-license-fr\|rel-license]] :

	* 21 juin 2005 : ~~soulevÃ©e~~ par Hixie		* 21 juin 2005 : soulevée par Hixie
	*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how rel=license must be handled.		*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how rel=license must be handled.
	# ACCEPTED. The specification should have a conformance section describing what UAs should do.		# ACCEPTED. The specification should have a conformance section describing what UAs should do.
Line 10:		Line 9:
	# ACCEPTED. The specification should provide better documentation explaining this (it tries to now, but obviously failed for this particular reader). In particular rel="license" enables a content author to explicitly express in a machine readable way what license(s) the content is licensed under, in particular, by using licenses that reside at external URLs, commonly maintained by various open source and related organizations.		# ACCEPTED. The specification should provide better documentation explaining this (it tries to now, but obviously failed for this particular reader). In particular rel="license" enables a content author to explicitly express in a machine readable way what license(s) the content is licensed under, in particular, by using licenses that reside at external URLs, commonly maintained by various open source and related organizations.

	* 9 ~~dÃ©cembre~~ 2005 ~~soulevÃ©e~~ par Kenny Heaton		* 9 décembre 2005 soulevée par Kenny Heaton
	*# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.		*# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.
	# 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".

RolliCpasr: ricacel

2008-12-20T04:22:38Z

ricacel

← Older revision		Revision as of 04:22, 20 December 2008
Line 1:		Line 1:
	==~~Problématiques~~==		novarcnaaco
			==ProblÃ©matiques==

	~~Problématiques soulevées~~ par le microformat [[rel-license-fr\|rel-license]] :		ProblÃ©matiques soulevÃ©es par le microformat [[rel-license-fr\|rel-license]] :

	* 21 juin 2005 : ~~soulevée~~ par Hixie		* 21 juin 2005 : soulevÃ©e par Hixie
	*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how rel=license must be handled.		*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how rel=license must be handled.
	# ACCEPTED. The specification should have a conformance section describing what UAs should do.		# ACCEPTED. The specification should have a conformance section describing what UAs should do.
Line 9:		Line 10:
	# ACCEPTED. The specification should provide better documentation explaining this (it tries to now, but obviously failed for this particular reader). In particular rel="license" enables a content author to explicitly express in a machine readable way what license(s) the content is licensed under, in particular, by using licenses that reside at external URLs, commonly maintained by various open source and related organizations.		# ACCEPTED. The specification should provide better documentation explaining this (it tries to now, but obviously failed for this particular reader). In particular rel="license" enables a content author to explicitly express in a machine readable way what license(s) the content is licensed under, in particular, by using licenses that reside at external URLs, commonly maintained by various open source and related organizations.

	* 9 ~~décembre~~ 2005 ~~soulevée~~ par Kenny Heaton		* 9 dÃ©cembre 2005 soulevÃ©e par Kenny Heaton
	*# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.		*# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.
	# 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".

Tantek: Reverted edit of HjuPdm, changed back to last version by Tantek

2007-06-06T12:34:48Z

Reverted edit of HjuPdm, changed back to last version by Tantek

@@ Line 11: / Line 11: @@
 * 9 décembre 2005 soulevée par Kenny Heaton
 *# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.
-*#* 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>
+*#* 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".

HjuPdm at 12:25, 6 June 2007

2007-06-06T12:25:27Z

@@ Line 11: / Line 11: @@
 * 9 décembre 2005 soulevée par Kenny Heaton
 *# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.
-*#* 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>

Tantek: Reverted edit of Ph8Ntt, changed back to last version by ChristopheDucamp

2007-04-10T18:38:14Z

Reverted edit of Ph8Ntt, changed back to last version by ChristopheDucamp

@@ Line 11: / Line 11: @@
 * 9 décembre 2005 soulevée par Kenny Heaton
 *# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.
-*#* 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>
+*#* 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".

Ph8Ntt at 18:24, 10 April 2007

2007-04-10T18:24:11Z

@@ Line 11: / Line 11: @@
 * 9 décembre 2005 soulevée par Kenny Heaton
 *# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.
-*#* 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>

ChristopheDucamp: to be translated - link vers fr translation html spec

2006-12-19T07:50:01Z

to be translated - link vers fr translation html spec

← Older revision		Revision as of 07:50, 19 December 2006
Line 15:		Line 15:
	* 2006-04-07 raised by [[User:Evan\|Evan]]		* 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.la-grange.net/w3c/html4.01/types.html#h-6.12 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'?''

			==Voir aussi==
			* [[rel-faq-fr\|rel-faq]]

ChristopheDucamp: /* Problématiques */

2006-06-27T06:54:42Z

Problématiques

← Older revision		Revision as of 06:54, 27 June 2006
Line 1:		Line 1:
	==Problématiques==		==Problématiques==

	Problématiques soulevées par le microformat [[rel-license]] :		Problématiques soulevées par le microformat [[rel-license-fr\|rel-license]] :

	* 21 juin 2005 : soulevée par Hixie		* 21 juin 2005 : soulevée par Hixie

ChristopheDucamp at 06:54, 27 June 2006

2006-06-27T06:54:03Z

New page

==Problématiques==

Problématiques soulevées par le microformat [[rel-license]] :

* 21 juin 2005 : soulevée par Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how rel=license must be handled.
*#* ACCEPTED. The specification should have a conformance section describing what UAs should do.
*# ''Issue H-2: What's the point of rel="license"?
*#* ACCEPTED. The specification should provide better documentation explaining this (it tries to now, but obviously failed for this particular reader). In particular rel="license" enables a content author to explicitly express in a machine readable way what license(s) the content is licensed under, in particular, by using licenses that reside at external URLs, commonly maintained by various open source and related organizations.

* 9 décembre 2005 soulevée par Kenny Heaton
*# ''There needs to be an explicit explanation of when to use rel-license which "Indicates that the referred resource is a license for the referring page.", and when to use the W3C defined copyright link type which "Refers to a copyright statement for the current document." since copyright and licensing are similar concepts and can be confused.
*#* 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]]
*# ''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 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'?''