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

dct:creator for dcat:Resource #443

Closed
agbeltran opened this issue Oct 4, 2018 · 5 comments · Fixed by #504
Closed

dct:creator for dcat:Resource #443

agbeltran opened this issue Oct 4, 2018 · 5 comments · Fixed by #504
Assignees
Milestone

Comments

@agbeltran
Copy link
Member

when discussing data citation in #61, we added dct:creator to dcat:Dataset

I believe this property could be moved to the super class dcat:Resource and potentially to other classes, such as dcat:Distribution to (partly) support citation of distributions (#433)

@agbeltran agbeltran added the dcat label Oct 4, 2018
@makxdekkers
Copy link
Contributor

makxdekkers commented Oct 4, 2018

The property is already in the box dcat:Resource in Fig 1 at https://w3c.github.io/dxwg/dcat/#vocabulary-overview, but it should be modeled as a object property with range foaf:Agent like dct:publisher.
Not sure if we foresee cases where individual distributions have their own creator but if it helps with citation then I guess it's OK to put it on distribution too.

@dr-shorthair
Copy link
Contributor

Fixed the figure

@agbeltran
Copy link
Member Author

Thanks both - it is in the figure but not in the text https://w3c.github.io/dxwg/dcat/#Class:Resource; I'll add this.

The other classes that require it and don't inherited from dcat:Resource would be dcat:Distribution and dcat:CatalogRecord

@agbeltran agbeltran self-assigned this Oct 6, 2018
@dr-shorthair
Copy link
Contributor

I was also thinking that we should list the inherited properties in the introduction to each class, and not just expect users to cross check the parent class. So the text in section 6 would better reflect how it is presented in Figure 1 in section 5.

@dr-shorthair
Copy link
Contributor

See #459

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

Successfully merging a pull request may close this issue.

3 participants