ISSUE-3 how to specify the shape information and the data information

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I added a section to
https://www.w3.org/2014/data-shapes/wiki/ISSUE-3:_Graph_Shape_Association
providing two ways to invoke a SHACL engine.

In the first way there are two arguments, one for the shapes and one for the
data.  This is the no-linking method and is the most basic invoking mechanism.

In the other way there is one argument.  This argument can either contain
the data or point to some other place to get the data.  This argument can
either contain all the shape stuff or point to a place where there is more
shape stuff.


Under this proposal a service could return an RDF graph that contains
something like this:
  The start node is X
  The start shape is S
  Look at <https:...> for the shape definitions and other SHACL stuff
  ... data ... data .. data
To verify this claim a SHACL engine would run the shapes starting at the
start node and the start shape against all the data in this graph.


A service could also return a small RDF graph that contains something like thi
s:
  Look at <https:...> for the scoped shapes
  Look at <http:...> for the data
To verify this claim a SHACL engine would check that the data satisfies the
scoped shapes.

Note that in the first service example that whatever encoding is used to
specify the start node, start shape, and pointer to the other SHACL stuff
ends up as part of the data that is being checked whereas in the second
service example no SHACL-related informmation need show up in the data being
checked.


peter





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVXiaMAAoJECjN6+QThfjzyKkH/2bi5du4Xls5be9aNSAw+ZLP
ZxlJBpYuWT7S9PajeB2P63Uqh03CGMeWsViOCNjfjAZldDmGGyIu+UJsQDmvAf8w
SCkQPZFTwOfDnphlSGkHz1tgJSmpo9gboXTJoc39sJD1BwOSHC9naHSZGCLCvVWC
vv7cffvnsmarJq7evknY4IiGgeYFdlToCyy1ZjtYE9nDkcYxRKJ7Fh6rABdsMZvO
/QOFRROArbIN6yB8zU6/P6/Ov9Yvg0ruGbpNC/e49VJzWRWETvr5IEu/n1IIXHsR
Y+Z5P2wKXW6z+CfrQJ5KHTh+Lw2Tfx8kbKZ2Yyr0HMvfsDDc8XXqVgqkbt/y8gg=
=Spfu
-----END PGP SIGNATURE-----

Received on Thursday, 21 May 2015 18:40:44 UTC