Skip to content

Latest commit

 

History

History
44 lines (30 loc) · 3.3 KB

README.md

File metadata and controls

44 lines (30 loc) · 3.3 KB
Raw

CI

ASPECT: wind energy vAriableS ParametErs and ConsTants

This repository is meant for maintaining and updating the taxonomy (i.e. controlled vocabulary) of vAriableS ParametErs ConsTants (ASPECT) used in wind energy community. In general, controlled vocabularies such this one allow an accurate and controlled approach in describing assets such datasets.

We use sheet2rdf and OntoStack, developed by developed by Nikola Vasiljevic, to build and serve ASPECT taxonomy. We use purl.org to provide persistant URLs for ASPECT terms and properties:

sheet2rdf

This repository hosts automatic workflow, executed by means of Github actions, and underlying shell and python scripts which:

  • Fetches Google Sheet from Google Drive, which contains definitions of concepts (i.e., variables, parameters and constants), and converts it to xlsx and csv and stores these files to this repository
  • Converts fetched sheet to machine-actionable and FAIR RDF vocabulary using xls2rdf
  • Tests the resulting RDF vocabulary using qSKOS
  • Commits conversion results and tests logs to this repository
  • and deploy RDF vocabulary to OntoStack to be served to humans and machines

OntoStack

OntoStack is a set of orchestrated micro-services configured and interfaced such that they can intake vocabularies and resolve their terms and RDF properties upon requests either by humans or machines.

Some of OntoStack micro-services are:

  • Jena Fuseki a graph database
  • SKOSMOS a web-based SKOS browser acting as a front-end for the vocabularies persisted by the graph database
  • Træfik an edge router responsible for proper serving of URL requests

ASPECT is served by DTU Wind Energy instance of OntoStack: https://data.windenergy.dtu.dk/ontologies/view

Taxonomy implementation

The taxonomy is implemented in following services:

NEWA: New European Wind Atlas

Contribute

The taxonomy is intended to be used and further developed by the community. Therefore, we welcome collaborators willing to take part in the further development of the taxonomy. If you are one of them either request to become one of the taxonomy admins and/or post GitHub issues on what we can improve in the current taxonomy.