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

RE : Comments on SKOS Extension for Sub. Indexing

From: Antoine Isaac <Antoine.Isaac@KB.nl>
Date: Mon, 5 Feb 2007 23:13:22 +0100
Message-ID: <68C22185DB90CA41A5ACBD8E834C5ECD039A1F1B@goofy.wpakb.kb.nl>
To: "Jakob Voss" <jakob.voss@gbv.de>, "SKOS" <public-esw-thes@w3.org>
Hi Jakob,

>> By the way the properties skos:primarySubject 
>> skos:isPrimarySubjectOf should also be skipped (do you read this
>> Mike? ;-) because they are not well defined (what is "primary"? why
>> isn't there a "secondary"? or "third?" What about weighted index
>> terms? To support syntactic indexing in SKOS first the Coordination
>> issue needs to be solved. And I am not sure whether syntactic
>> indexing is really an SKOS issue. The most important is maybe
>> *ordered sets* of index terms.
>> This reads weird. In my opinion this 'ordered set' idea raises the
>> same problem as the primary or secondary subject one... If you have
>> a motivation for an ordered set, then you have specific indexing
>> needs, an it would perhaps be more adequate to include your own
>> subject specializations (unless you plan unlimited number of
>> ordered subjects)

>Ordered index terms (that is to keep in information in which order the
index terms were entered) are fundamental. The difference between "term1
term2, term3" and "term3, term2, term1" might be small but just skipping
this information is an error. SKOS needs a concept of ordered index sets
and this concept is relevant both to coordination for combined concepts
(especially when mapping) and to indexing.

Perhaps I misunderstood your use of the expression "ordered index terms": do you actually refer to what we called "concept combination"? (see [1] and the 25F giving 25F(+33) in the Iconclass example to which this issue points)

> For coordination it is still in the air, cf the list of issue (and
> requirement) that are being currently worked out on the Semantic Web
> Deployment wiki [1] For notations, well we could raise a dedicated
> issue, but it would be nice for SWD to have more motivating use cases
> than the single Iconclass one I contributed. I suppose UDC would be
> enough, but have no time to write it down now :-(

>Almost *any* classification system uses notations and titles instead of
labels only. Because SKOS was designed for thesauri the problem was not
visible before. But in a classification there are two kinds of labels:
1. notations: mostly artificial codes that uniquely identify a concept
2. titles: human readable label, does not need to be unique. May occur
in multiple languages and variants.
This is *not* the same distinction as skos:prefLabel and skos:altLabel.

I am very well aware of that, since as said I had to deal with a vocabulary with notations (and that, once again, I used your zxx-prefLabel trick)

>For use cases see:
For example:

Thanks for the links!



[1] http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox#head-4d19f4a19e981a612732d38183cc494f0affe91c
Received on Monday, 5 February 2007 22:13:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:55 UTC