Aw: Re: HTTP requests, databases and how to transmit SHACL validation reports

On Freitag, 05. Juni 2020 um 01:24 Uhr, "Andy Seaborne" <andy@apache.org> wrote:
[...]

> > I don’t see how a SHACL validation violation would produce anything other than a SHACL validation report.
> > 
> > My initial thought was a custom header and standard mime type.
> 
> Vladimir has mentioned profiles:
> 
> https://www.w3.org/TR/dx-prof-conneg/
> 
> which look like a progressive approach.

[Disclaimer: I'm one of the editors of that document]

Yes, this is exactly what profiles are for. What's needed is a URI that identifies a document as a SHACL validation report _irrespective of the media type_ (i.e it's orthogonal to the fact that it's turtle or RDF/XML or any other syntax).

> So I see there are choices to consider before making a de-facto 
> registration (a CG can't formally register a MIME type). 

Can a CG can write a note defining URIs for SHACL profiles? I guess there would be two of them, one for shape definition documents (or rather "this document contains (among other things) shape definitions" and one for SHACL validation reports.

And (this one's for Andy): Is profiles something you could consider adding to Jena?

Best,

Lars

Received on Friday, 5 June 2020 05:41:36 UTC