W3C home > Mailing lists > Public > public-esw-thes@w3.org > January 2016

Re: S36 implementation details

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Fri, 15 Jan 2016 16:20:30 +0100
Message-ID: <56990E3E.4090900@few.vu.nl>
To: <public-esw-thes@w3.org>
Dear Frederik,

It's mostly a timing issue.
At the time SKOS was made OWL2 property chains were still a fresh notion. We were aware of their development but it seemed a bit premature to base the SKOS standard on them. Hence we didn't consider using them.
As a matter of fact the official OWL specification of SKOS is still an OWL1 one.

Best,

Antoine

On 1/15/16 3:53 PM, Frederik Baumgardt wrote:
> Hi all,
>
> I’m wondering about this detail in SKOS whereby elements in a memberList of an OrderedCollection are also members of the same OC. It appears in this comment <https://github.com/AKSW/Xturtle/blob/develop/vocabularies/xturtle.skos/skos.ttl#L180> and in S36 <https://www.w3.org/TR/skos-reference/#collections> of the reference document, but I’m not able to find its implementation.
>
> On a sidenote, I am inclined to think of it as an owl:propertyChainAxiom, but that would require a property linking a list with its members without the rdf:List/rdf:rest{}/rdf:first indirection. Which has me wondering if a transitive property in place of rdf:rest positioned inside an owl:propertyChainAxiom — like so: ex:member owl:propertyChainAxiom (ex:rest ref:first) would achieve the desired effect.
>
> Sorry if I’m being ignorant of important skos/owl/rdf spec-details here. New to the field and still learning about the finer distinctions.
>
> Best,
> Frederik Baumgardt
>
> --
> Sr. Developer @ Perseids Project
> Perseus Digital Library
> Tufts University
Received on Friday, 15 January 2016 15:21:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:46:48 UTC