Re: Preliminary EARL report

Gregg,

beautiful. Only two mini-mini comments

- we should use some other title for the document. Probably simply 'test report'
- the references should all be informal. This will not become a standard, maybe not even a note, so normative references make no sense.

Thanks

Ivan


On Mar 17, 2012, at 07:29 , Gregg Kellogg wrote:

> I've updated the report [1], and addressed most of your issues. Note that I haven't yet provided alternative versions of the individual tests.
> 
> Note that I made up DOAP information for librdfa and clj-rdfa: if you have something better, it can be added to processors.json.
> 
> I ran with Manu's and Niklas' processors, but I wasn't able to run XHTML1 with the clojure implementation for some reason. I've updated my version (used for showing details) based on test failures I encountered, and there still are probably a couple of more tests that need to be added.
> 
> Further feedback on the report contents and format is appreciated.
> 
> Gregg
> 
> [1] http://rdfa.info/earl-reports/
> 
> On Mar 14, 2012, at 1:28 AM, Ivan Herman wrote:
> 
>> Gregg,
>> 
>> this is a really great. My comments are really only cosmetic, and probably easy to add.
>> 
>> - Just to make it formally better, in terms of reporting at the end of the CR period, it is probably better to run the vocab section both with xml and xhtml1. I know the tests are identical, but better having that there instead of being asked to make additional explanations.
>> 
>> - Actually, an SVG run would be nice as well. We know that, test-wise, it is the same as for XML, but good to have that, too (maybe in the Appendix, to avoid overcrowding the text)
>> 
>> - We should work on adding more info. I am not sure what is already available in the EARL reports. As far as I could see, the titles and the short descriptions of the tests are there; it may be worth adding these to the tables, additionally to the test numbers. Also, we should try to get some sort of an explanation for each of the sections (what do we mean by rdfa11.1-vocab, this sort of things). 
>> 
>> - This may have to be done manually, but we should also provide a short description for each of the processors: who did it, what does it offer, where is it available, etc. For example, the URI-s you provide there are, in some sense, not a reference to the tools themselves in general but, rather, the way an online service should be run. We should have links for both for each.
>> 
>> - I would put the 'individual test results' list to the end. Hopefully we will have more than just these three, and that list may become very long. Maybe putting them in a tabular format is also a possibility. Also, we should add a remark that these links are to the EARL reports in RDFa (and maybe add a separate link to get directly to the turtle format of the individual reports).
>> 
>> As I said, I believe all these are really minor issues only. All in all, it looks great!
>> 
>> Huge thank!
>> 
>> Ivan
>> 
>> 
>> 
>> On Mar 14, 2012, at 01:46 , Gregg Kellogg wrote:
>> 
>>> I ran reports for Ivan's and my processors against XML, XHTML1, and HTML5 along with vocabulary-expansion for XML. (Note, XML1 has been renamed to just XML, at Ivan's suggestion). I collected all the reports in the /earl-reports directory, with a consolidated report available at [1]. There could obviously be some better explanatory information, but the core processing work is done. Note this information is (of course) encoded with RDFa, and is available through some alternative representations, as described in the report.
>>> 
>>> Note that between Ivan and I, we pass everything (except 0235 in XHTML1 for mine, for some odd reason). I think there may be some remaining XMLLiteral issues to be worked out.
>>> 
>>> About report generation:
>>> 
>>> Individual reports are generated as HTML+RDFa and parsed into a common graph, which is then output as both Turtle and JSON-LD. Note that the structure of the EARL report has been supplemented to allow for the JSON-LD framing. This is then used directly in a Ruby/Haml template to generate the HTML report.
>>> 
>>> Feedback appreciated!
>>> 
>>> Gregg
>>> 
>>> [1] http://rdfa.info/earl-reports/
>> 
>> 
>> ----
>> 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
>> 
>> 
>> 
>> 
>> 
> 


----
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