- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Mon, 4 Feb 2013 14:15:32 -0500
- To: Reece Dunn <msclrhd@googlemail.com>
- CC: W3C RDFa WG <public-rdfa-wg@w3.org>
On Feb 4, 2013, at 10:13 AM, Reece Dunn <msclrhd@googlemail.com> wrote: > On 4 February 2013 17:45, Gregg Kellogg <gregg@greggkellogg.net> wrote: > I re-generated a rollup EARL report [1] for most of the processors defined in the processors.json file. The good news is that we have 2 processors passing 100% of the tests for HTML5+RDFa and XHTML5+RDFa (pyRdfa and RDF::RDFa). We also have a different two processors passing 100% of the Processor Graph tests (RDF::RDFa and Semargl), and 4 processors passing vocabulary expansion (clj-rdfa, pyRdfa, RDF::RDFa and Semargl). > > Specific per-processor results are summarized in [2]. > > The processors tested were the following: > > * any23, > * clj-rdfa, > * EasyRdf, > * java-rdfa, > * librdfa, > * pyRdfa, > * RDF-RDFa-Parser, > * RDF::RDFa, and > * Semargl > > If you implement an HTML5+RDFa conformant processor and would like your results included, please submit EARL results, with an earl:subject referencing a DOAP description. If the subject does not define a Description of a Project (DOAP), you can send in a DOAP file which will be used for generating the results. The specific entries used in the report generator are determined by this SPARQL query: > > PREFIX doap: <http://usefulinc.com/ns/doap#> > PREFIX foaf: <http://xmlns.com/foaf/0.1/> > PREFIX rdfatest: <http://rdfa.info/vocabs/rdfa-test#> > > SELECT DISTINCT ?uri ?name ?developer ?dev_name ?dev_type ?doap_desc ?homepage ?language > WHERE { > ?uri doap:name ?name . > OPTIONAL { ?uri doap:developer ?developer . ?developer foaf:name ?dev_name .} > OPTIONAL { ?uri doap:developer ?developer . ?developer a ?dev_type . } > OPTIONAL { ?uri doap:homepage ?homepage . } > OPTIONAL { ?uri doap:description ?doap_desc . } > OPTIONAL { ?uri doap:programming-language ?language . } > } > > EARL reports can be generated through the RDFa Test Suite [3], by setting the processor URL and running all tests for each combination of host language and RDFa version to be tested, or through other means. > > Gregg Kellogg > gregg@greggkellogg.net > > [1] http://rdfa.info/earl-reports/earl.html#processors > [2] http://rdfa.info/earl-reports/earl.html > [2] http://rdfa.info/test-suite > > Hi, > > Is it possible to run the tests on a command-line RDFa processor (e.g. the rapper command-line tool) and generate an EARL report that way? Yes, if you clone the RDFa repository [1], do a "bundle install", you can use bin/run-suite to run all (or selected) tests against a processor. There is an example command-line shell in bin/rdf-rdfa, which can be invoked as follows: bin/run-suite bin/rdf-rdfa The command-line shell takes some standard arguments (--rdfagraph, --uri, --vocab_expansion, --version) and either STDIN or a URL argument referencing the test to run. The results are processed the the SPARQL query to get pass/fail. You can also run against a locally running HTTP processor, by giving the appropriate URI for the processor similar to those available online. There's a bit of documentation in the README at [1]. Gregg [1] http://github.com/rdfa/rdfa-website > The reason I ask is I have a command-line metadata extractor tool that I would like to run these tests against when I implement RDFa to check RDFa conformance. That tool does not have a web-based front end, nor do I want to create one just to test RDFa conformance. > > Thanks, > - Reece
Received on Monday, 4 February 2013 19:16:19 UTC