[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 18:58:11 UTC 2010

Thanks to Puneet and Jean-Claude for providing feedback on the
XHTML+RDFa generated by the CC0 chooser.  I've fixed a bug in that code,
and updated the site.

You can find an example of a page with the markup pasted in (and the
appropriate doctype, etc) that validates at
http://labs.creativecommons.org/~nathan/validation_test.html.

Regards,

Nathan

On 02/25/2010 09:15 AM, Mr. Puneet Kishor wrote:
> Just to keep you all updated. I received a reply from the intrepid coder
> at CC who is looking into the issue, and will let me (us) know as soon
> as there is a fix. This is quality service, I must say rather
> approvingly and admiringly.
> 
> Puneet.
> 
> 
> On Feb 25, 2010, at 8:53 AM, Jean-Claude Bradley wrote:
> 
>> OK - I sent a comment about this problem to CC
>>
>> On Thu, Feb 25, 2010 at 8:45 AM, Mr. Puneet Kishor
>> <punkish at eidesis.org> wrote:
>>
>> On Feb 25, 2010, at 7:33 AM, Jean-Claude Bradley wrote:
>>
>> Puneet,
>> Until the issue gets resolved will putting this allow for automatic
>> discovery of CC0 licensed content?
>> <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>
>>
>>
>>
>> I am skating on thin ice here, but my understanding is that it won't
>> be enough. The 'rel' attribute indicates a relationship between your
>> document and the linked-to document, declaring the linked document to
>> be a "license." The other bits that you are omitting, actually allow
>> extracting terms such as 'publisher' and 'title' from your
>> declaration. Note that if one (a human being or a program) follows the
>> a href, they land up at the CC0 waiver page where they can get an
>> earful re. the CC0 waiver, but have no clue as to the entity that
>> actually used that waiver.
>>
>> I have sent a query to CC, and I suggest you do so as well. Hopefully
>> we will have this resolved rapidly. In the meantime, as I said, just
>> put the whole bit inside HTML comments, with only the CC0 badge
>> showing up and going through the validator.
>>
>>
>> On Thu, Feb 25, 2010 at 8:05 AM, Mr. Puneet Kishor
>> <punkish at eidesis.org> wrote:
>> Jean-Claude,
>>
>>
>>
>> On Feb 25, 2010, at 6:26 AM, Jean-Claude Bradley wrote:
>>
>> Puneet
>> I tried to use the entire code generated by
>> http://creativecommons.org/choose/zero
>>
>> But it kept throwing an HTML error code:
>> The HTML you have entered is not valid HTML: No declaration for
>> attribute content of element span
>>
>> Yes, that is a problem, and not just because it is not valid HTML. It
>> doesn't seem to be valid XHTML+RDFa as well, as per the validator at
>> http://validator.w3.org/check
>>
>> Interestingly, W3C's recommended RDFa syntax at
>> http://www.w3.org/TR/rdfa-syntax/ also doesn't seem to pass W3C's
>> validator.
>>
>> So, now what to do? First, let's inform CC that this is an issue. I am
>> sending them an email, but you should also send one to explain the
>> problem and add to the feedback.
>>
>> Second, perhaps the best option may be to put the entire CC0 code in
>> comments, and only put valid markup visible to the validator.
>>
>> Of course, you could just ignore the errors and proceed merrily, but
>> that is not right. I think our feedback should help CC fix this or at
>> least clarify what DOCTYPE we need to use in order to generate RDFa
>> markup that passes the validator 100%. This needs to be even more easy
>> and clear.
>>
>> Many thanks,
>>
>>
>>
>>
>> This is the code:
>> <p xmlns:dct="http://purl.org/dc/terms/"
>> xmlns:vcard="http://www.w3.org/2001/vcard-rdf/3.0#">
>>  <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>
>>  <br />
>>  To the extent possible under law, <a
>> href="http://onschallenge.wikispaces.com" rel="dct:publisher"><span
>> property="dct:title">Jean-Claude Bradley</span></a>
>>  has waived all copyright and related or neighboring rights to
>>  <span property="dct:title">ONS Challenge</span>.
>> This work is published from
>> <span about="http://onschallenge.wikispaces.com"
>> property="vcard:Country" datatype="dct:ISO3166" content="US">United
>> States</span>.
>> </p>
>>
>>
>> On Thu, Feb 25, 2010 at 7:15 AM, Mr. Puneet Kishor
>> <punkish at eidesis.org> wrote:
>>
>> 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
>>
>> <p xmlns:dct="http://purl.org/dc/terms/"
>> xmlns:vcard="http://www.w3.org/2001/vcard-rdf/3.0#"> <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> <br /> To the extent possible under law, <a
>> href="http://onschallenge.wikispaces.com/" rel="dct:publisher"><span
>> property="dct:title">Jean-Claude</span></a> has waived all copyright
>> and related or neighboring rights to <span property="dct:title">ONS
>> Challenge</span>. </p>
>>
>> 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
>> =======================================================================
>>
>>
>>
>>
>> -- 
>> Jean-Claude Bradley, Ph. D.
>> E-Learning Coordinator for the College of Arts and Sciences
>> Associate Professor of Chemistry
>> Drexel University
>>
>> http://usefulchem.blogspot.com
>> http://drexel-coas-elearning.blogspot.com
>> http://drexel-coas-talks-mp3-podcast.blogspot.com/
>> http://friendfeed.com/jcbradley
>>
> 
> 
> 
> _______________________________________________
> open-science mailing list
> open-science at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/open-science

-- 
Nathan R. Yergler
Chief Technology Officer
Creative Commons

http://wiki.creativecommons.org/User:Nathan_Yergler