W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > March 2012

Re: Preliminary EARL report

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Thu, 15 Mar 2012 02:48:02 -0400
To: Ivan Herman <ivan@w3.org>
CC: Manu Sporny <msporny@digitalbazaar.com>, public-rdfa-wg WG <public-rdfa-wg@w3.org>
Message-ID: <2804F844-B5F9-4D63-88EC-1C81E839F44E@greggkellogg.net>
On Mar 14, 2012, at 11:02 PM, Ivan Herman wrote:

> Gregg,
> 
> Just a few thoughts, but I am on a workshop today...
> 
> - the license URI issue is a question of a WG decision or, rather agreement. If we all agree that license should be defined in the CC namespace, then (a) the initial context file should be changed (that is for me to do) and (b) a bunch of tests have to be updated and (c) all the implementations have to be changed because, I presume, we all store these URI-s locally somehow. So better synchronize this if we want to do this.

Yes, looking through the minutes I see we discussed it, but didn't resolve it.

> - I will look at your other mail for the missing tests, but necessarily this week. Thanks!
> 
> - to be on the safe side: could you send us a URI to the DOAP file you use for your implementation? In fact, I already have doap included on my processor's home page (of course, in RDFa...) but I would like to be sure that the properties you would use for the EARL report are the right one...

I'm using the DOAP file I referenced before [1] (actually, I'm using a more complete DOAP [2] with information for everything in my distiller, but only extracting the rdf-rdfa bits), and I'm taking your DOAP too; they're pretty compatible, but your doap:description is more of a description of RDFa then your processor.

This is the Turtle I've extracted so far:

<http://rubygems.org/gems/rdf-rdfa> a earl:TestSubject,
     doap:Project;
   dc:creator <http://greggkellogg.net/foaf#me>;
   doap:blog <http://greggkellogg.net/>;
   doap:category <http://dbpedia.org/resource/Resource_Description_Framework>,
     <http://dbpedia.org/resource/Ruby_(programming_language)>;
   doap:contributor <http://nicholas.humfrey@bbc.co.uk>;
   doap:created "2011-08-29"^^<http://www.w3.org/2001/XMLSchema#date>;
   doap:description """
      RDF::RDFa is an RDFa reader/writer for Ruby using the RDF.rb library suite.
    """@en;
   doap:developer <http://greggkellogg.net/foaf#me>;
   doap:documenter <http://greggkellogg.net/foaf#me>;
   doap:homepage <http://github.com/gkellogg/rdf-rdfa>;
   doap:maintainer <http://greggkellogg.net/foaf#me>;
   doap:name "RDF.rb", "RDF::RDFa";
   doap:programming-language "Ruby";
   doap:shortdesc "RDFa reader/writer for Ruby."@en;
   <http://www.w3.org/1999/xhtml/vocab#license> <http://creativecommons.org/licenses/publicdomain/>;
   <http://www.w3.org/ns/rdfa#hasVocabulary> doap:;
   <http://xmlns.com/foaf/0.1/maker> <http://greggkellogg.net/foaf#me> .

<http://www.w3.org/2012/pyRdfa> a earl:TestSubject;
   doap:created "2012-03-13";
   doap:description """RDFa is a
        specification for attributes to be used with XML languages or with HTML5 to
        express structured data. The rendered, hypertext data of XML or HTML is reused by
        the RDFa markup, so that publishers donít need to repeat significant data in the
        document content. The underlying abstract representation is RDF,
        which lets publishers build their own vocabulary, extend others, and evolve their
        vocabulary with maximal interoperability over time. pyRdfa is a distiller that
        generates the RDF triples from an XML or HTML5 file annotated by RDFa in various
        RDF serialization formats. It can either be used directly from a command line or
        via a CGI service. It corresponds to the RDFa 1.1 Core
          document, XHTML+RDFa, and HTML+RDFa
        specifications, as well as to the SVG
          Tiny 1.2 Recommendation for the SVG version.""";
   doap:developer <http://www.ivan-herman.net/foaf#me>;
   doap:file-release <http://dev.w3.org/2004/PythonLib-IH/dist/pyRdfa-3.tar.gz>;
   doap:license <http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231>;
   doap:maintainer <http://www.ivan-herman.net/foaf#me>;
   doap:name  "pyRdfa";
   doap:programming-language "Python";
   doap:repository <http://dev.w3.org/2004/PythonLib-IH/dist/pyRdfa-3.tar.gz>;
   doap:repository-location <http://dev.w3.org/2004/PythonLib-IH/dist/pyRdfa-3.tar.gz>;
   <http://www.w3.org/2000/01/rdf-schema#seeAlso> <http://www.w3.org/TR/rdfa-core/> .

I'm currently planning on using doap:name, doap:description, doap:developer, doap:homepage, and doap:programming-language in the report body.

Gregg

[1] https://raw.github.com/gkellogg/rdf-rdfa/master/etc/doap.html
[2] http://rdf.greggkellogg.net/doap

> Cheers!
> 
> Ivan
> 
> 
> On Mar 14, 2012, at 18:26 , Gregg Kellogg wrote:
> 
>> On Mar 14, 2012, at 7:35 AM, Ivan Herman wrote:
>> 
>>> Manu, 
>>> 
>>> I am on the road so if blog there is, you should write it...
>>> 
>>> However... it seems that we are now closing in to have the test harmess done, but there are still some minor issues. Also, are we sure we have covered all features with the tests? What about initial contexts?
>> 
>> Test 0206: Usage of Default Profile (name should be changed) does just a little of this, looking to see that xsd: is defined, but I think we need some that explicitly looks for all of the prefixes and terms defined for XHTML1, XML/SVG, HTML4/HTML5/XHTML5 is appropriate. I'll add some.
>> 
>> I have a separate email with some other observations of tests we might need to hit MUST statements within the specs.
>> 
>>> We also have to decide on license URI issue. 
>> 
>> The initial context validation specs should hit on this.
>> 
>>> I would prefer to go so public when these are all solved. 
>>> 
>>> Ivan
>>> 
>>> P.S we may want add more implementations to the harness. Niklas'? Shane's?
>> 
>> That would be great! Note that you don't really need to have a publicly accessible processor to do this, if you run it on your own machine and access an internal endpoint; I do this for development all the time.
>> 
>> Send in any tests you have, although we will probably need to do it again after we've stopped adding/changing tests.
>> 
>> Gregg
>> 
>>> ----
>>> Ivan Herman
>>> +31 641044153
>>> 
>>> (Written on my mobile. Excuses for brevity and frequent misspellings...)
>>> 
>>> 
>>> 
>>> On 14 Mar 2012, at 14:35, Manu Sporny <msporny@digitalbazaar.com> wrote:
>>> 
>>>> On 03/14/2012 04:28 AM, Ivan Herman wrote:
>>>>> As I said, I believe all these are really minor issues only. All in
>>>>> all, it looks great!
>>>> 
>>>> Yes, all of this is really great stuff. I'm very impressed with the
>>>> report generation, Gregg. It shows how HTML+RDFa, TURTLE, and JSON-LD
>>>> all work together to generate the final document. I think you should
>>>> definitely blog about how you accomplished this feat. I think many
>>>> people continue to be confused about how all this technology works together.
>>>> 
>>>> Also, we landed our CR exit criteria (thanks to Ivan and Gregg) two days
>>>> after we entered CR. I think we should make some noise about this - blog
>>>> post at W3C Semantic Web blog? Ivan? I can write the blog post.
>>>> 
>>>> Let me know if there are any objections before 4pm EDT today, if not,
>>>> I'll post something about it.
>>>> 
>>>> -- manu
>>>> 
>>>> -- 
>>>> Manu Sporny (skype: msporny, twitter: manusporny)
>>>> President/CEO - Digital Bazaar, Inc.
>>>> blog: PaySwarm Website for Developers Launched
>>>> http://digitalbazaar.com/2012/02/22/new-payswarm-alpha/
>>>> 
>>> 
>> 
> 
> 
> ----
> Ivan Herman, W3C Semantic Web Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> FOAF: http://www.ivan-herman.net/foaf.rdf
> 
> 
> 
> 
> 
Received on Thursday, 15 March 2012 06:49:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:30 UTC