Updates to lower versions of extension such as 1.2.0 or 1.1.1

[bkavlak]

Hey people,

We still couldn't migrate to STAC 1.1.0 and therefore cannot use EO 2.0.0.

But we need rededge071 and rededge075 band names, which are only released in EO 2.0.0 but not available in EO 1.1.0.

Migrating to STAC 1.1.0 requires some planning on our end, and we need to cover bands rededge071 and rededge075 for users. We are thinking about hosting an EO 1.1.1 version, appending these bands to the common names.

We wonder if it would make sense to add this here or host it in a UP42 domain. What would be your take on this?

[m-mohr]

Nothing really prevents you from using EO 2.0.0 in STAC 1.0. You may not get validation in the old eo:bands, but it's never "full" validation anyway due to JSON Schema limitations.

Creating a new eo-like extension is not a good idea, IMHO.

[bkavlak]

@m-mohr thanks for the responses!

I get the following error if I add EO 2.0.0 and use the old way

jsonschema.exceptions.ValidationError: 'eo:bands' does not match any of the regexes: '^(?!eo:)'

[m-mohr]

Oh, shoot. Yeah, that's true. So maybe it's easier to release a 1.2.0 that contains the new common band names....

[bkavlak]

Shall I send a PR? I believe it wouldn't be in the main branch, but rather in the gh-pages branch?

[m-mohr]

I just created a new branch v1.2.0 based on the v1.1.0 tag. It currently is the content v1.1.0, but we'd need a PR that updates the branch to include all changes needed for v1.2.0. Once the PR is merged, we can issue a release through GitHub releases.

[bkavlak]

here is an attempt #40