SKOS Core Second Review

The second review for the SKOS Core Vocabulary begins 25th July 2005, reviewers appointed by SWBPD-WG are Mark van Assem and Ralph Swick.

The reviewers are asked to raise any issues with the following proposed changes to the SKOS Core Vocabulary:

  1. subjectIndicatorUse-1 : drop usage of the skos:subjectIndicator property within the SKOS Core Vocabulary itself.
  2. notes-2: deprecate skos:privateNote and skos:publicNote and replace with new property skos:note.
  3. symbolicLabelsRange-3: refactor symbolic labelling properties and change range to DCMI type Image.
  4. seeAlsoTranslations-4: add rdfs:seeAlso statements to fr and de labels/definitions/comments.

subjectIndicatorUse-1: drop usage of the skos:subjectIndicator property within the SKOS Core Vocabulary itself.

Issue / Requirement

The usage of the skos:subjectIndicator property within the SKOS Core Vocabulary itself, to describe properties and classes of the SKOS Core Vocabulary is dubious, and does not fit with intended usage of this property.

Proposed action

Proposed to remove all statements from the SKOS Core Vocabulary RDF/OWL description that have skos:subjectIndicator as predicate, i.e. that match the pattern (?x <http://www.w3.org/2004/02/skos/core#subjectIndicator> ?y).

N.B. this is not a proposal to remove the skos:subjectIndicator property itself.

Transition history

opened on 1 June 2005
Background, proposals, threads, notes

notes-2: deprecate skos:privateNote and skos:publicNote and replace with new property skos:note.

Issue / Requirement

Currently all SKOS Core documentation properties are sub-properties of either skos:publicNote or skos:privateNote. This means that currently e.g. a definition or a scope note must always be public, and a change note must always be private. There is a requirement for stating the intended audience of a note independently from the function of the note. I.e. someone might want different definitions for different audiences, with the notion of 'public' versus 'private' being only one way of specifying an audience.

Proposed action

Proposed to deprecate the skos:publicNote and skos:privateNote properties, and to replace these with a new property skos:note.

Proposed to change the super-property of skos:definition skos:scopeNote skos:example skos:historyNote skos:editorialNote and skos:changeNote to skos:note. So i.e. the new documentation property hierarchy will look like:

skos:note
  skos:definition
  skos:scopeNote
  skos:example
  skos:historyNote
  skos:editorialNote
  skos:changeNote

Proposed to add a paragraph to the SKOS Core Guide recommending usage of the dcterms:audience property to specify the audience of a note (where the note is represented as a related resource description or a document reference).

Transition history

opened on 15 June 2005
Background, proposals, threads, notes

symbolicLabelsRange-3: refactor symbolic labelling properties and change range to DCMI type Image.

Issue / Requirement

Currently both symbolic labelling properties have a range of foaf:Image, however FOAF is relatively unstable. The DCMITYPE vocabulary has an Image class and is more stable.

Also current design pattern in SKOS Core is for all property families to descend from a single super-property, however both skos:prefSymbol and skos:altSymbol have no super-property, yet share some semantics.

Proposed action

Proposed to add new property skos:symbol with domain of rdf:Resource and range of http://purl.org/dc/dcmitype/Image, with a definition like 'a symbolic label for a resource'.

Proposed to make skos:prefSymbol and skos:altSymbol sub-properties of skos:symbol.

Proposed to remove domain and range statements from skos:prefSymbol and skos:altSymbol (domain and range is implied by super-property).

Transition history

opened on 1 July 2005
Background, proposals, threads, notes

seeAlsoTranslations-4 : add rdfs:seeAlso statements to fr and de labels/definitions/comments.

Issue / Requirement

Labels, comments and definitions for SKOS Core classes and properties in languages other than English.

Proposed action

Add the following statements to http://www.w3.org/2004/02/skos/core ...

@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<http://www.w3.org/2004/02/skos/core> rdfs:seeAlso <http://www.w3.org/2004/02/skos/core_fr> . 
<http://www.w3.org/2004/02/skos/core> rdfs:seeAlso <http://www.w3.org/2004/02/skos/core_de> . 

Transition history

opened on 11 July 2005
Background, proposals, threads, notes

$Id: review-2.html,v 1.2 2005/09/01 14:59:23 ajm65 Exp $

Valid XHTML 1.0!