ISSUE-74

MappingPropertyConventions

State:
CLOSED
Product:
SKOS
Raised by:
Alistair Miles
Opened on:
2008-01-16
Description:
Currently, given separate vocabularies for semantic relations (skos:broader,
skos:narrower, skos:related etc.) and for concept mapping relations
(skos:broadMatch, skos:narrowMatch, skos:relatedMatch etc.), our assumption is
that, *by convention*, the SKOS semantic relation properties are *only* used to
state links between conceptual resources within the *same* concept scheme, and
the SKOS concept mapping properties are *only* used to state links between
conceptual resources in *different* concept schemes. 

Is this usage convention appropriate, useful and viable? Are there circumstances
where we would recommend *not* adhering to this convention?

Note that it is difficult to formally state any integrity conditions which could
be used to enforce this usage convention. No such integrity conditions are
currently stated in the SKOS reference. Therefore, graphs such as:

<A> skos:broader <B> ; skos:related <C> .
<A> skos:inScheme <MyScheme> .
<B> skos:inScheme <AnotherScheme> .
<C> skos:inScheme <AnotherScheme> .
<MyScheme> owl:differentFrom <AnotherScheme> . 

... and:

<A> skos:broadMatch <B> ; skos:relatedMatch <C> .
<A> skos:inScheme <MyScheme> .
<B> skos:inScheme <MyScheme> .
<C> skos:inScheme <MyScheme> .

... are both consistent with the SKOS data model. If we agree on the usage
convention, can we live without any supporting integrity conditions?

Note finally that if we chose *not* to have a separate vocabulary for concept
mapping relations and for semantic relations, and we use only semantic relations
to assert links between conceptual resources, this issue goes away. I.e. the
resolution of this issue is dependant on the resolution of ISSUE-71.


Related emails:
  1. ISSUE-74: MappingPropertyConventions (from dean+cgi@w3.org on 2008-01-16)
  2. Re: ISSUE-74: MappingPropertyConventions (from aisaac@few.vu.nl on 2008-01-21)
  3. Re: ISSUE-71: ParallelMappingVocabulary (from aisaac@few.vu.nl on 2008-01-21)
  4. Several emails to reply to (from Margherita.Sini@fao.org on 2008-02-04)
  5. [SKOS] Issues Review [From Alistair] (from aisaac@few.vu.nl on 2008-02-17)
  6. [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions [From Alistair Miles!] (from aisaac@few.vu.nl on 2008-02-17)
  7. Re: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions (from aisaac@few.vu.nl on 2008-02-17)
  8. RE: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions (from Margherita.Sini@fao.org on 2008-02-18)
  9. [SKOS] Closing ISSUE-71 ParallelMappingVocabulary (from aisaac@few.vu.nl on 2008-02-19)
  10. [SKOS] Closing ISSUE-74 MappingPropertyConventions (from aisaac@few.vu.nl on 2008-02-19)
  11. Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary (from dlrubin@stanford.edu on 2008-02-19)
  12. Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary (from sean.bechhofer@manchester.ac.uk on 2008-02-20)
  13. Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary (from aisaac@few.vu.nl on 2008-02-20)
  14. [Fwd: [SKOS] Issues Review (from alistair.miles@zoo.ox.ac.uk on 2008-02-21)
  15. [SKOS] Issues Review (from alistair.miles@zoo.ox.ac.uk on 2008-02-21)
  16. RE: [SKOS] on ISSUE-71 and ISSUE-74 (from dstudhope@glam.ac.uk on 2008-02-28)
  17. Meeting Record: 2008-02-27 SWD telecon (from ehs@pobox.com on 2008-03-01)
  18. Comment: ISSUE-74 (from johan.de-smedt@tenforce.com on 2008-03-02)
  19. RE: [SKOS] on ISSUE-71 and ISSUE-74 (from sdclarke@lukehouse.demon.co.uk on 2008-03-03)
  20. Minutes from 2008-03-18 telecon (from cred@loc.gov on 2008-03-19)
  21. [SKOS] Issue owners - preparation for Washington (from baker@sub.uni-goettingen.de on 2008-04-15)
  22. Re: [SKOS] Issue owners - preparation for Washington (from aisaac@few.vu.nl on 2008-04-21)

Related notes:

2008-04-22: See also issue 71 ParallelMappingVocabulary ParallelMappingVocabulary

2008-04-22: http://www.w3.org/2006/07/SWD/track/issues/71

2008-05-07: RESOLUTION: 1. keep the mapping vocabulary broadMatch, narrowMatch, 2. broadMatch, narrowMatch, etc. are rdfs:subPropertyOf broader, narrower, 3. there are no semantic conditions on broadMatch, narrowMatch; i.e. graphs 1-6 are all consistent, 4. there is some text about cultural conventions explaining where we expect broadMatch to be used, 5. by convention, mapping properties are only used to link concepts in different schemes, 6. in the Last Call WD we'll note that the mapping vocabulary may be dropped -- http://www.w3.org/2008/05/06-swd-minutes.html#item04