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

Re: [SKOS] ISSUE-33 "SimpleExtension" proposal (was RE: [SKOS] "Lexicalization" or "term"?)

From: Guus Schreiber <schreiber@cs.vu.nl>
Date: Sun, 17 Jun 2007 12:55:10 +0200
Message-ID: <4675130E.9070806@cs.vu.nl>
To: "Miles, AJ \(Alistair\)" <A.J.Miles@rl.ac.uk>
CC: Antoine Isaac <aisaac@few.vu.nl>, SWD WG <public-swd-wg@w3.org>, public-esw-thes@w3.org



Miles, AJ (Alistair) wrote:
> Hi Antoine,
> 
> I just took a look at the latest revision of the "SimpleExtension" proposal [1] for ISSUE-33. Interesting :)
> 
> Under this proposal, is there a bijection [2] between the extension of skos:Label and the set of RDF plain literals?
> 
> In other words, is there only one skos:Label for every plain literal, and vice versa?
> 
> Or, under this proposal, is there only a surjection [3] between the extension of skos:Label and the set of RDF plain literals
> 
> In other words, is there only one plain literal for every skos:Label, but one or more skos:Label for every plain literal?
> 
> This is absolutely crucial to exploring the consequences of the proposal. It is crucial because it bears on the conditions under which it makes practical and logical sense to assert the identity of two individuals of type skos:Label. This is the fundamental question that all proposals following the "terms-as-classes" pattern must address.

Good point, should have made this clear. As skos:Label is just a support class for the literal, my initial reaction was that a liretal can only have one skos:Label attached to it  But this will not work in practice, as literals may be used as terms in several vocabularies. The only constraint that makes sense, I think, is to require that literals only have one lLabel within one particular ConceptScheme. Would this work?

Guus

> 
> Cheers,
> 
> Al.
> 
> [2] <http://en.wikipedia.org/wiki/Bijection>
> [3] <http://en.wikipedia.org/wiki/Surjective_function>
> 
> 
> 
> This proposal makes me happy, not because I support it necessarily, but because , because there is enough information there to understand the intended semantics There are two fundamental questions this propsal
> 
> 
> It seems to me that [1] intendes the skos:Label class is equivalent to the class of RDF
> 
> [1] <http://www.w3.org/2006/07/SWD/wiki/SkosDesign/RelationshipsBetweenLabels/ProposalThree?action=recall&rev=14>
> 
> --
> Alistair Miles
> Research Associate
> Science and Technology Facilities Council
> Rutherford Appleton Laboratory
> Harwell Science and Innovation Campus
> Didcot
> Oxfordshire OX11 0QX
> United Kingdom
> Web: http://purl.org/net/aliman
> Email: a.j.miles@rl.ac.uk
> Tel: +44 (0)1235 445440  
> 
>> -----Original Message-----
>> From: public-swd-wg-request@w3.org 
>> [mailto:public-swd-wg-request@w3.org] On Behalf Of Antoine Isaac
>> Sent: 08 June 2007 12:47
>> To: Thomas Baker
>> Cc: Daniel Rubin; SWD WG
>> Subject: Re: [SKOS] "Lexicalization" or "term"?
>>
>>
>> Hi Tom,
>>> On Fri, Jun 08, 2007 at 10:36:23AM +0200, Antoine Isaac wrote:
>>>   
>>>> To add to this mutual clarification process: as said, 
>> nothing like a 
>>>> "term" appears now in current SKOS, it only popped up in the 
>>>> discussion because of loosely wording used in the proposals for 
>>>> solving the RelationshipBetweenLabels issue. [and of 
>> course I share a 
>>>> great deal of responsability for that :-(] Hence my will to 
>>>> replace"term"by "Lexicalization" (or by anything more 
>> neutral than "term") in Guus'
>>>> proposal
>>>>
>> (http://www.w3.org/2006/07/SWD/wiki/SkosDesign/RelationshipsBetweenLa
>>>> bels/ProposalThree)
>>>>     
>>> One problem is that "lexicalization" is not defined in the average 
>>> desk dictionary.
>> How about http://www.m-w.com/dictionary/lexicalization ? Is 
>> it too unclear, or too process-oriented?
>>>  If I were to guess at it's
>>> meaning, out of this context, I'd have said "the process of 
>>> lexicalizing", and I see that some linguists use lexicalization to 
>>> refer to the process of making a word for a concept, but these 
>>> meanings are misleading for what we want to say here.
>>>
>>> Given a choice between "lexicalization" and "term", I'd 
>> still go for 
>>> "term" but agree we should try to find something more neutral.
>>>   
>> Clearly "term" should be avoided. "LexicalToken"? 
>> "LabelResource"? I am ready to accept anything ;-)
>>
>> Antoine
>>
>>
> 

-- 
Vrije Universiteit Amsterdam, Computer Science
De Boelelaan 1081a, 1081 HV Amsterdam, The Netherlands
T: +31 20 598 7739/7718; F: +31 84 712 1446 
Home page: http://www.cs.vu.nl/~guus/
Received on Sunday, 17 June 2007 10:55:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:38:58 GMT