-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
Sounds like a good idea. Not sure how to do this across these sources though? |
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.. |
Agree |
@TAlonglong - I took this one out of the May sprint. It is too complicated to solve in one go now. |
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. |
thesauri
folderxs:simpleType
in thexsd/mmd.xsd
fileI suggest to write some tests to check that the definitions are internally consistent.
The text was updated successfully, but these errors were encountered: