Hi Karen,
On Wed, Oct 07, 2015 at 01:25:33PM -0700, Karen Coyle wrote:
> 1) There are two modes of operation for SHACL -- open shape and
> closed shape (shape being a definition of a graph to be validated).
> The default in SHACL is "open" which means that "extra" triples will
> not be noted or treated as errors. "Closed" can be interpreted to
> mean: "these triples and only these triples." I wanted to create
> tests that demonstrate how these intereact with other validation
> rules -- mainly because I think this will be useful for training.
So that I understand: Is the distinction between "open shape" and
"closed shape" meant to apply at the level of individual SHACL
expressions, or to entire sets of SHACL expressions? Is the choice made
entirely by the data consumer, or is "open/closed" encoded in the
individual SHACL expression? Apologies if this has already been covered
here.
> 3) I've only thought about very very simple SHACL cases; even though
> I don't know how to express more complex cases in SHACL
What is the current level of interest in the Data Shapes WG in providing
a language that can easily be used for the simplest and most common use
cases? Should we be worried that the WG is moving towards a
specification that is unhelpfully over-engineered from the perspective
of, say, cultural heritage requirements? I'm thinking that complexity
is all and good -- unless it actually gets in the way.
Tom
--
Tom Baker <[log in to unmask]>
|