W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > May 2016

Re: shapes-ISSUE-159: [Editorial] Eliminate "scope class" from 2.1.n [SHACL Spec]

From: Holger Knublauch <holger@topquadrant.com>
Date: Mon, 2 May 2016 11:49:05 +1000
To: public-data-shapes-wg@w3.org
Message-ID: <b6004dc1-9f2f-a3a8-e8a5-0cefe16c992e@topquadrant.com>
Hi Karen,

yes these are good points. The use of "scope class" here is confusing, 
also due to the overlap with the unrelated sh:scopeClass property. The 
proper term for them would be "scope type", which is also used in 
section 8.2

Please review my edits:

https://github.com/w3c/data-shapes/commit/4f74748b0637eeb5406abfce2797335baad6e33a

On 1/05/2016 10:27, RDF Data Shapes Working Group Issue Tracker wrote:
> shapes-ISSUE-159: [Editorial] Eliminate "scope class" from 2.1.n [SHACL Spec]
>
> http://www.w3.org/2014/data-shapes/track/issues/159
>
> Raised by: Karen Coyle
> On product: SHACL Spec
>
> I would like to clarify 2.1.3 and its subsections by eliminating the phrase "scope class". The current description in the introduction is:
>
> 2.1.3 (sentence 3)
> "SHACL includes four built-in scope classes: sh:PropertyScope... etc."
>
> The pattern for each subsections reads:
>
> 2.1.3.1 Property scopes (sh:propertyScope)
> "The scope class sh:PropertyScope selects all subjects that have at least one value for a given property sh:predicate."
>
> I would suggest that we replace sentence 3 in 2.1.3 with:
> "SHACL includes four subclasses of sh:Scope that define the core scope types:...."
>
> And the pattern first statement for the subsections would be:
>
> "The class sh:PropertyScope is the class of those subjects that have at least one value for a given property sh:predicate."

In the latter case I diverged a bit from your suggestion to the pattern 
"represents the class of scopes of XY". I prefer this because a scope 
does not represent a class of subjects - the term class is already 
overloaded with different meaning IMHO. Scopes "represent" sets of nodes 
in my opinion.

Are these edits addressing your issue?

Thanks
Holger


>
> Reasons: this eliminates the vague phrase "scope class", and also does not ascribe agency to the subclasses (subclasses do not SELECT).
>
>
>
Received on Monday, 2 May 2016 01:49:39 UTC

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