shapes-ISSUE-27 (extensions-in-highlevel): Can extension constraints be used in the high-level language? [SHACL Spec] from RDF Data Shapes Working Group Issue Tracker on 2015-03-28 (public-data-shapes-wg@w3.org from March 2015)

From: RDF Data Shapes Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Sat, 28 Mar 2015 20:18:47 +0000
To: public-data-shapes-wg@w3.org
Message-Id: <E1YbxBv-0008ma-Fu@maia.w3.org>

shapes-ISSUE-27 (extensions-in-highlevel): Can extension constraints be used in the high-level language? [SHACL Spec]

http://www.w3.org/2014/data-shapes/track/issues/27

Raised by: Richard Cyganiak
On product: SHACL Spec

It looks like SHACL will be split into two parts:

1) A high-level “Core/Lite” language consisting of things like cardinality constraints, datatype constraints, conjunctions and disjunctions
2) An extension mechanism that relies on embedded expressions in a more expressive language

Do constraints defined using 2) become part of the high-level language, that is, can they be used in nested expressions like conjunctions and disjunctions? Or do they stand “outside” the high-level language and are directly associated with classes/individuals/etc?

Received on Saturday, 28 March 2015 20:18:48 UTC