Re: EARL-based Implementation Reports

Hi Jack,

great to have you on board. You may have seen my requests for help on 
the SHACL-SHACL file. This is our last work item before hopefully moving 
to CR. After that, the bulk of the remaining work is on defining test 
cases with proper coverage. See

     http://w3c.github.io/data-shapes/data-shapes-test-suite/

on the process. Anyone is invited to submit tests at this stage.

Thanks,
Holger


On 31/03/2017 1:29, HODGES Jr, John wrote:
> Hello SHACL WG,
>
> I was just nominated to participate on this group as a Siemens representative. I hope that there is still work to be done, and hope that I can supply some energy to help out. What can I do to help?
>
> Regards,
> Jack Hodges, Ph.D.
>
> Siemens Corporation
> CT RDA NEC WOS-US
> 1936 University, Suite 320
> Berkeley, CA 94704-1074, USA
>
> Mobil: +1 510 289-2982
> mailto:jack.hodges@siemens.com
>
>
> -----Original Message-----
> From: Holger Knublauch [mailto:holger@topquadrant.com]
> Sent: Wednesday, March 29, 2017 11:48 PM
> To: public-data-shapes-wg@w3.org
> Subject: EARL-based Implementation Reports
>
> Hi all,
>
> as discussed in the meeting yesterday, I have defined a more sophisticated process for SHACL implementation reports, based on the EARL ontology. See
>
>       http://w3c.github.io/data-shapes/data-shapes-test-suite/
>
> Among the updates, we now distinguish between *full compliance* and *partial compliance* (for lack of better words), where partial compliance covers only true and false as results - no need to produce the full report.
>
> Furthermore I have added a clause that allows implementers to make the comparison "manually" without going through the graph isomorphism process. Not that I believe there are problems with graph isomorphism, yet I want to lower the bar for people to contribute.
>
> In the latter section of the document I have started a table with specific test results. This currently only includes the TopBraid SHACL API (in Java) but I have prepared a converter script that I can re-run whenever someone submits a new report.
>
> Each test has a status, which is currently "proposed" for each. We can update these values once the tests have been used and found acceptance by more people.
>
> Holger
>
>

Received on Monday, 3 April 2017 02:17:07 UTC