-
Notifications
You must be signed in to change notification settings - Fork 47
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:record - check constraints #118
Comments
I would vote to keep the domain and range here -- this property is one of the properties that are part of the backbone structure of DCAT: |
Is an inverse property needed? |
Makx' makes a compelling case for retaining domain and range. I'll bring this proposition to the next DCAT team telecon for resolution. |
+1 to no change |
https://www.w3.org/2018/03/21-dxwgdcat-minutes |
In DCAT v1 the property
dcat:record
is axiomatizedThe text was updated successfully, but these errors were encountered: