Issue 419: Add shaclc snippets

[jeswr]

Editorial change to add SHACL-C snippets to the core spec document

Closes #419

• See this document rendered online here

[bergos]

Updating the specification via JavaScript code generates several changes that aren't related to the shaclc snippets. I think these changes should be in a separate commit, separate from the shaclc changes. I don't see any problem with the changes, but others should also review them.

The code and the generated snippets look good.

[jeswr]

Updating the specification via JavaScript code generates several changes that aren't related to the shaclc snippets. I think these changes should be in a separate commit

These are now done in cf8a8ea including manual adding of <thead> as pointed out by @afs in #421 (comment)

[jeswr]

@bergos could you please update your review when you get the chance. @TallTed you may wish to review cf8a8ea, noting that these are largely automated changes to the HTML.

[TallTed]

FWIW, everything I see in cf8a8ea looks good.

[YoucTagh]

I am adding my review late, but there are 28 Shapes graph boxes with Turtle and JSON-LD only, with no SHACL-C. Is this intentional?

[jeswr]

I am adding my review late, but there are 28 Shapes graph boxes with Turtle and JSON-LD only, with no SHACL-C. Is this intentional?

Those graph boxes for which there is no SHACL-C are ones for which SHACL-C is not currently expressive enough to describe. The SHACL-C was autogenerated, and autogeneration was skipped if the serializer detected features it could not handle.