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

Should dcterms:creator be mandatory? #108

Open
Tracked by #114
tpluscode opened this issue Oct 18, 2023 · 3 comments
Open
Tracked by #114

Should dcterms:creator be mandatory? #108

tpluscode opened this issue Oct 18, 2023 · 3 comments

Comments

@tpluscode
Copy link
Contributor

For visualize, the cube requires the presence of dcterms:creator in addition to schema:creator

Is that property only required in that context? @l00mi
Maybe we need a profile for visualize with this and other extensions? @Rdataflow

@tpluscode
Copy link
Contributor Author

Cube Creator added that validation to its shape by requiring that schema:creator equals dctems:creator

@Rdataflow
Copy link
Contributor

Maybe we need a profile for visualize with this and other extensions? @Rdataflow
💯 we need such kind of checks automated.
adrian mentioned 3 validation profiles and I agree on this.

  • cube.link spec conformity
  • opendata.swiss conformity (incl. cube.link)
  • visualize conformity (incl. opendata.swiss)
    @tpluscode would you take this?

cc @MartinaElsawy @ClaudioDiGallo you may follow this here https://gitlab.ldbar.ch/bafu/visualize/-/issues/564

@Rdataflow
Copy link
Contributor

Cube Creator added that validation to its shape by requiring that schema:creator equals dctems:creator

  • 💯 would be good to have this check in validation
  • can we keep all the relevant validation in 1 place (once only) and reuse it from there i.e. in cube-creator? - else we will suffer diversity in validation 🙃

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

2 participants