W3C home > Mailing lists > Public > public-esw-thes@w3.org > June 2007

Re: [SKOS] ISSUE-31 BasicLexicalLabelSemantics proposed resolution

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Tue, 26 Jun 2007 22:42:10 +0200
Message-ID: <46817A22.8030503@few.vu.nl>
To: "Miles, AJ \(Alistair\)" <A.J.Miles@rl.ac.uk>
CC: SWD WG <public-swd-wg@w3.org>, public-esw-thes@w3.org

> Hi all,
> I'd like to propose the following section of the SKOS Semantics as a resolution for [ISSUE-31]:
> [1] <http://www.w3.org/2006/07/SWD/wiki/SKOS/Semantics/Labelling?action=recall&rev=5>
> This proposal deals with the intuitive semantics of "preferred", "alternative" and "hidden" at the syntactic level, which avoids complicated semantics conditions and allows for error-tolerant strategies to be defined.

Regarding the content of these conditions I agree, even though I find it quite difficult to think about labelling properties trying to abstract from any concept scheme-related consideration. 
I may have however some doubts about the first:

> An application MAY ignore any triple in an RDF graph where the 
> predicate is either skos:prefLabel, skos:altLabel or skos:hiddenLabel 
> and the object is NOT a plain literal.

If I understand well, this condition does not discourage strongly the 
use of resources as object of labelling properties. In this case, why 
are we trying to find extra names for the term-as-class proposal [e.g. 
1] to ISSUE-26: RelationshipsBetweenLabels [2], on the (not single, yet 
important) basis that it would be confusing to have a property having 
both resources and literals as possible objects?


PS: most of my comments about labelling issues [3] actually fall into 
[ISSUE-32] not [ISSUE-31]. I'm impatient :-)

[2] http://www.w3.org/2006/07/SWD/track/issues/26
[3] http://lists.w3.org/Archives/Public/public-swd-wg/2007Mar/0009.html
[ISSUE-31] <http://www.w3.org/2006/07/SWD/track/issues/31>
[ISSUE-32] <http://www.w3.org/2006/07/SWD/track/issues/32>
Received on Tuesday, 26 June 2007 20:42:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:45:40 UTC