- From: Andy Seaborne <andy@apache.org>
- Date: Fri, 7 Jan 2022 14:25:31 +0000
- To: public-shacl@w3.org
On 07/01/2022 07:03, Håvard Ottestad wrote: > Hi, > > If there are a lot of targets then it would be very costly memory wise > to distinct them before performing validation. True - something an implementation may need to deviate from the detail of the spec. There are always points where "ideal" and a certain usage interact. You only need to make the target terms that fail validation a set. The ones conform are invisible to the report. And a Bloom filter may help. Andy > > Cheers, > Håvard M. Ottestad > >> On 7 Jan 2022, at 07:11, Vladimir Alexiev >> <vladimir.alexiev@ontotext.com> wrote: >> >> >> > implementation question, rather than a standards question. >> >> The number of Validation Results will be different (unless targets are >> distinct, there will be duplicate results). >> Even if one stored Validation Results in a repo, they would not be >> deduplicated since it's not likely Results can use deterministic URLs >> (not blank nodes or UUID URNs). >> >> The impact on performance will be a linear slowdown. >> If that shape causes a lot of other shapes to be invoked, that can be >> very significant. >> >> > Holger: I believe this is following the intention of the spec. >> >> Agreed. But still, the spec should mention DISTINCT. >> I'll post this to https://github.com/w3c/data-shapes/issues >> <https://github.com/w3c/data-shapes/issues> "SHACL Errata", as per >> https://github.com/w3c/data-shapes/issues/103 >> <https://github.com/w3c/data-shapes/issues/103> >> >> Cheers!
Received on Friday, 7 January 2022 14:25:45 UTC