8000 Relax range restriction on dcat:theme · Issue #1364 · w3c/dxwg · GitHub
[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Relax range restriction on dcat:theme #1364

Closed
andrea-perego opened this issue May 18, 2021 · 5 comments · Fixed by #1379
Closed

Relax range restriction on dcat:theme #1364

andrea-perego opened this issue May 18, 2021 · 5 comments · Fixed by #1379
Labels
dcat:theme dcat feedback Issues stemming from external feedback to the WG
Milestone
DCAT3 3PWD

Comments

@andrea-perego
Copy link
Contributor

@dr-shorthair

Why not relax range constraint for dcat:theme? In the biomedical domain we have more ontologies and often these ontologies have owl:Class typing for concepts.

Originally posted by @rajaram5 in #123 (comment)
@andrea-perego andrea-perego mentioned this issue May 18, 2021
Closed
@andrea-perego andrea-perego added dcat dcat:theme feedback Issues stemming from external feedback to the WG labels May 18, 2021
@andrea-perego andrea-perego added this to the DCAT3 3PWD milestone May 18, 2021
@andrea-perego andrea-perego mentioned this issue May 18, 2021
Closed
@agbeltran
Copy link
Member

There was also a discussion around the range for dcat:theme at: #1153

@dr-shorthair
Copy link
Contributor

I would be comfortable relaxing the ranges of theme and themeTaxonomy. But it is important to keep them as object-properties, since the object must be denoted by a URI - i.e. taken from a managed source somewhere.

@makxdekkers
Copy link
Contributor

All, there was an earlier discussion on this (see here), where I noted that dcat:theme was explicitly minted for DCAT version 1 because it was felt that the range of dct:subject was too broad and that it would be useful to have a property with a range restricted to skos:Concept. Otherwise, dct:subject could have been used.
Now, with the relaxation of the range of dct:subject, which now also allows for textual values, I guess that dcat:theme with relaxed range, but still requiring it to be an object property, can still be seen as a restriction on dct:subject, effectively making it the same as the 'old' (pre-relaxation) dct:subject. Right?

@rajaram5
Copy link

@dr-shorthair yes, it could work for our use cases if dcat:theme is an object property

@rajaram5
Copy link

@makxdekkers I see your point. As I mentioned early in biomedical domain we have more owl based ontologies and vocabularies. So if you still like to restrict range of dcat:theme property it would be nice to have list of values like skos:Concept, owl:Class.

This was referenced Jun 7, 2021
Closed
Merged
@riccardoAlbertoni riccardoAlbertoni linked a pull request Jun 18, 2021 that will close this issue
Dcat issue 1364 second solution #1379
Merged
@riccardoAlbertoni riccardoAlbertoni mentioned this issue Jul 5, 2021
Merged
riccardoAlbertoni added a commit that referenced this issue Jul 5, 2021
@riccardoAlbertoni
adding Rajaram Kaliyaperumal for issue #1364
70f20e3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dcat:theme dcat feedback Issues stemming from external feedback to the WG
Projects
None yet
Milestone
DCAT3 3PWD
Development

Successfully merging a pull request may close this issue.

Dcat issue 1364 second solution w3c/dxwg
5 participants
@dr-shorthair @agbeltran @rajaram5 @makxdekkers @andrea-perego
0