-
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:distribution - check constraints #120
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: |
Do we need an inverse property here - to allow a distro to point to the dataset that it purports to instantiate? |
In this case I think an inverse property makes sense. Otherwise, Makx makes a compelling case for retaining domain and range. |
No inverse properties please. They are not necessary. But that probably should better be discussed in a separate issue. |
Discussion on inverse of dcat:distribution moved to #166 |
+1 to no change |
https://www.w3.org/2018/03/21-dxwgdcat-minutes |
In DCAT v1 the property
dcat:distribution
is axiomatizedThe text was updated successfully, but these errors were encountered: