SHACL Overview, what's new

[nicholascar]

• will satisfy the requirement to have information on what's new for Core & SPARQL Horizontal Review
• cribbed from LinkedIn and extended

Rendered at https://raw.githack.com/w3c/data-shapes/whats-new/shacl12-overview/index.html

Expected updates from Nick:

• ordering of table
• updating links to specs as they become real

[HolgerKnublauch]

SHACL 1.1 was never published and was ever only in draft stage. If you want to refer to the old documents, it should be 1.0 (Core and SPARQL) for sure, but SHACL-AF could be referred to as 1.1.

Under what's new, I suggest to add "Misc New Constraint Components": sh:singleLine, sh:memberShape, sh:minListLength, sh:maxListLength, sh:uniqueMembers.

[nicholascar]

Oh yes, I was sort of trialing out SHACL 1.1 instead of SHACL 1.0. The thinking being that SHACL was published without a version number but based on RDF 1.1. So if we are aligning current SHACL to RDF 1.2, we should retcon all previous SHACL docs to 1.1.

Obviously this thought wasn't what we originally discussed, but how does it strike you as a logic?

[HolgerKnublauch]

The original https://www.w3.org/TR/shacl/ doesn't have any version number, so couldn't we just call them "Previous SHACL specifications", without any specific version number?

[nicholascar]

The original https://www.w3.org/TR/shacl/ doesn't have any version number, so couldn't we just call them "Previous SHACL specifications", without any specific version number?

Yes, we can do that. I'll apply that label across the board via updates to this PR so we are consistent.

[TallTed]

Grammar, punctuation, US English, etc.

Addressed all issues, just testing the review process

[TallTed]

Note that you can use "add to batch" to make a single commit from multiple change requests. "Squash and merge" can also help to keep the commit history cleaner, while preserving contribution records.