There has been talk of a next version on slack, it is time to make this more official. The proposed new version will be 1.6 (following the existing convention of even number as production).
Note the purpose and scope is not to try and add expressivity to match OWL. It is to clarify unclear parts of the spec, correct errors, and to add additional features that are very high priority for groups that use obo format as the edit format. Note that consumers should not use obo format, and instead use obograph json or owl.
Tasks:
[x] create 1.4 and 1.6 labels in this repo and issue templates
[ ] translate @balhoff's google doc into issues tagged with new labels
[ ] ensure WG is all on #obo-format on slack
[ ] create a stub page for 1.6 and stub diffs
[ ] decide on whether to maintain a .html file as SOT
[ ] repo hygiene. We are using gh-pages as main for legacy reasons. Continue?
There has been talk of a next version on slack, it is time to make this more official. The proposed new version will be 1.6 (following the existing convention of even number as production).
Note the purpose and scope is not to try and add expressivity to match OWL. It is to clarify unclear parts of the spec, correct errors, and to add additional features that are very high priority for groups that use obo format as the edit format. Note that consumers should not use obo format, and instead use obograph json or owl.
Tasks:
#obo-formaton slack