- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 9 Feb 2004 09:58:53 -0500 (EST)
- To: "Miles, AJ (Alistair) " <A.J.Miles@rl.ac.uk>
- Cc: "'public-esw-thes@w3.org'" <public-esw-thes@w3.org>
I say this is a good solution. If you have something with soks:preferredLabels you can refer to the concept by either label, which is probably useful in lots of cases - hence the use case for alternative labels. If you havea thesaurus where two concepts have the same preferredLabel, you need to be more specific in order to get to a single concept. Leaving this open makes merging thesauri easier - you have a valid one, even if you don't instantly correct all cases of using the same label for two concepts. Which means you can develop organically. But the cost is that sometimes you will have to choose what concept you get, from a fuller description (other labels, looking at the examples / definitions). So it's normally helpful to avoid this situation... cheers Chaals On Mon, 9 Feb 2004, Miles, AJ (Alistair) wrote: >So there's three options for soks:prefLabel. > >1. soks:prefLabel should be used so that it uniquely identifies a concept >globally (inverse functional). > >2. soks:prefLabel should be used so that it uniquely identifies a concept >within a conceptual scheme (in effect inverse functional within a given >scope). > >3. soks:prefLabel doesn't uniquely identify anything at any level. > >(1) is obviously impractical. (2) could be useful. (3) is most flexible. > >Personally, I say that we write the support documentation to strongly >recommend users implement their thesauri in SKOS adhering to (2). This then >gives them the option of working with terms only, and >reference-by-description, if they want to. But obviously there is nothing >to stop users breaking (2) and doing whatever they like. The only >consequence is, they lose the ability to have people reference their >concepts via the soks:prefLabel property. > >Chaals: what do you say to all that?
Received on Monday, 9 February 2004 09:59:07 UTC