rellicense-issues-fr: Difference between revisions
Jump to navigation
Jump to search
m (Reverted edit of Ph8Ntt, changed back to last version by ChristopheDucamp) |
No edit summary |
||
| Line 11: | Line 11: | ||
* 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> | *#* 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> | ||
Revision as of 12:25, 6 June 2007
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.
- Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how rel=license must be handled.
- 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 XFN home page for example, which uses both a
- 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 XFN home page for example, which uses both a
- 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.