Origin and position:
Made available to the geoscience community by EPOS and operated by BRGM, the "EPOS Vocabulary Registry" is offering linked data vocabularies related to geoscience.
Born during the EPOS early days, it was designed to offer a reference entry point for FAIR linked data and vocabularies relevant to the domain of geoscience, that includes but is not limited to: geology, hydrogeology, geochemistry, geotechnics, mineral resources, geophysics, petrology, seismology, ...
The contents come from multiple international projects or even standards. A non-exhaustive list of sources, providers and projects includes: ISO, IUGS/CGI, INSPIRE, EPOS TCS Geological Information and Modeling, Minerals4EU.
Technology and functionnalities:
registry.epos-eu.org/ncl is an instance of LDRegistry.
Some key features are listed below:
- Discovery: navigate through the available vocabularies and browse the definitions and links between terms,
- Search: indicate a term you are looking for and see the results in the available vocabularies,
- SPARQL endpoint: advanced users can directly query the registry from https://registry.epos-eu.org/ncl/ui/sparql-form in order to submit raw SPARQL queries.
Basic operation
The tool's behavior to aliment the registry draws on three operations, each of these may be performed by authorized users through the Actions tab of different pieces of the information model:
- Existing item edition: this presents the set of predicates of the item, currently having assigned values, and also permits adding additional predicates;
- New item creation: "Create register" and "Manual entry" actions respectively allow creating a subregister or a single entry into an existing register;
- Batch edition or creation: "Register new or changed entires" allows editing or creating multiple entries of an existing register by direct uploading a CSV, JSONLD or TTL file. Structure of such files shall comply with the abovementioned information model of entities and collections as presented in these examples.
Rights, roles and permissions
As extensively described in LDRegistry Security Model, permissions sets are grouped under roles, granted to users, and qualified by locations.
In the example below, permissions Grant and Update grouped under the Maintainer role are granted to Bob for the specific Item1 located in Register2, while permissions Register, Update, StatusUpdate and Grant grouped under Manager role are granted to Alice for Register4 and thus apply to its whole subtree, i.e. Subregister1 and its contained items.
| Role | Applies to | Grants permissions |
|---|---|---|
| Manager | Specific register and its contained subtree | Register ; Update ; Status Update ; Grant |
| Maintainer | Single non-register item | Update ; Grant |
| Submitter | Specific register | Register ; Update |
| Reviewer | Specific register | Status Update |