Re: shapes-ISSUE-33 (Simonstey): Shifting section "Shape Selection" to introduction? [SHACL Spec]

Hi Simon,

I have so far not emphasized the aspect of shape selection because it 
was a controversial topic (you certainly remember the Class-vs-Shape 
discussion which is still not completely resolved). In our brief 
collaboration on the primer, Eric was very keen on introducing Shapes 
without relying on either selection mechanism - because the validation 
could also be triggered by custom mappings outside of the RDF data model.

Having said this, the introduction [1] currently has the following 
paragraph:

"One of theoperations 
<http://w3c.github.io/data-shapes/shacl/#operations>that SHACL engines 
should support validates that a given RDF node matches a given shape. 
This operation can be invoked based on any control logic, i.e. 
applications can pick their own mapping between RDF nodes and their 
shapes. SHACL also provides two mapping mechanisms based on the RDF 
triples in the graph being validated. Current proposals for these 
mechanisms include selection based on|sh:nodeShape|and|rdf:type|triples."

So my question is, what is missing to make this clearer? Could you 
propose alternative prose for this aspect?

Thanks
Holger

[1] http://w3c.github.io/data-shapes/shacl/#introduction

On 4/1/2015 19:20, RDF Data Shapes Working Group Issue Tracker wrote:
> shapes-ISSUE-33 (Simonstey): Shifting section "Shape Selection" to introduction? [SHACL Spec]
>
> http://www.w3.org/2014/data-shapes/track/issues/33
>
> Raised by: Simon Steyskal
> On product: SHACL Spec
>
> Information on how to associate shapes with resources/data they constrain is imho very crucial and should be part of the introduction rather than being placed somewhere at the end of the specification.
>
>
>