Switched to YAML for the vocab definition #954
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just a technical PR with no difference in the generated content for the vocabulary. The PR aligns the VCDM vocabulary generation structure to that of the data integrity one.
The generation uses now the separate tool. Apart from sharing a tool with the security vocab, YAML is now used as the format to define the vocabulary itself. YAML is (much!) easier to edit than CSV. I do not rely on any fancy feature of YAML (like cross references), just the basic stuff. The YAML file of the vocabulary is the file that should be modified whenever the vocabulary has to be changed.