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:record - check constraints #118

Closed
dr-shorthair opened this issue Feb 15, 2018 · 5 comments
Closed

dcat:record - check constraints #118

dr-shorthair opened this issue Feb 15, 2018 · 5 comments

Comments

@dr-shorthair
Copy link
Contributor

In DCAT v1 the property dcat:record is axiomatized

dcat:record
  rdf:type owl:ObjectProperty ;
  rdfs:domain dcat:Catalog ;
  rdfs:range dcat:CatalogRecord ;
.

  1. Verify that the range is appropriate and necessary
  2. Verify that the domain is appropriate and necessary (see Review global domain axioms on dcat properties #110)
  3. Consider whether any guarded constraints (using owl:Restriction) should be introduced (see Use owl:Restriction constraints to bind DC properties to DCAT classes  #105)
@makxdekkers
Copy link
Contributor

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:
Catalog > record > CatalogRecord

@dr-shorthair
Copy link
Contributor Author

Is an inverse property needed?

@dr-shorthair
Copy link
Contributor Author

dr-shorthair commented Mar 14, 2018

Makx' makes a compelling case for retaining domain and range.

I'll bring this proposition to the next DCAT team telecon for resolution.

@dr-shorthair
Copy link
Contributor Author

+1 to no change

@dr-shorthair
Copy link
Contributor Author

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

No branches or pull requests

2 participants