Re: Ditching the Constraint Violation Vocabulary

On 3/31/2015 17:39, Richard Cyganiak wrote:
>
> The current draft doesn’t properly support multiple sh:message values; you can only return one from SPARQL-based constraints.

For the record, it does, via multiple values of sh:message in multiple 
languages at the constraint

http://w3c.github.io/data-shapes/shacl/#sparql-constraints-variables

(Having said this we could of course narrow down the engine so that only 
one value is computed, for a requested language).

Likewise most other result variables can alternatively be specified via 
such properties (sh:path etc). Since the properties are already there, 
using them also for the output structure is just a trivial further step.

Holger

Received on Tuesday, 31 March 2015 08:25:16 UTC