Re: more sloppiness in the SHACL document

This fixes one problem but introduces another.

There can be more than one focus node in play at any given time.  (Yes, this
is itself quite sloppy, but the new wording has brought temporal issues into
play.)   There might be more than one shape or constraint currently in play
for any of these focus nodes.

The part of the document on validation reports has quite a few similar issues.
 Aside from those that I have already pointed out there is the issue that
various validation results are supposed to be temporary but the value of
sh:result MUST include them all.

Peter F. Patel-Schneider
Nuance Communications


On 12/05/2016 05:35 PM, Holger Knublauch wrote:
> I have rewritten that section to implement the convention that constraints and
> shapes "are" nodes (as you correctly point out) and to no longer exclude
> bnodes (which was a mistake):
> 
> https://github.com/w3c/data-shapes/commit/5b6ef796f453b3a9578442e901099fc5c0565eaf
> 
> 
> Please let me know if this does not address your issue.
> 
> Thanks,
> Holger
> 
> 
> On 5/12/2016 6:15, Peter F. Patel-Schneider wrote:
>> "Validation results may link to the IRI of the constraint that has caused the
>> result, specified via the property sh:sourceConstraint, and at the IRI of the
>> shape that has declared the constraint, via sh:sourceShape."
>>
>> However, shapes and constraints don't have IRIs and many shapes and
>> constraints aren't IRIs.
>>
>> Aside from that, the sentence has major semantic issues, e.g.,
>> sh:sourceConstraint doesn't specify a linking.
>>
>> Peter F. Patel-Schneider
>> Nuance Communications
>>
> 
>

Received on Tuesday, 6 December 2016 02:06:40 UTC