Creative Commons copyright link
19th December 2002
It’s great to see the Creative Commons getting an overwhelmingly positive reception—as Lessig says on his blog,
’Tis the season to be giving, and this will be a great gift to the Commons. If you haven’t seen their explanatory flash animation, Get Creative, you should really check it out.
That said, I have to admit I have a few reservations about the machine readable form of the CC licenses. The recommended way of including them in a page is RDF embedded in a comment, similar to Moveable Type’s Trackback system. This is fine for HTML documents (although it feels like a bit of a cludge) but is problematic when used with XHTML. Why? Because XHTML documents are XML documents, and the XML specification states that
an XML processor may, but need not, make it possible for an application to retrieve the text of comments. The logical way of extracting Creative Commons information from an XHTML document would be to parse it with an XML processor, but it is likely that many processors will be unable to extract the comments (and even those with the ability to extract them will not treat them as XML, requiring a second run of the XML parser to extract information from the RDF). In practical terms this is unlikely to be a problem as regular expressions can be used instead, but from an idealogical point of view it leaves something of a bad taste in the mouth.
If I’m going to criticise the embedded RDF approach I should probably suggest an alternative. The HTML 4 specification describes a “Copyright” link type which is defined as follows:
- Refers to a copyright statement for the current document.
I suggest using a
link element in the
<head> section of a document which points to the Creative Commons license governing the page in question (or to an RDF document similar to that currently used by the embedded comments method). If you view source on your page you will see that I have done exactly that.
More recent articles
- Datasette Enrichments: a new plugin framework for augmenting your data - 1st December 2023
- llamafile is the new best way to run a LLM on your own computer - 29th November 2023
- Prompt injection explained, November 2023 edition - 27th November 2023
- I'm on the Newsroom Robots podcast, with thoughts on the OpenAI board - 25th November 2023
- Weeknotes: DevDay, GitHub Universe, OpenAI chaos - 22nd November 2023
- Deciphering clues in a news article to understand how it was reported - 22nd November 2023
- Exploring GPTs: ChatGPT in a trench coat? - 15th November 2023
- Financial sustainability for open source projects at GitHub Universe - 10th November 2023
- ospeak: a CLI tool for speaking text in the terminal via OpenAI - 7th November 2023
- DALL-E 3, GPT4All, PMTiles, sqlite-migrate, datasette-edit-schema - 30th October 2023