VocPrez Profile - Specification

URI: https://w3id.org/profile/vocprez/spec
Title: VocPrez Profile - Specification Document
Definition: This document specifies the VocPrez Profile. It is to be used to inform people about the requirements that need to be met by data claiming to conform to the profile.
Created: 2022-03-20
Modified: 2022-03-20
Creator: SURROUND Australia Pty Ltd
Publisher: SURROUND Australia Pty Ltd
Further metadata: This specification is part of the VocPrez Profile. See that profile's main document for License & Rights information and other metadata not given here.
Profile URI: https://w3id.org/profile/vocprez
License: CC-BY 4.0

Abstract

This is the specification document of the VocPrez Profile which is a profile of another profile, the VocPub Profile, which profiles the Simple Knowledge Organization System (SKOS).

This document specifies the requirements of data that must be met in order for that data to claim conformance to the VocPrez Profile.

This specification document is not to be used for testing conformance of RDF resoruces to this profile. That role belongs to the validation resources within this profile:

The first in the list above contains tests for this profile's unique requirements only. The second, the combination of this profile's and the VocPub profile's requirements.

For the list of all resources within this profile, see the profile definition:

https://w3id.org/profile/vocprez

Namespaces

This document refers to elements of various ontologies by short codes using namespace prefixes. The prefixes and their corresponding namespaces' URIs are:

dcterms: http://purl.org/dc/terms/
prof: http://www.w3.org/ns/dx/prof/
prov: http://www.w3.org/ns/prov#
sdo: https://schema.org/
skos: http://www.w3.org/2004/02/skos/core#
rdfs: http://www.w3.org/2000/01/rdf-schema#
vocpub: https://w3id.org/profile/vocpub/

1. Introduction

The VocPub Profile constrains the many ways in which the Simple Knowledge Organization System Reference (SKOS)^{ref may be used to formulate vocabularies. VocPub requires simplicity of vocab presentation - one vocab per file; all vocabs to consist of Concepts within a single Concept Scheme etc. - that basic metadata is provided - all Concepts must have certain labels and definitions and ConceptScheme must indicate publishers etc.} - and that Concepts indicate both the vocabulary which originally defined them and were they appear in the current vocabulary - where the defining and current vocabulary, or may not, be the same.

Other than that, vocabulary implementers using VocPub may implement standard SKOS vocabularies as they wish: the shat of the hierarchy is as they prefer; whether to use Collections or not etc.

This profile add just two Requirements on top of VocPub's:

All Concept, Concept Schema and Collection objects must present a literal identifier
All Concepts must use the skos:inScheme property

These two Requirements are implemented to ensure that the VocPrez configuration of the Prez tool - a Linked Data API - has all the data elements it needs in order to dpsplay vocabulary content well.

So this profile is a system-specific profile and will always be ket up-to-date with the VocPrez system's needs.

In the next section, this specification's two Requirements are formally identified and described. They are indicated in red text.

2. Elements & Requirements

2.1. Each SKOS Concept, ConceptScheme and Collection MUST provide exactly one identifier using the DCTERMS identifier property and typed as an XSD token

The VocPrez system needs to be able to construct short system URLs to each data object within it and for this it needs a unique identifier per object where the identifier contains no characters taht would be problematic in a URL path segment.

2.2 Each SKOS Concept MUST indicate that it is within exactly one Concept Scheme by use of the SKOS inScheme property

While it is possible to indicate that a skos:Concept is placed within a skos:ConceptScheme in a couple of different ways, for instance with use of skos:inScheme or skos:topConceptOf, the VocPrez looks specifically for the skos:inScheme property when constructing concept heirarchies, so this property must be present.

3. References

PROV: Rob Atkinson; Nicholas J. Car (eds.). The Profiles Vocabulary. 18 December 2019. W3C Working Group Note. URL: https://www.w3.org/TR/dx-prof/
SKOS: Alistair Miles; Sean Bechhofer (eds.). SKOS Simple Knowledge Organization System Reference. 18 August 2009. W3C Recommendation. URL: https://www.w3.org/TR/skos-reference/
SKOS Primer: Antoine Isaac; Ed Summers (eds.). SKOS Simple Knowledge Organization System Primer. 18 August 2009. W3C Note. URL: https://www.w3.org/TR/skos-primer/
Semantic Web: World Wide Web Consortium. Semantic Web 2015. Web Page. URL: https://www.w3.org/standards/semanticweb/, accessed 2020-06-14