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

Controlled vocabularies are defined in several places #127

Open
mortenwh opened this issue Jan 8, 2021 · 5 comments
Open

Controlled vocabularies are defined in several places #127

mortenwh opened this issue Jan 8, 2021 · 5 comments
Milestone

Comments

@mortenwh
Copy link
Collaborator

mortenwh commented Jan 8, 2021

  • chapter 4 in the documentation
  • files in the thesauri folder
  • under xs:simpleType in the xsd/mmd.xsd file

I suggest to write some tests to check that the definitions are internally consistent.

@steingod
Copy link
Collaborator

steingod commented Feb 1, 2021

Sounds like a good idea. Not sure how to do this across these sources though?

@mortenwh mortenwh added Epic and removed Epic labels Feb 2, 2021
@mortenwh
Copy link
Collaborator Author

mortenwh commented Feb 2, 2021

That should be possible. Maybe not easy and may require some coding but I think it would be useful to integrate it in the CI. I'll add it to the S-ENDA backlog, then we can see. Probably not highest priority at the moment, though..

@steingod
Copy link
Collaborator

Agree

@mortenwh
Copy link
Collaborator Author

mortenwh commented May 4, 2021

@TAlonglong - I took this one out of the May sprint. It is too complicated to solve in one go now.

@mortenwh mortenwh added this to the Full project milestone Jun 1, 2021
@ferrighi
Copy link
Collaborator

I suggest to begin with keeping only the thesauri/mmd-vocabulary.ttl as reference and use a git action to generate mmd-vocabulary.xml (as we do for adoc->html/pdf). This can be done with rdflib. I can test this a bit. For the schema, we should probably remove the vocab list from that and import valid vocabularies from the ttl/xml. So we keep the schema formally validating the structure and the vocabulary to validate the content.

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

4 participants