[open-science] Open Science Microformats/Pattern languages? was Re: Launch of the Panton Principles for Open Data in Science + Is It Open Data?

Thu Feb 25 12:15:27 UTC 2010

On Feb 24, 2010, at 6:56 PM, Jean-Claude Bradley wrote:

> We added this CC0 logo and license
> <a rel="license" href="http://creativecommons.org/publicdomain/zero/1.0/ 
> " style="text-decoration:none;">
>     <img src="http://i.creativecommons.org/l/zero/1.0/88x31.png"  
> border="0" alt="CC0" />
>   </a>
>
> to the nav bar on the ONSC wiki
> http://onschallenge.wikispaces.com/
>
> and to the results of any solubility search:
> http://old.oru.edu/cccda/sl/solubility/allsolvents.php?solute=benzoic%2520acid
>
> Does this meet the requirements for machine readability of CC0 intent?

Jean-Claude,

Seems like you didn't copy the entire code fragment from the CC0  
chooser. If you had, the above would have looked like so

<a rel="license" href="http://creativecommons.org/publicdomain/zero/1.0/ 
" style="text-decoration:none;"> <img src="http://i.creativecommons.org/l/zero/1.0/88x31.png 
" border="0" alt="CC0" /> </a> To the extent possible under 
law, <a href="http://onschallenge.wikispaces.com/" 
rel="dct:publisher">Jean-Claude</a> 
has waived all copyright and related or neighboring rights to ONS Challenge.

Note: I am using your name and your resource name only for illustration.

The XML namespace declaration tells a parser that "the terms we are  
going to use here are as per their meaning established by the Dublin  
Core initiative." See http://dublincore.org/documents/usageguide/elements.shtml

This ensures that when you say poh-tah-toh and I say poh-tay-toh, we  
don't call the whole thing off.

Once the parser has established that we are talking DC-speak, which  
will henceforth (for the scope of this session) be referred to by the  
alias 'dct', it knows exactly what you mean by dct:publisher and  
dct:title, etc.

Now, I understand that you may not want to pollute your lovely looking  
navbar with all the text that will show up. No problem -- just put the  
stuff you don't want humans to see as an html comment. A source code  
parser will still be able to crack the meaning out, and your web page  
will still look lovely. The point is, don't omit the code, as that is  
what adds the machine-readable intelligence to the license waiver.

Hope that helps.

>
> Jean-Claude
>
> ..

-- 
Puneet Kishor http://www.punkish.org
Carbon Model http://carbonmodel.org
Charter Member, Open Source Geospatial Foundation http://www.osgeo.org
Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor
Nelson Institute, UW-Madison http://www.nelson.wisc.edu
-----------------------------------------------------------------------
Assertions are politics; backing up assertions with evidence is science
=======================================================================