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

Resolving ELIs in HVD Datasets #328

Open
fabiankirstein opened this issue Jan 19, 2024 · 1 comment
Open

Resolving ELIs in HVD Datasets #328

fabiankirstein opened this issue Jan 19, 2024 · 1 comment

Comments

@fabiankirstein
Copy link

DCAT-AP High Value Datasets introduces the property dcatap:applicableLegislation , which should be populated with ELI URLs, such as http://data.europa.eu/eli/reg_impl/2023/138/oj.

I am wondering what the best approach is to resolve an ELI URL to extract the metadata. A possible use case would be display metadata of the legislation in a web frontend, such as the description.

However, it seems that the ELI metadata is only available as microdata as described here: https://eur-lex.europa.eu/eli-register/technical_information.html This means parsing means to include to download the HTML and process it with an RDFa parser. I did this with a browser plugin: example.txt

For me this seems very complicated. It would be better to just get the RDF maybe via content negotiation. Or do I overlook something here?

I am very much interested in opinions. Thanks!

@bertvannuffelen
Copy link
Contributor

This is already a long standing issue. I reached out the Cellar team responsible for the publication of the ELIs.

On the question: Are there any plans for making the CELLAR minted ELIs dereferenceable? The reponse is "Indeed, we have issues with ELI URIs and are working on it. We are currently doing some tests to fix it, and will come back to you."

I also questioned for alternatives and possibilities to get to the RDF representations of the ELIs.
They reponded with the following approach:

  1. replace the “/” with “:” on the ELI identifier. For example the URI http://data.europa.eu/eli/reg_impl/2023/138/oj is turned into by http://publications.europa.eu/resource/eli/reg_impl:2023:138:oj .
  2. This version results in HTML. For the RDF representation HTTP headers must be set. For instance: use the Accept header application/rdf+xml;notice or application/rdf+xml;notice=non-inferred

I also explored the CELLAR documentation at https://op.europa.eu/en/web/cellar/cellar-data/metadata/metadata-notices
.
I tried for instance

curl -H "Accept:application/xml;notice=identifiers" http://publications.europa.eu/resource/eli/reg_impl:2023:138:oj
curl -H "Accept:application/xml;notice=identifiers" http://publications.europa.eu/resource/eli/reg_impl:2023:138:oj -L
curl -H "Accept:application/rdf+xml;notice=non-inferred-tree" http://publications.europa.eu/resource/eli/reg_impl:2023:138:oj -L

Depending on the ELI it may return content. The rules why some return data and others not I do not know.

I hope this already gets you forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants