https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=FinBuu 2026-04-05T23:09:39Z User contributions MediaWiki 1.38.4 https://microformats.org/wiki/index.php?title=rel-license-issues&diff=17769 2007-06-22T17:56:32Z

<p>FinBuu: </p> <hr /> <div>==Issues==<br /> <br /> * 2005-06-21 raised by Hixie<br /> *# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how rel=license must be handled.<br /> *#* ACCEPTED. The specification should have a conformance section describing what UAs should do.<br /> *# ''Issue H-2: What's the point of rel=&quot;license&quot;?<br /> *#* ACCEPTED. The specification should provide better documentation explaining this (it tries to now, but obviously failed for this particular reader). In particular rel=&quot;license&quot; 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.<br /> <br /> * 2005-12-09 raised by Kenny Heaton<br /> *# ''There needs to be an explicit explanation of when to use rel-license which &quot;Indicates that the referred resource is a license for the referring page.&quot;, and when to use the W3C defined copyright link type which &quot;Refers to a copyright statement for the current document.&quot; since copyright and licensing are similar concepts and can be confused.<br /> *#* ACCEPTED. MOVE TO FAQ. The HTML 4.01 spec defines the 'copyright' rel value as: &quot;Refers to a copyright statement for the current document.&quot; 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 &lt;code&gt;</div>

FinBuu