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

Hi!

1. The SHACLC mime type is at
https://w3c.github.io/shacl/shacl-compact-syntax/#iana-considerations,
submitted to IANA

2. Let's pick some URLs for the shacl and shacl-validation-report profiles.
We don't need to wait for content profiles to become mainstream.
  It makes sense for those to be related to some of: the spec URL, the NS
URL, or the JSONLD context (I couldn't find a URL for that).
  Reading https://www.w3.org/TR/dx-prof-conneg/#profiles-in-prof, I think
the URLs should be as below.

   - https://www.w3.org/TR/shacl/
   - https://www.w3.org/TR/shacl/#validation-report

3. We should also describe these profile URLs as RDF individuals
(dct:Standard) in the sh: ontology

4. Havard, in addition to application/shacl-validation-report+n-quads
could you please add the option to return
text/shacl-validation-report+turtle.
It's a lot more convenient to read, and IMHO doesn't preclude streaming.
(BTW, do we ever have Graph components in the validation report triples?)
5. I'm not sure how to do conneg between the above two formats.

   - If the validation report is the result of exception to a SPARQL
   UPDATE, you could use the Accept header of the request
   - IMHO in addition to the above two types, you should also handle plain
   application/n-quads and text/turtle
   - But if the transaction is initiated in some other way (not SPARQL),
   then it should perhaps be some Java param somewhere.

Cheers!