Skip to Content.
Sympa Menu

cc-metadata - Re: All content on this site is availabe under a CC license

cc-metadata AT lists.ibiblio.org

Subject: discussion of the Creative Commons Metadata work

List archive

Re: All content on this site is availabe under a CC license

Chronological Thread  
    < Chronological >       < Thread >
  • From: "Firas D." <fd AT firasd.org>
  • To: discussion of the Creative Commons Metadata work <cc-metadata AT lists.ibiblio.org>
  • Subject: Re: All content on this site is availabe under a CC license
  • Date: Wed, 09 Feb 2005 19:10:05 -0500
Mike Linksvayer wrote:

Firas D. wrote:

An HTTP header? X-License: http://creativecommons.org/licenses/by-nd/2.0


That presumably says the same thing as embedding rdf:about="" in a page (the current URI is licensed).


No, it means any object served with said header is licensed. With .htaccess (in apache), one may say,

Header append X-License: http://creativecommons.org/licenses/by-nd/2.0, or:

<Files mybook.pdf>
Header append X-License: http://creativecommons.org/licenses/by-nd/2.0
</Files>

<FilesMatch *.(gif|jpg|jpeg|bmp)>
Header append X-License: http://creativecommons.org/licenses/by-nd/2.0
</FilesMatch>

Does XMDP provide for a way to add semantics to values of the html class attribute?

So people can say

<blockquote class="license-http://creativecommons.org/licenses/by-nd/2.0";>
<img class="license-http://creativecommons.org/licenses/by-nd/2.0";>
<embed class="license-http://creativecommons.org/licenses/by-nd/2.0";>

And so on.


I'm not sure what assertion your sample above is trying to make. That an image is specifically licensed? We can do that now with RDF.

My specific concern is a weblogging tool, so when people post images they say:

<img src="mypic.jpg" alt="Me and Sarah by a tree" class="insert" />

If they specify a license, I can just add in:

<img src="mypic.jpg" alt="Me and Sarah by a tree" class="insert license-http://creativecommons.org/by/2.0"; />

I'd never inflict the CC RDF inside the <body> tag. It's ugly..


I suggest that the license for each object referenced via an HTML document be resolved this way:

1. License embedded in the file; if unavailable, then:
2. License in the license-* value of the class attribute of the HTML tag that references it; if unavailable, then:
4. License in the X-License HTTP header.

This is a bit like CSS in the way that the style referenced with the most specificity is the style applied from clashing rules.

I should revise that, it would be:

1. Embedded License
2. License in header
3. License in referencing HTML tag


Archive powered by MHonArc 2.6.24.

Top of Page