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:
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 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.
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 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).
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 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).
Labels, comments and definitions for SKOS Core classes and properties in languages other than English.
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> .
$Id: review-2.html,v 1.2 2005/09/01 14:59:23 ajm65 Exp $