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

rcc.ttl is all wrong #4

Open
VladimirAlexiev opened this issue Oct 7, 2020 · 2 comments
Open

rcc.ttl is all wrong #4

VladimirAlexiev opened this issue Oct 7, 2020 · 2 comments

Comments

@VladimirAlexiev
Copy link

VladimirAlexiev commented Oct 7, 2020

Continuing the examination from #3:

  • again the : prefix is missing, so rcc.ttl is invalid
  • what's the purpose of using xsd:anyURI literals rather than actual URIs?
  • You say :Catalog :dataset :dataset481, :dataset_x001 but you have not defined such property. Thinking about dcat: doesn't magically bring its props into your namespace
  • You say :Corpus :publication :publication338, :publication340 but you have not defined such property

We've done significant work in KGs of Science so the following recommendations come from that experience:

  • authors and publications: use separate props to capture identifiers in important datasets like ORCID, DOI, Google Scholar, ResearchGate, Scopus. Eg Wikidata has external-ids for all of that
  • publications: use some established bibliographic ontology, don't just wing it with dc/dct
  • If you use DCT for a bunch of props, why suddenly switch to PAV for pav:createdOn? Use dct:created
  • dct:alternative is declared subprop of dct:title, so you'll get two dct:title: "National Health and Nutrition Examination Survey" and "NHANES", is that what you want?
@VladimirAlexiev VladimirAlexiev changed the title rcc ontology is all wrong rcc.ttl is all wrong Oct 7, 2020
@Juliaingridlane
Copy link

Juliaingridlane commented Oct 7, 2020 via email

@el2727
Copy link

el2727 commented Oct 8, 2020

Dear Vladimir,

Thank you very much for your very helpful comments, we reviewed, and noted them for the future development.

Thank you again.

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

No branches or pull requests

3 participants