Re: symbolic labels

I meant to refer to the "symbol" properties, naturally:

   What does the "prefSymbol" name imply? It is important that these term
   share meaning.... Any argument against "symbol" is an argument against
   "prefSymbol". And vice versa - any argument *for* "prefSymbol" is an
   argument for "symbol".

/Mikael

Mikael Nilsson wrote:
> 
> 
> Mark van Assem wrote:
> 
>> Hi,
>>
>> Ah, you're right, there is a need for a superprop for extensions.
>>
>> Note that giving it the name "symbol" implies (to me) a more general
>> semantics than "symbolicLabel". In the former any symbol can be
>> attached to a concept, in the latter they should be some kind of label
>> for the concept. E.g. the former allows an arrow to be a symbol for
>> the concept "rock" (e.g. as an icon in an application), while the
>> latter only allows this if there is a specific "symbol vocabulary"
>> that uses an arrow as a symbol for "rock".
> 
> 
> What does the "prefLabel" name imply? It is important that these term 
> share meaning.... Any argument against "label" is an argument against 
> "prefLabel". And vice versa - any argument *for* "prefLabel" is an 
> argument for "label".
> 
> :-)
> 
> /Mikael
> 
>>
>> Your suggestion is more general so probably to be preferred above
>> symbolicLabel?
>>
>> Mark.
>>
>>> I have no specific use case for this, but I would like SKOS Core to 
>>> follow the design pattern that all property families that share 
>>> common semantics descend from a single super-property.  I think it is 
>>> important to capture common semantics, and is important from the 
>>> point of view of extensions, where each property is in principle an 
>>> extension (refinement) point.
>>>
>>> So 'skos:symbol' (I propose that name, instead of the longer 
>>> 'skos:symbolicLabel') would be the symbol equivalent to rdfs:label.
>>>
>>> Cheers,
>>>
>>> Al.
>>>
>>>
>>>> -----Original Message-----
>>>> From: Mark van Assem [mailto:mark@cs.vu.nl]
>>>> Sent: 01 July 2005 13:51
>>>> To: Miles, AJ (Alistair)
>>>> Cc: public-esw-thes@w3.org
>>>> Subject: Re: symbolic labels
>>>>
>>>>
>>>> Hi,
>>>>
>>>> In general always a good idea to introduce a superprop, but what's 
>>>> the use case here? Will implementers be wanting to show a 
>>>> skos:symbolicLabel instead of just checking whether there is a 
>>>> prefSymbol available?
>>>>
>>>> Mark.
>>>>
>>>> Miles, AJ (Alistair) wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Following the design pattern for lexical labels, i.e. a 
>>>>
>>>>
>>>>
>>>> property hierarchy with a single root, e.g. ...
>>>>
>>>>> rdfs:label
>>>>> |
>>>>> +-- skos:prefLabel
>>>>> |
>>>>> +-- skos:altLabel
>>>>> |
>>>>> +-- skos:hiddenLabel
>>>>>
>>>>> ... oughtn't we have a single property at the root of the 
>>>>
>>>>
>>>>
>>>> symbolic labelling properties, e.g. ...
>>>>
>>>>> skos:symbolicLabel
>>>>> |
>>>>> +-- skos:prefSymbol
>>>>> |
>>>>> +-- skos:altSymbol
>>>>>
>>>>> ... ?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Al.
>>>>>
>>>>> ---
>>>>> Alistair Miles
>>>>> Research Associate
>>>>> CCLRC - Rutherford Appleton Laboratory
>>>>> Building R1 Room 1.60
>>>>> Fermi Avenue
>>>>> Chilton
>>>>> Didcot
>>>>> Oxfordshire OX11 0QX
>>>>> United Kingdom
>>>>> Email:        a.j.miles@rl.ac.uk
>>>>> Tel: +44 (0)1235 445440
>>>>>
>>>>>
>>>>
>>>> -- 
>>>>  Mark F.J. van Assem - Vrije Universiteit Amsterdam
>>>>        mark@cs.vu.nl - http://www.cs.vu.nl/~mark
>>>>
>>>
>>>
>>
> 

-- 
Plus ça change, plus c'est la même chose