W3C home > Mailing lists > Public > public-esw-thes@w3.org > February 2009

Re: broader and broaderMatch

From: Alistair Miles <alistair.miles@zoo.ox.ac.uk>
Date: Mon, 2 Feb 2009 09:23:23 +0000
To: Christophe Dupriez <christophe.dupriez@destin.be>
Cc: SWD Working Group <public-swd-wg@w3.org>, "public-esw-thes@w3.org" <public-esw-thes@w3.org>
Message-ID: <20090202092323.GC8750@skiathos>

Hi Christophe,

Section 10.6.1 of the SKOS Reference current editors' draft [1]
states:

"By convention, the SKOS mapping properties are only used to link
concepts in different concept schemes. [...] The mapping properties
skos:broadMatch, skos:narrowMatch and skos:relatedMatch are provided
as a convenience, for situations where the provenance of data is
known, and it is useful to be able to tell "at a glance" the
difference between internal links within a concept scheme and mapping
links between concept schemes."

So skos:broadMatch is intended for the special case where concepts
from different schemes are being mapped. I expect that tools for
translating information retrieval queries using one KOS into queries
using another, or for translating metadata statements from one KOS to
another, will make use of these special mapping properties to drive
these transformations.

The properties skos:broader, skos:narrower and skos:related establish
the basic expectations for broader/narrower (hierarchical) and related
(associative) links. For example, [S27] establishes that
broader/narrower links are disjoint with associative (related) links.

The mapping properties skos:broadMatch, skos:narrowMatch and
skos:relatedMatch extend (refine) the properties skos:broader,
skos:narrower and skos:related [S41]. That means they also effectively
"inherit" these basic expectations. I.e. by virtue of [S27] and [S41],
broader/narrower mapping links are disjoint with associative mapping
links.

Can you describe your practical development issues in more detail?

Many thanks,

Alistair

[1] http://www.w3.org/2006/07/SWD/SKOS/reference/20081001/#mapping
[S27] http://www.w3.org/2006/07/SWD/SKOS/reference/20081001/#S27
[S41] http://www.w3.org/2006/07/SWD/SKOS/reference/20081001/#S41

>
> For me:
> <A> broader <B> implies <A> broadMatch <B>
> but not <A> broadMatch <B> implies <A> broader <B>
>
> You can branch me to some document or tutorial (supplement to specs  
> chapter 10.6) as this is a rather basic question!!!
> This question is not "academic" as it is related with practical  
> development issues.
>
> Thanks!
>
> Christophe

> begin:vcard
> fn:Christophe Dupriez
> n:Dupriez;Christophe
> org:DESTIN inc. SSEB
> adr;quoted-printable:;;rue des Palais 44, bo=C3=AEte 1;Bruxelles;;B-1030;Belgique
> email;internet:Christophe.Dupriez@Destin.be
> title:Informaticien
> tel;work:+32/2/216.66.15
> tel;fax:+32/2/242.97.25
> tel;cell:+32/475.77.62.11
> note;quoted-printable:D=C3=A9veloppement de Syst=C3=A8mes de Traitement de l'Information
> x-mozilla-html:TRUE
> url:http://www.destin.be
> version:2.1
> end:vcard
> 


-- 
Alistair Miles
Senior Computing Officer
Image Bioinformatics Research Group
Department of Zoology
The Tinbergen Building
University of Oxford
South Parks Road
Oxford
OX1 3PS
United Kingdom
Web: http://purl.org/net/aliman
Email: alistair.miles@zoo.ox.ac.uk
Tel: +44 (0)1865 281993
Received on Monday, 2 February 2009 09:24:00 GMT

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