View source for SkosCoreGuideToc/SectionConceptIdentity

__NOTOC__
= Concept Identity =

This section describes issues relating to establishing identity of resources of type <code><nowiki>skos:Concept</nowiki></code>.

== Identity and Mapping ==

Here 'identity' is taken to mean:

Two resources of type <code><nowiki>skos:Concept</nowiki></code> are identical iff they represent the same concept as defined by a specified concept scheme.

Here 'equivalence' is taken to mean:

Two resources of type <code><nowiki>skos:Concept</nowiki></code> are equivalent iff they intend the same meaning.

'''Identical resources of type <code><nowiki>skos:Concept</nowiki></code> may be merged in an RDF graph.'''

'''Equivalent but not identical resources of type <code><nowiki>skos:Concept</nowiki></code> may NOT be merged in an RDF graph.'''

To put this in plain speak: for two concepts that mean the same thing, if they belong to different concept schemes then they should always be represented as two distinct resources in an RDF graph.

Or, in other words: identical concepts should be merged; equivalent but not identical concepts should be mapped.

== Concept Identifiers ==

=== URI Identifiers ===

The simplest way to work with concepts in an RDF context is to refer to them using URIs.

There are a number of issues relating to assignment of URIs to concepts - for a full discussion see the VM TF note [ref].  

Here are a couple of issues briefly stated as an introduction to the options.

==== HTTP URIs ====

@@TODO

==== INFO URIs ====

@@TODO

==== Other URIs ====

@@TODO

=== Non-URI Identifiers ===

If you already have an identifier scheme for your concepts that is not based on the URI, you will probably want to include these identifiers in the description of your concepts, and may want to use them instead of URIs for referring to the concepts.

To include non-URI identifiers in a description of a concept, we recommend you define your own property.  So for example:


<pre><nowiki>
<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
  
  <rdf:Property rdf:about="http://my.example.org/knowledgebase/schema#identifier">
    <rdfs:comment>An identifier for a concept within my scheme.</rdfs:comment>
    <rdfs:subPropertyOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#value"/>
    <rdfs:subPropertyOf rdf:resource="http://purl.org/dc/elements/1.1/identifier"/>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
  </rdf:Property>

</rdf:RDF>
</nowiki></pre>


You can then use this new property in concept descriptions, for example:


<pre><nowiki>
<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  xmlns:skos="http://www.w3.org/2004/02/skos/core#"
  xmlns:my="http://my.example.org/knowledgebase/schema#">

  <skos:Concept rdf:about="http://my.example.org/knowledgebase/biology#spottedbowerbird">
    <!-- Other properties of the concept ... -->
    <my:identifier>14H87</my:identifier>
  </skos:Concept>

</rdf:RDF>
</nowiki></pre>


There are three things to note about the definition of the new property.

First, it is a sub-property of <code><nowiki>dc:identifier</nowiki></code>.  This helps to establish that the intended use of the new property is to specify an identifier for the given concept.  I.e. generic applications can deduce the semantics of the property.

Second, it is a sub-property of <code><nowiki>rdf:value</nowiki></code>.  This is to support interoperability with qualified dublin core usage of the <code><nowiki>dc:subject</nowiki></code> property (see below).

Third, it is an <code><nowiki>owl:[[InverseFunctionalProperty]]</nowiki></code>.  This means that two concepts with the same value for this property will be deemed identical.  In practise, this means that you can do things like:


<pre><nowiki>
<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  xmlns:skos="http://www.w3.org/2004/02/skos/core#"
  xmlns:my="http://my.example.org/knowledgebase/schema#">

  <skos:Concept>
    <skos:prefLabel>Spotted bowerbird</skos:prefLabel>
    <my:identifier>14H87</my:identifier>
    <skos:broader rdf:parseType="Resource">
      <my:identifier>12L47</my:identifier>
    </skos:broader>
    <skos:narrower rdf:parseType="Resource">
      <my:identifier>42U43</my:identifier>
    </skos:narrower>
    <!-- Other properties of the concept ... -->
  </skos:Concept>

</rdf:RDF>
</nowiki></pre>


I.e. you can have a complete RDF description of a concept scheme, without needing URIs.

== Published Subject Indicators ==

@@TODO

== Concept Identity Rules (Smushing) ==

=== Strong Identity Rules ===

The following rules may be used as a reliable basis for merging of graphs of concepts.

# If two resources have the same URI, then they are identical (RDF identity).
# If two resources have the same literal value (including language tag) for a <code><nowiki>skos:prefLabel</nowiki></code> property AND the same resource value for a <code><nowiki>skos:inScheme</nowiki></code> property, then they are identical (SKOS identity).
# If two resources have the same value for a property of type <code><nowiki>owl:[[InverseFunctionalProperty]]</nowiki></code> then they are identical (OWL identity).

=== Weak Identity Rules ===

The following rules may be applied to attempt graph merging:

# If two resources have the same value for an <code><nowiki>rdf:value</nowiki></code> property AND the same value for an <code><nowiki>rdf:isDefinedBy</nowiki></code> property, then they are candidates for identity.
# If two resources have the same value for an <code><nowiki>rdf:value</nowiki></code> property AND the same value for an <code><nowiki>rdf:type</nowiki></code> property where the value is not <code><nowiki>skos:Concept</nowiki></code>, then they are candidates for identity.
# If two resources have the same value for an <code><nowiki>rdfs:label</nowiki></code> property AND the same value for an <code><nowiki>rdf:isDefinedBy</nowiki></code> property, then they are candidates for identity.
# If two resources have the same value for an <code><nowiki>rdfs:label</nowiki></code> property AND the same value for an <code><nowiki>rdf:type</nowiki></code> property where the value is not <code><nowiki>skos:Concept</nowiki></code>, then they are candidates for identity.

Note these rules are included to support interoperability with Qualified Dublin Core style use of the <code><nowiki>dc:subject</nowiki></code> property.  For example, the dqc spec [ref] recommends usage such as:


<pre><nowiki>
<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/">

  <Description rdf:about="http://somewhere.org/someDoc.html">
    <dc:subject>
      <Description>
         <value>19D10</value>
         <rdfs:label>Algebraic K-Theory of spaces</rdfs:label>
         <rdfs:isDefinedBy rdf:resource="URI2"/>
      </Description>
    </dc:subject>
  </Description>

</RDF>
</nowiki></pre>


Compare this to a hypothetical description of a concept using SKOS Core:


<pre><nowiki>
<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:skos="http://www.w3.org/2004/02/skos/core#">
  
  <skos:Concept rdf:about="http://my.example.org/knowledgebase/mathematics#ktheory">
    <skos:prefLabel>Algebraic K-Theory of spaces</skos:prefLabel>
    <skos:inScheme rdf:resource="URI2"/>
  </skos:Concept>

</rdf:RDF>
</nowiki></pre>


Because <code><nowiki>skos:prefLabel</nowiki></code> is a sub-property of <code><nowiki>rdfs:label</nowiki></code>, and <code><nowiki>skos:inScheme</nowiki></code> is a sub-property of <code><nowiki>rdfs:isDefinedBy</nowiki></code>, the concept described in the second snippet is a candidate for identity with the blank node defined in the first snippet, under weak rule 3.

Or this description of a concept:


<pre><nowiki>
<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:skos="http://www.w3.org/2004/02/skos/core#"
  xmlns:my="http://my.example.org/knowledgebase/schema#identifier">
  
  <skos:Concept rdf:about="http://my.example.org/knowledgebase/mathematics#ktheory">
    <my:identifier>19D10</my:identifier>
    <skos:inScheme rdf:resource="URI2"/>
  </skos:Concept>

</rdf:RDF>
</nowiki></pre>


Here, because <code><nowiki>my:identifier</nowiki></code> is a sub-property of <code><nowiki>rdf:value</nowiki></code> (see above), and <code><nowiki>skos:inScheme</nowiki></code> is a sub-property of <code><nowiki>rdfs:isDefinedBy</nowiki></code>, the concept described in this snippet is a candidate for identity with the blank node defined in the first snippet, under weak rule 1.

----

'''End section'''