W3C home > Mailing lists > Public > public-esw-thes@w3.org > September 2005

RE: Use AND type references

From: Lori Finch <lfinch@nal.usda.gov>
Date: Wed, 28 Sep 2005 09:06:46 -0400
Message-ID: <9B16A6EEFA600347BFCDD599E07842900215CA22@moonlight.corp.nal.usda.gov>
To: "Bernard Vatant" <bernard.vatant@mondeca.com>, <public-esw-thes@w3.org>

Bernard,

Hmmm...  since "cut flower production" is a concept, but actually
expressed by two preferred terms, I am glad to see that your new idea is
to have it as a subclass of Concept.  That is logical to me.

Simple is good and it makes sense.

Thanks for your reply!  
Good to hear from Stella too!

Lori


-----Original Message-----
From: Bernard Vatant [mailto:bernard.vatant@mondeca.com] 
Sent: Wednesday, September 28, 2005 8:41 AM
To: Lori Finch; public-esw-thes@w3.org
Subject: RE: Use AND type references


Second thoughts ...

> Note that skos:AND-Concept is not a subclass of skos:Concept,
> since it does not bear prefLabel

Thinking about it, skos:prefLabel is *not* mandatory for skos:Concept.

So maybe we do not even need a particular class for the AND concepts
but simply use blank skos:Concept nodes.

<skos:Concept rdf:ID="foo">
	<skos:AND rdf:parseType="Collection">
		<skos:Concept rdf:about="http://thes.org#cut_flowers"/>
		<skos:Concept
rdf:about="http://thes.org#crop_production"/>
	</skos:AND>
	<skos:altLabel>cut flower production</skos:altLabel>
</skos:Concept>

Maybe too simple to be true :)

> -----Message d'origine-----
> De : public-esw-thes-request@w3.org
> [mailto:public-esw-thes-request@w3.org]De la part de Bernard Vatant
> Envoye : mercredi 28 septembre 2005 13:13
> A : Lori Finch; public-esw-thes@w3.org
> Objet : RE: Use AND type references
>
>
>
> Just some ideas - do not know what Alistair has in store about it.
>
> 1. You do not want to create an explicit descriptor for "cut flowers"
AND "crop
> production".
> 2. But you want anyway to hang the alternative label "cut flower
production" to some
> resource.
> 3. Actually ("cut flowers" AND "crop production") is a concept
>
> What comes to mind is to use "blank concept", defined by some "AND"
operator defined in
> the SKOS namespace.
> Something like
>
> <skos:AND-Concept rdf:ID="foo">
> 	<skos:AND rdf:parseType="Collection">
> 		<skos:Concept rdf:about="http://thes.org#cut_flowers"/>
> 		<skos:Concept
rdf:about="http://thes.org#crop_production"/>
> 	</skos:AND>
> 	<skos:altLabel>cut flower production</skos:altLabel>
> </skos:AND-Concept>
>
> Note that skos:AND-Concept is not a subclass of skos:Concept, since it
does not bear
> prefLabel
>
> How does that fly?
>
> ----------------------------------
> Bernard Vatant
> Mondeca Knowledge Engineering
> bernard.vatant@mondeca.com
> (+33) 0871 488 459
>
> http://www.mondeca.com
> http://universimmedia.blogspot.com
> ----------------------------------
> -----Message d'origine-----
> De : public-esw-thes-request@w3.org
[mailto:public-esw-thes-request@w3.org]De la part de
> Lori Finch
> Envoye : mardi 27 septembre 2005 22:06
> A : public-esw-thes@w3.org
> Objet : Use AND type references
>
>
> Pardon if this was already discussed -
>
> I don't see an accommodation of USE "AND-TYPE" cross references in the
SKOS core nor in
> the SKOS Extensions.
>
> An example of AND-type cross reference in thesauri:
>
> cut flower production USE cut flowers
>                                AND crop production
>
> This indicates to the indexer and searcher to use both preferred
terms, "cut flower" AND
> "crop production" for indexing and retrieval of the concept "cut
flower production".
>
> For NISO Z39.19 thesaurus standard, this is section 8.2.5.
"Cross-references to Elements
> of Compound Terms"
>
> Any previous discussion or suggestions for how these can be handled in
SKOS?
>
> Thanks,
> Lori
>
> Lori J. Finch
> Thesaurus Coordinator
> National Agricultural Library
> 10301 Baltimore Avenue
> Beltsville, MD 20705
> 301-504-6853
> NAL Agricultural Thesaurus: http://agclass.nal.usda.gov/agt/agt.htm
>
>
>
>
Received on Wednesday, 28 September 2005 13:07:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 13:32:06 UTC