Versioning Proposal (1.0.1 - 1.1 - 2.0)
The Task Force Data Processing will benefit from a somewhat stable next Version of the Schema, to make all collected mappings conform to, in one go. (rather than make them conform to 1.0 and then needing to touch them again shortly after)
One Proposal:
-
more technical and small improvements (or ones already agreed upon) like in https://gitlab.hzdr.de/hmc/hmc/cct-1-mapping/category-definitions/-/issues/33, could go into a 1.0.1 (see -> Proposal for 1.0.1). The Idea of a Version 1.0.1 is to decide on the easy fixes as soon as possible for Task Force Data Processing efforts going on right now. We probably won't need a PDF version for this.
-
Small logical changes/additions could become a 1.1
-
for the next/first publication a 2.0 as a fully revised schema is planed
The corresponding Gitlab Milestones are 2, 3 and 4:
-
2. Data is cleaned and merged into one common format While some of this could be seen as cleaning up Version 1.0, it might make sense to put some improvements that differ from the 1.0 PDF into a version 1.0.1. e.g.: some small Schema improvements beyond 1.0 where already carried out in the JSONS (see closed issues in this milestone) and should be tracket in our next Version. Not all made it into the most current Schema Word document
-
3. The schema specification is revised based on experience of data collection This right now is a (pretty full) bucket of all kinds of Schema improvement wishes. Some we might want to push to milestone 4 (v2.0).
-
4. Schema version 2.0 is published beyond HMC including associated packaged JSON schema. This is the really visionary stuff (but could be prepared)