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

Re: Transitive?

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Mon, 16 May 2016 08:57:08 -0700
To: public-data-shapes-wg@w3.org
Message-ID: <5739EDD4.70807@kcoyle.net>
SHACL is defining "SHACL subClassOf" to be equivalent to SPARQL's 
rdfs:subClassOf*. This is more than saying it is "transitive" -- it is 
saying "the operation here is to 'transit' this path." The 
rdfs:subClassOf allows one to follow the path but does not dictate that 
the path be followed, as rdfs:subClassOf* does.

1) I'm not convinced that "All resources and all their inferred types" 
[1] is the appropriate "default" for SHACL
2) I don't think that the meaning of subClassOf should be overloaded 
with the property path.
3) is there a reason not to use rdfs:subClassOf* ? If so, could a 
similar notation be developed?

kc
[1] https://www.w3.org/TR/sparql11-query/

On 5/16/16 5:10 AM, Holger Knublauch wrote:
> Our recent editorial experiments were to use the terms SHACL instance,
> SHACL type and SHACL subclass. I don't find this very attractive to read
> and it gives room to misinterpretation too, e.g. people could read it as
> if we were using different properties than rdf:type or rdfs:subClassOf.
>
> Looking at the RDFS spec [1], we can read
>
>      "The rdfs:subClassOf property is transitive".
>
> This is exactly the relevant bit of "inferencing" that we are using in
> SHACL too.
>
> So why can't we switch to the terms
>
> - transitive subclass
> - transitive type
> - transitive instance
>
> which should be relatively unambiguous esp given that each usage of
> these terms is now hyperlinked to the terminology section. Furthermore
> transitivity even carries a fairly appropriate meaning:
>
>      https://en.wikipedia.org/wiki/Transitive_relation
>
> Regards,
> Holger
>
> [1] https://www.w3.org/TR/rdf-schema/#ch_subclassof
>
>
>

-- 
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600
Received on Monday, 16 May 2016 15:57:34 UTC

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