releasing 0.5.0

[keighrim]

Overview

Release 0.5.0 includes big changes regarding how CLAMS vocabulary items are versioned. This change will help streamline version checking of I/O @types in CLAMS pipelines. It also includes more rigid validation for required fields in MMIF json.

Additions

• Some of required fields in MMIF must now have non-empty values (see #196).

Changes

• Changed IRI format of CLAMS vocabulary items
  • old format: https://mmif.clams.ai/<VERSION>/vocabulary/<TYPE_NAME>
  • new format: https://mmif.clams.ai/vocabulary/<TYPE_NAME>/<VERSION>
• CLAMS vocabulary items are now versioned independantly from the MMIF version. See comments time-stamped between Feb 2023 - Apr 2023 in these threads for discussion behind this big change:
  • https://github.com/clamsproject/mmif-python/issues/163#issuecomment-1424549083
  • https://github.com/clamsproject/mmif/issues/14#issuecomment-1439055907

[keighrim]

• There is one type with a version that is not v1 (Annotation) and it is not clear to me why that is. It was mentioned in version 04.2 that it was repurposed. But other types were changed recently too in version 0.4.0. Would dit be cleaner to have them all at v1?

Please refer to https://github.com/clamsproject/mmif/issues/14#issuecomment-1504439497 and

• Version numbers in the requirements were removed. I think we debated about this before. What is the advantage of this. A disadvantage is that new version that are backward incompatible will break our code.

The requirements are just for build.py. As long as we manually release MMIF versions by running the build.py manually, I don't believe there's anything to be broken.

[keighrim]

As I haven't heard anything for three days, I'm assuming there are no further problems. Force merging this PR to move on to work on follow-up updates on the SDK code.