You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Flanders an indication is given for each type of entity which standards the entity conforms to. Example: an entity is of type registry service when it offers data according to the ISO19115 standard.
The properties of a standard are the following:
property
definition
title
Name of the standard
langString [0..1]
description
Brief description of the standard
langString [0..1]
identifier
Unique identifier
string [1..1]
type
Categorisation of the standard
Concept [0..n]
seeAlso
Link to the specification
Resource [0..1]
versionInfo
Version of the standard
string [0..1]
issued
Date of publication of the standard
dateTime [0..1]
prefLabel
Abbreviated notation of the standard, e.g., ISO19115
string [0..1]
Adding the identifier allows us to refer to the exact specification by the standard, if possible, to the entity. For example:
The attributes seeAlso and prefLabel are additions on top of GeoDCAT-AP. Could this be interesting on the DCAT-AP level as well, as we feel that this would be a more generic improvement?
In Flanders an indication is given for each type of entity which standards the entity conforms to. Example: an entity is of type registry service when it offers data according to the ISO19115 standard.
The properties of a standard are the following:
ISO19115
Adding the identifier allows us to refer to the exact specification by the standard, if possible, to the entity. For example:
The attributes
seeAlso
andprefLabel
are additions on top of GeoDCAT-AP. Could this be interesting on the DCAT-AP level as well, as we feel that this would be a more generic improvement?Related ticket: #115
The text was updated successfully, but these errors were encountered: