- From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
- Date: Wed, 10 Jun 2015 07:45:09 -0700
- To: RDF Data Shapes Working Group <public-data-shapes-wg@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Here is what I think is the minimum that a formal definition oF SHACL needs. References to document sections are to places where relevant information is available, sometimes only in an informal manner. Where the information is incomplete or incorrect, I have so noted. Syntax - - what makes a valid RDF-encoded shape - not in document? UML diagram??? - - what makes a valid RDF-encoded constraint - not in document - - what makes a valid RDF-encoded scope - not in document? UML diagram??? - - what makes a valid RDF-encoded template - 8, maybe incomplete - - what makes a valid RDF-encoded function - 11, maybe incomplete - - what makes a valid SHACL RDF graph - not in document Templates - - what makes a valid RDF-encoded template instance of a template - not in document - - what templates make the built-in constraints - Appendix B Semantics - - how is SHACL invoked - 10.2, 10.3, 10.4, 10.5 - - how are shapes validated - 10.1, 12 - incomplete - - how is an RDF-encoded template instance translated into SPARQL - 12.2, incomplete, partly incorrect - - how is an RDF-encoded function instance translated into SPARQL - 12.3, incomplete - - how is an RDF-encoded shape translated into SPARQL - not in document - - how are violations determined - 3, 4, 5, and 12, incorrect - - how are violations reported - 12.1.2, partly incorrect - - how are violations turned into human readable output - 12.1.2, incomplete This completes my ACTION-27. peter -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVeE10AAoJECjN6+QThfjz2FYH/inTKSvfgrqgWBulPj6q0VUZ sDF+ZxQ/U372fkOeS0af+ymbv1HIRGdY/bN62pOHFrEMO9OctgE1st2dgTeyVhI4 pdkQ75DQBXlr2ehsYdcUS4wa1uVUIcxhEgRZNELxJDb2aGMvpYqp5BbheZBmGrT/ Krh0SKEMmlCFAPmtqJWkt4SzL1Vo9CXXbBcKclCEu3oR/7F1QTRudzXijUUGYCgD g3wW8Xs5toE2FAQsPRddR26zqvchdW3HofsgqPN/UVE9TG7zXgRFDm+wotHglyW/ doQ8Nqiz2oClsONoTj02OqZFZMujOTHseaDum6Q5yp6R7zcBWh+3JZarQwN5XVo= =H4Rt -----END PGP SIGNATURE-----
Received on Wednesday, 10 June 2015 14:45:40 UTC