- From: Arnaud Le Hors <lehors@us.ibm.com>
- Date: Mon, 12 Sep 2016 10:55:48 +0200
- To: Holger Knublauch <holger@topquadrant.com>
- Cc: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org>
Received on Monday, 12 September 2016 08:56:25 UTC
I think that's reasonable. -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM Cloud From: Holger Knublauch <holger@topquadrant.com> To: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org> Date: 09/08/2016 04:53 AM Subject: SHACL Full We have different terms to speak about the non-Core features of SHACL. Among others, they are labeled "advanced features" or "extension mechanisms". Neither of them are sufficient to cover what these features really are about. We do have the established term "SHACL Core", so I suggest we call the language consisting of SHACL Core plus these other features simply "SHACL Full". This is similar to how OWL 1 is defined. I have made corresponding edits to the spec, including definitions in the Terminology section. Please let me know if anyone has concerns with this approach. Thanks, Holger
Received on Monday, 12 September 2016 08:56:25 UTC