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

dcat:themeTaxonomy proprety #38

Open
bfrichet3 opened this issue Jan 25, 2022 · 1 comment
Open

dcat:themeTaxonomy proprety #38

bfrichet3 opened this issue Jan 25, 2022 · 1 comment
Labels
status:question-answered Issue is a question, which has been answered with no impact on the implementation.

Comments

@bfrichet3
Copy link

Dear @andrea-perego

I hope you are all right and I wish you a very pleasant year.

I have a question regarding the dcat:themeTaxonomy proprety of dcat:Catalog. I cannot it in a RDF/XML I created with your API and I cannot find any occurence of that proprety in the xsl you document here. Does that mean you haven't (yet) implemented that mapping or is it something else?

Regards,

Benoît

@andrea-perego andrea-perego added the enhancement New feature or request label Feb 18, 2022
@andrea-perego
Copy link
Collaborator

Sorry for the late reply, @bfrichet3 .

You are right. The mapping is not implemented.

The reason is that this would require inferring the theme taxonomy based upon the keywords from controlled vocabularies included in the metadata records of catalogue services. However, both the keywords and the originating controlled vocabularies are usually specified not with URIs, but as free text keywords. Mapping them to URIs requires additional processing that has been kept out from the reference XSLT, as this would result in efficiency and performance issues.

@jakubklimek jakubklimek added status:question-answered Issue is a question, which has been answered with no impact on the implementation. and removed enhancement New feature or request labels Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:question-answered Issue is a question, which has been answered with no impact on the implementation.
Projects
None yet
Development

No branches or pull requests

3 participants