Difference between revisions of "Talk:License HTML Code"

From Creative Commons
Jump to: navigation, search
(Where on cc.org did you find this?)
Line 6: Line 6:
  
 
Using <code>link</code> and/or RDF/XML-embedded-in-HTML-comments are not recommended (the latter was at one point). Updating this article in a second... [[User:Mike Linksvayer|Mike Linksvayer]] 22:45, 8 April 2007 (UTC)
 
Using <code>link</code> and/or RDF/XML-embedded-in-HTML-comments are not recommended (the latter was at one point). Updating this article in a second... [[User:Mike Linksvayer|Mike Linksvayer]] 22:45, 8 April 2007 (UTC)
 +
 +
Actually, I found it on wiki.creativecommons.org, in the source for the [[Developer]] and [[FAQ]] pages. Thanks for the link to the right way to do it--the code I got from the license generation process on creativecommons.org first time around included a span with invalid attributes, but I just went through it again and that no longer seems to be happening.

Revision as of 19:03, 9 April 2007

I couldn't find this information—that is, what exactly one should add to HTML to make its licensing machine-readable—but found this code on creativecommons.org itself. Note that if the desired code is simply that which is generated by the license selection process, this should still be made available as an alternative since the license selection process provides code that doesn't validate as XHTML or HTML unless you strip out those parts referring to the license resource links (which means it's not really machine-readable anymore).

If the code I added is erroneous, could someone provide the valid HTML that should be added to mark up CC-licensed (X)HTML documents and put it on the License_HTML_Code page?

Where on cc.org did you find this?

Using link and/or RDF/XML-embedded-in-HTML-comments are not recommended (the latter was at one point). Updating this article in a second... Mike Linksvayer 22:45, 8 April 2007 (UTC)

Actually, I found it on wiki.creativecommons.org, in the source for the Developer and FAQ pages. Thanks for the link to the right way to do it--the code I got from the license generation process on creativecommons.org first time around included a span with invalid attributes, but I just went through it again and that no longer seems to be happening.