W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > March 2015

What was in CONSTRAINTS (was Re: Core or Lite?)

From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
Date: Tue, 24 Mar 2015 11:19:54 -0700
Message-ID: <5511AACA.40902@gmail.com>
To: Richard Cyganiak <richard@cyganiak.de>, Arnaud Le Hors <lehors@us.ibm.com>
CC: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/24/2015 10:30 AM, Richard Cyganiak wrote:
[...]

> We need both; the declarative vocabulary and the expressive fallback.
> Proposals that only address one (like Resource Shapes, and most of the
> descriptions of ShEx, and Peter’s original CONSTRAINTS proposal) are
> insufficient to address the charter.
> 
> Best, Richard

From
https://lists.w3.org/Archives/Public/public-data-shapes-wg/2015Feb/0257.html

Details of the Shapes in CONSTRAINTS

What remains to be determined is just what facilities are provided by
shapes, including whether and how shapes can be related to other shapes.

One option is that global shapes are SPARQL queries, local shapes are SPARQL
queries with a special variable, and that the core operation is running the
query on the RDFS consequences of the RDF dataset.  This is what is done in
SPIN, although SPIN does not have node-based control or inter-shape control.

Another option is that local shapes are ShExC shape expressions and
interpreted as in ShExC over the RDFS consequences of an RDF graph.

A third option is that local shapes are OWL 2 class expressions, global
shapes are OWL 2 axioms, and that the core operation is evaluating OWL
axioms on the Herbrand model of the RDFS consequences of the RDF graph.

Combinations or variations of these options are also possible.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJVEarKAAoJECjN6+QThfjzCc0H/2jvdu6OIto9+ZS5sE8aq8Wo
xVN4MLJAmyId9fIzVr/1s2PXvXV/B5KwJD5zsUGFEnC+1mbWm3v7pvlwBvCaAnYc
Eqk6NPeGK9jeQKOXoXnJD9Y9zfC6aFF3J933jtE3BImr+u/+YQFcyk4erHw8QOaP
rGiQUuEryRcxkOL8DRyDyATGHtgXg4aYP4B6zmlADVU4XAHlhSWgJ3IbjbSnViIY
657pikLciIYLFQmCI6ocrMNjdoA5/2b9dyYJ8r5cHd+whIyOUPQTE74kYJ0tLR00
HW8fMy06HkQbJRazPKtNl31vUidpz5Iy1i3VB2L9863uetoQtLD3Twvs+FSl5ww=
=BPCR
-----END PGP SIGNATURE-----
Received on Tuesday, 24 March 2015 18:20:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:18 UTC