W3C home > Mailing lists > Public > public-swd-wg@w3.org > September 2008

ISSUE-146: Last Call Comment: broadMatch and skos:narrowMatch should be used only when there are no exact or close matches for the term elsewhere?

From: SWD Issue Tracker <dean+cgi@w3.org>
Date: Tue, 30 Sep 2008 12:00:44 +0000 (GMT)
To: public-swd-wg@w3.org,public-rdf-in-xhtml-tf@w3.org
Message-Id: <20080930120044.A7D65C6DAE@barney.w3.org>


ISSUE-146: Last Call Comment: broadMatch and skos:narrowMatch should be used only when there are no exact or close matches for the term elsewhere?

http://www.w3.org/2006/07/SWD/track/issues/146

Raised by: Alistair Miles
On product: SKOS

Raised by Margie Hlava in [1]:

"""
This is excellent work and generally a map can be made from a ANSI/NISO or 
a BSI or even and ISO thesaurus or controlled vocabulary standard to SKOS.  
However there are still a few confusions which prevent one from insuring 
complete interoperability from one to another.  This is represented by the 
section 10. Mapping Properties

skos: broadMatch and skos:narrowMatch should be used only when there are
no exact or close matches for the term elsewhere?

A taxonomic view of a thesaurus depends on the broader term narrower term 
relationships.  To SKOS this is not as important as the synonym (also known 
as equivalence) relationships.  The parent child, genus species, broader 
narrower term designations allows browse-able or navigational search.  This 
technique has taken much of the information industry  by storm for the last 
couple of years.  To allow this only as an after thought in SKOS is to 
marginalize an important area in findability.

Otherwise, no comments.
"""

[1] http://lists.w3.org/Archives/Public/public-swd-wg/2008Sep/0055.html
Received on Tuesday, 30 September 2008 12:01:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:54 UTC