- From: Houghton,Andrew <houghtoa@oclc.org>
- Date: Mon, 18 Oct 2004 10:29:03 -0400
- To: public-esw-thes@w3.org
> -----Original Message----- > From: Miles, AJ (Alistair) [mailto:A.J.Miles@rl.ac.uk] > Sent: 18 October, 2004 10:11 > Subject: RE: search labels > > > Hi, > > I'm fine with 'hiddenLabel' for this. > > However there is another issue to contend with: what should > 'skos:hiddenLabel' be a sub-property of? > > I originally thought to do: > > [property hierarchy] > rdfs:label > skos:prefLabel > skos:altLabel > skos:hiddenLabel > > ... with the implicit assumption that terms given by > skos:prefLabel and skos:altLabel (or any sub-property > thereof) are for display, while those given by > skos:hiddenLabel (or any sub-property thereof) are not. > > However, Leonard suggested below that we make > 'skos:hiddenLabel' a sub-prop of 'skos:altLabel' ... which > would be at odds with the assumption above. > I think there is a case for both situations. It is possible that you want terms to be "hidden" but you don't want them described as alternate labels in your thesaurus. For example, incorporating terms from other thesaurus that you want to lead someone to the appropriate term in your thesaurus. However, the terms are not authorized in your thesaurus as alternate labels for policy reasons. You are using these terms for searching and indexing purposes. This is how, I think, Miles viewed it. In the other case, you may want to have alternate labels that are authorized, but don't wish those to show up in the display of the thesaurus. This might suggest an alternate property hierarchy rdfs:label skos:displayLabel skos:prefLabel skos:altLabel skos:hiddenLabel skos:*Label or rdfs:label skos:publicLabel skos:prefLabel skos:altLabel skos:privateLabel skos:*Label Andy.
Received on Monday, 18 October 2004 14:29:26 UTC