- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Wed, 22 Jun 2016 18:03:45 -0400
- To: public-data-shapes-wg@w3.org
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? -- -ericP office: +1.617.599.3509 mobile: +33.6.80.80.35.59 (eric@w3.org) Feel free to forward this message to any list for any purpose other than email address distribution. There are subtle nuances encoded in font variation and clever layout which can only be seen by printing this message on high-clay paper.
Received on Wednesday, 22 June 2016 22:03:49 UTC