- From: Holger Knublauch <holger@topquadrant.com>
- Date: Thu, 23 Jun 2016 09:15:23 +1000
- To: public-data-shapes-wg@w3.org
Hi Eric, when a shape is validated as part of a "nested" sh:shape, sh:and, sh:not etc then its declared scope is ignored. Only its sh:filterShapes will be considered. This is one of the reasons why the current spec states that node constraints are validated against each focus node individually, because the set of scope nodes is relatively orthogonal to the shape's current execution context. HTH Holger On 23/06/2016 8:03, Eric Prud'hommeaux wrote: > Is a validation engine expected to always honor sh:scope*? > > Apart from cardinality constraints on subjects of type arcs, validations boil down to various choreographies to invoke sh:hasShape, which effectively validates a node in a graph against a shape in a schema. There are of course an unenumerable number of ways that one may wish to connect nodes to shapes, user interface, posts to LD containers, routine sweeps of data stores, etc. So if one were to invoke a validation and the schema included some conflicting sh:scopeNode or sh:scopeProperty assertions, which would win?
Received on Wednesday, 22 June 2016 23:15:54 UTC