This repository is part of the PLDN activities for the PLDN Linked Data Thesaurus Working Group.
The terminology that is used in the Linked Data domain consists of many specialized terms, abbreviations and acronyms that makes it hard for persons new to Linked Data to understand what Linked Data is about and what you can do with it to overcome e.g. data integration barriers (the data silo problem).
There is large communication gap (semantic gap) between Linked Data experts and non-experts that the PLDN Linked Data Thesaurus Working Group would like to solve via a new and up-to-date PLDN Linked Data Thesaurus that defines 30% of the Linked Data terms that we use 90% of the time (a minimal set of the most relevant terms). Not only will each term have a short, clear and concise definition, it will also have references to existing definitions in DBpedia and Wikidata and it will have references to additional information from authorative sources like W3C, the Dutch Standardization Forum, etc. And the Linked Data Thesaurus will also have a hierarchical and thematic structure that would make terms, abbreviations and acronyms as accessible and findable as possible.
No Linked Data vocabulary stands on its own, it is usually linked to other internal and external vocabularies and datasets to maximize data re-use and to realize a more modular structure, where the needed modeling constructs are defined only once (and re-used many times). This means that we will also create a PLDN Community Ontology that defines the persons, organizations and activities of PLDN and a PLDN Publication Ontology that defines the deliverables of PLDN. Both ontologies will be lightweight ontologies, where we will only show the modelling constructs that we need in combination with the PLDN Linked Data Thesaurus and the first versions of these ontologies will be based upon current OWL-based practices (SHACL-based versions might be added in the future).
This repository contains the relevant development documentation for the PLDN Vocabularies is such a way that it can be used as a PLDN Vocabulary Catalog supporting the:
- development process
- documentation process
- governance process
- PLDN Best Practices: with e.g. the PLDN Thesaurus Best Practices document (when available)