- From: Ivan Herman <ivan@w3.org>
- Date: Sat, 11 Jun 2016 14:47:41 +0200
- To: Shane McCarron <shane@spec-ops.io>
- Cc: W3C Public Annotation List <public-annotation@w3.org>, Gregg Kellogg <gregg@greggkellogg.net>
- Message-Id: <2ED79737-A8F5-40AF-9BDA-C69FAE28B355@w3.org>
> On 11 Jun 2016, at 13:32, Shane McCarron <shane@spec-ops.io> wrote: > > Ivan et. al., > > I talked with Gregg yesterday about the implementation reports. In the end, we feel that the most practical course is to just use the report format supplied by the Web Platform Tests. This requires that we get some skeletal directories in place. I am going to talk to the relevant parties about that right now. > > You can see an example at http://w3c.github.io/test-results/battery-status/all.html <http://w3c.github.io/test-results/battery-status/all.html> > > For us, I expect the data will be in annotation-model/all.html, annotation-protocol/all.html, and annotation-vocab/all.html > > Basically, the way this works is that as people run their tests, they update one or more JSON files in the relevant directory with their test results. These are then automagically pulled into the report. > > While these reports are not quite what I wanted, they 1) just work, 2) come for free from using WPT, 3) are going to be familiar to the powers that be. That works for me. Whatever is simple(r) to produce for you guys; that is my only concerns Ivan P.S., actually, the powers that have become familiar with Gregg's report format, too; I am not sure how many groups' results were reported that way. Four? (RDFa, JSON-LD and maybe other RDF, CSVW…) > > If there any questions, let me know. > > -- > Shane McCarron > Projects Manager, Spec-Ops ---- Ivan Herman, W3C Digital Publishing Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Saturday, 11 June 2016 12:47:53 UTC