W3C home > Mailing lists > Public > public-swd-wg@w3.org > July 2008

RE: [SKOS] ISSUE-123 Proposed Resolution

From: Houghton,Andrew <houghtoa@oclc.org>
Date: Thu, 31 Jul 2008 07:07:08 -0400
Message-ID: <6548F17059905B48B2A6F28CE3692BAAF59768@OAEXCH4SERVER.oa.oclc.org>
To: <public-swd-wg@w3.org>

I think this proposal solves the issue for large controlled vocabularies that have many top concepts and it is not feasible to specify large numbers of skos:hasTopConcept properties in skos:ConceptScheme.  It seems to me that, with this proposal, you would be able to maintain whether a concept was a top concept in skos:Concept instead and still be able to find them regardless of specifying the top concept aspect in skos:Concept or skos:ConceptScheme.  If I understood this proposal correctly, then I'm in favor of it.

Andy.

> -----Original Message-----
> From: public-swd-wg-request@w3.org [mailto:public-swd-wg-
> request@w3.org] On Behalf Of Alistair Miles
> Sent: Wednesday, July 30, 2008 6:13 AM
> To: public-swd-wg@w3.org
> Subject: [SKOS] ISSUE-123 Proposed Resolution
> 
> 
> We propose the following resolution to [ISSUE-123]:
> 
> PROPOSED: Add a new property skos:topConceptInScheme to the SKOS
> vocabulary.
> Add two new statements to the SKOS data model: skos:topConceptInScheme
> is a
> sub-property of skos:inScheme, and skos:topConceptInScheme is the
> owl:inverseOf skos:hasTopConcept.
> 
> == Rationale ==
> 
> The resolution [1] to [ISSUE-83] includes an entailment which must
> follow
> from the SKOS data model, involving skos:inScheme and
> skos:hasTopConcept.
> 
> However, the resolution [1] does not give the precise logical
> connection
> between skos:inScheme and skos:hasTopConcept, nor does it specify how
> that
> connection should be stated in the SKOS Reference.
> 
> We propose that the entailment in [1] follows because the inverse of
> skos:hasTopConcept is a sub-property of skos:inScheme.
> 
> It has been suggested [2] that this condition be expressed using OWL
> axioms
> involving an anonymous property. However, there are known issues with
> anonymous properties in RDF [3].
> 
> Hence we propose to coin a new URI in the SKOS vocabulary,
> skos:topConceptInScheme, naming a property which is the inverse of
> skos:hasTopConcept and a sub-property of skos:inScheme.
> 
> It has also been suggested that this new property be named
> skos:topConceptOf
> [4]. Naming is always an inherently subjective issue, and it is hard to
> predict how a name will appeal to a wide audience. We propose
> skos:topConceptInScheme to make it intuitively clear that this property
> is a
> refinement (specialisation) of skos:inScheme.
> 
> Kind regards,
> 
> Alistair
> Sean
> 
> [1] http://lists.w3.org/Archives/Public/public-swd-wg/2008May/0068.html
> [2] http://lists.w3.org/Archives/Public/public-swd-wg/2008Jul/0043.html
> [3] http://dx.doi.org/10.1016/j.websem.2005.06.001
> [4] http://www.w3.org/2008/07/29-swd-minutes.html
> [ISSUE-83] http://www.w3.org/2006/07/SWD/track/issues/83
> [ISSUE-123] http://www.w3.org/2006/07/SWD/track/issues/123
> 
> --
> Alistair Miles
> Senior Computing Officer
> Image Bioinformatics Research Group
> Department of Zoology
> The Tinbergen Building
> University of Oxford
> South Parks Road
> Oxford
> OX1 3PS
> United Kingdom
> Web: http://purl.org/net/aliman
> Email: alistair.miles@zoo.ox.ac.uk
> Tel: +44 (0)1865 281993
> 
> 
> 
> 
Received on Thursday, 31 July 2008 11:07:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:31:52 UTC