Abstract

Introduction

This model is an application profile for Data4Wallonia. It allows to express the taxonomy used to classify concepts in Data4Wallonia portal.

D4WTA-AP is designed to meet the following use cases:

• facilitating the findability of the concepts;
• being compliant with existing standards to reach semantic interoperability.

The specification of the Data4Wallonia Taxonomy Application Profile is represented in a UML class diagram. The figure here beneath shows the full profile which includes the classes and properties that define the taxonomy itself.

Status

This Application Profile has the status Draft published at 2024-09-04.

Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog.

License

Copyright © 2024 Agence Du Numérique. All material in this repository is published under the license CC-BY 4.0, unless explicitly otherwise mentioned.

Terminology

An Application Profile (AP) is a specification that reuses terms from one or more base standards, adding more specificity by identifying mandatory, recommended and optional elements to be used for a particular application, as well as recommendations for controlled vocabularies to be used.

A Core Vocabulary (CV) is a basic, reusable and extensible data specification that captures the fundamental characteristics of an entity in a context-neutral fashion. Its main objective is to provide terms to be reused in the broadest possible context. More information can be found on the SEMIC Style Guide.

Overview

Main Entities

Concept

Definition

This class represents any concept that can be used for classifying the Public Service and which relates to the Public Service through the property Is Classified By.

Usage Note

This class has been added in the CPSV-AP to complement the need for adding other ways of classifying the Public Service, which have not been explicitly defined in the CPSV-AP. In this context, the CPSV-AP reuses the Concept class as defined in the SKOS Simple Knowledge Organization System. For describing the attributes of a Concept (labels, preferred labels, alternative labels, definition, etc.) we refer to SKOS. The Concept may or may not belong to (member) a certain Collection.

Properties

For this entity the following properties are defined: alternative label , definition , has broader , identifier , is in scheme , is replaced by , is top concept of , preferred label , replaces , status , title , version info .

	Property	Range	Card	Definition	Usage
	alternative label	Text	0..*	An alternative lexical label for a resource.	Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel).
	definition	Text	1..*	A statement or formal explanation of the meaning of a concept.
	has broader	Concept	0..1	Relates a concept to a concept that is more general in meaning.
	identifier	String	1	An unambiguous reference to the resource within a given context.
	is in scheme	Concept Scheme	1	Relates a resource (for example a concept) to a concept scheme in which it is included.
	is replaced by	Concept	0..1	A related resource that supplants, displaces, or supersedes the described resource.
	is top concept of	Concept Scheme	0..1	Relates a concept to the concept scheme that it is a top level concept of.
	preferred label	Text	1..*	The preferred lexical label for a resource, in a given language.	Labels should be in French or English. Labels should be at least in French. Labels should start with capital letters. Labels should not contain special characters such as & ( ) \ or /.
	replaces	Concept	0..1	A related resource that is supplanted, displaced, or superseded by the described resource.
	status	Concept	1	The status of the concept in the context of a particular workflow process.	The recommended controlled vocabulary is the Publications Office Concept status authority table.
	title	Text	0..*	A name given to the resource.	This property is used as the "popularized title".
	version info	String	1	This element contains a string giving information about this version such as RCS/CVS keywords.	The values should follow Semantic Versioning (X.X.X).

Concept Scheme

Definition

A set of concepts, optionally including statements about semantic relationships between those concepts.

Usage Note

A concept scheme may be defined to include concepts from different sources.

Properties

For this entity the following properties are defined: date created , date issued , date modified , has top concept , identifier , is replaced by , preferred label , replaces , title , version info .

	Property	Range	Card	Definition	Usage
	date created	Date	1	Date of creation of the resource.
	date issued	Date	0..1	Date of formal issuance of the resource.
	date modified	Date	0..1	Date on which the resource was changed.
	has top concept	Concept	0..*	Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies.
	identifier	String	1	An unambiguous reference to the resource within a given context.
	is replaced by	Concept Scheme	0..1	A related resource that supplants, displaces, or supersedes the described resource.
	preferred label	Text	1..*	The preferred lexical label for a resource, in a given language.	Labels should be in French or English. Labels should be at least in French. Labels should start with capital letters. Labels should not contain special characters such as & - ( ) \ or /.
	replaces	Concept Scheme	0..1	A related resource that is supplanted, displaced, or superseded by the described resource.
	title	Text	0..*	A name given to the resource.
	version info	String	1	This element contains a string giving information about this version such as RCS/CVS keywords.	The values should follow Semantic Versioning (X.X.X).

Supportive Entities

Datatypes

	Class	Definition
	Date	The ·value space· of date consists of top-open intervals of exactly one day in length on the timelines of dateTime, beginning on the beginning moment of each day (in each timezone), i.e. '00:00:00', up to but not including '24:00:00' (which is identical with '00:00:00' of the next day). For nontimezoned values, the top-open intervals disjointly cover the nontimezoned timeline, one per day. For timezoned values, the intervals begin at every minute and therefore overlap.
	String	The string datatype represents character strings in XML. The ·value space· of string is the set of finite-length sequences of characters (as defined in [XML 1.0 (Second Edition)]) that ·match· the Char production from [XML 1.0 (Second Edition)]. A character is an atomic unit of communication; it is not further specified except to note that every character has a corresponding Universal Character Set code point, which is an integer.
	Text	The text data type is a combination of a string and a language identifier.