Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make catalog information DCAT-AP/VL compliant #964

Closed
rorlic opened this issue Nov 2, 2023 · 4 comments
Closed

Make catalog information DCAT-AP/VL compliant #964

rorlic opened this issue Nov 2, 2023 · 4 comments
Assignees
Labels
admin enhancement New feature or request fetch good first issue Good for newcomers

Comments

@rorlic
Copy link
Contributor

rorlic commented Nov 2, 2023

Is your feature request related to a problem? Please describe.
Currently, when adding a new catalog using /admin/api/v1/dcat the catalog is identified using a newly created GUID.
This GUID is currently not used except for as a way to delete the catalog information.
The DCAT-AP/VL requires a dc:identifier for a catalog and currently we do not add one.

Describe the solution you'd like
we can reuse the generated GUID as the catalog identifier.
Please add a statement to the catalog for the generated identifier. E.g.

@prefix dcat:     <http://www.w3.org/ns/dcat#> .
@prefix dc:       <http://purl.org/dc/terms/> .
@prefix rdfs:     <http://www.w3.org/2000/01/rdf-schema#> .

[] a dcat:Catalog ;
  ...
  dc:identifier "2a896d35-8c72-4723-83b3-add9b1be96aa"^^rdfs:Literal .
@rorlic rorlic added enhancement New feature or request good first issue Good for newcomers admin fetch labels Nov 2, 2023
@rorlic
Copy link
Contributor Author

rorlic commented Nov 2, 2023

In addition, please also add the following for each dataset (= LDES):

[] a dcat:Dataset
  ...
  dc:conformsTo <https://w3id.org/tree/specification>, <https://w3id.org/ldes/specification> .

<https://w3id.org/tree/specification> a dc:Standard .
<https://w3id.org/ldes/specification> a dc:Standard .

i.e. add 2 dc:conformsTo statements to each Dataset.

@rorlic rorlic changed the title Add catalog identifier to DCAT info Make catalog information DCAT-AP/VL compliant Nov 2, 2023
@rorlic
Copy link
Contributor Author

rorlic commented Nov 2, 2023

In addition, add an identifier to each Dataset and each DataService:

[] a dcat:Dataset
  ...
  dc:identifier "https://example.org/observations"^^rdfs:Literal .

[] a dcat:DataService
  ...
  dc:identifier "https://example.org/observations/by-location"^^rdfs:Literal .

You can use the full URL of the LDES and view as a string (not an URI).

@rorlic
Copy link
Contributor Author

rorlic commented Nov 2, 2023

Finally, add an endpoint description to each DataService (view) and mark it as a rdfs:Resource:

[] a dcat:DataService
  ...
  dcat:endpointDescription <http://localhost:8080/v1/swagger?urls.primaryName=base> .

<http://localhost:8080/v1/swagger?urls.primaryName=base> a rdfs:Resource .

The URI of the dcat:endpointDescription can be constructed by taking the server settings:
{ldes-server.host-name}{springdoc.swagger-ui.path}?urls.primaryName=base

@rorlic
Copy link
Contributor Author

rorlic commented Nov 7, 2023

for now use a fixed value for all dcat:endpointDescription, i.e.

...
dcat:endpointDescription <https://semiceu.github.io/LinkedDataEventStreams/> .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin enhancement New feature or request fetch good first issue Good for newcomers
Projects
Archived in project
Development

No branches or pull requests

2 participants