Re: SKOS Guide and owl:sameAs

Andrew Houghton wrote:

> Probably, both.  An example of a concept relocating in the DDC would be
> in Edition 21 005.6 was the concept "Microprogramming and microprograms",
> in Edition 22 005.6 was relocated to 005.18.  In this case you have the
> relationship:
> 
> Edition 21
>   skos:Concept 005.6
>     dct:isReplacedBy E22 005.18
> 
> Edition 22
>   skos:Concept 005.18
>     dct:replaces E21 005.18
> 
> to indicate the notion of a concept being relocated. 
>
> An example of
> a concept splitting would be in Edition 21 T2--145 was the concept 
> "Plane regions" which included pampas, plains, prairies, steppes, 
> tundras. However, in Edition 22 T2--145 pampas, prairies, steppes, 
> tundras were relocated to T2-153.  In this case you have the 
> relationship:
> 
> Edition 21
>   skos:Concept T2--145
>     dct:isReplacedBy
>       rdf:Alt
>         rdf:li E22 T2--145
>         rdf:li E22 T2--153
> 
> Edition 22
>   skos:Concept T2--145
>     dct:replaces E21 T2--145
>   skos:Concept T2--153
>     dct:replaces E21 T2--145
> 
> to indicate the notion of a concept splitting.

Thanks for the examples and a smart solution with dct:replaces and
dct:isReplacedBy. But this is just editorial information and does not
directly help you in retrieval. I wonder what the relation to the SKOS
mapping vocabulary should be.

In the first case:

Edition 21
  skos:Concept 005.6
     mapping:exactMatch E22 005.18

Edition 22
  skos:Concept 005.6
     mapping:exactMatch E22 005.18


In the second case:

Edition 21
  skos:Concept T2--145
    mapping:narrowMatch E22 T2--145
    mapping:narrowMatch E22 T2--153

Edition 22
  skos:Concept T2--145
    mapping:broadMatch E21 T2--145
  skos:Concept T2--153
    mapping:broadMatch E21 T2--145

But the concept splitting does involve more: E21 T--145 is the union of
E22 T2--145 and E22 T2--153. SKOS still lacks support of coordination.
It could be expressed something like this way:

Edition 21
  skos:Concept T2--145
    mapping:exactMatch
       coord:ucoord
         rdf:member E22 T2--145
         rdf:member E22 T2--153


Anyway dct:replaces and dct:isReplacedBy looks like one of these pitfals
where people can guess the meaning by the name of the property while it
is not clearly defined. If one concept is replaced by another you still
don't know how the meaning has changed - it's just said that something
is dropped and something new has been created instead.

Welcome to the "looks-like-semantic-web" ;-)
Jakob

Received on Wednesday, 1 November 2006 18:45:09 UTC