Release v2.0.0

[gadomski]

The main changes are

• relaxing a required field to non-required (pc:schemas)
• removing a field (pc:encoding)

Related issues

• Closes what is acutally needed for pc:schemas  #13

[m-mohr]

because [...] it is allowed to have fields w/ a pc: prefix that aren't in the extension.

That is not correct. Unknown pc: prefixed fields will be reported as invalid. @gadomski

[gadomski]

Alrighty, then should be v2.0.0. Thanks @m-mohr I'll update.

[m-mohr]

Generally, the schema could be updated to a better version that we use in some other extensions. I'm not sure it's in the template extension yet, but if you go 2.0.0 preferrably also improve the schema ;-)

[gadomski]

Generally, the schema could be updated to a better version that we use in some other extensions. I'm not sure it's in the template extension yet, but if you go 2.0.0 preferrably also improve the schema ;-)

Ok, I'll hold off on merging and see if I can get some time to update the schema 👍🏼

[m-mohr]

Here's a recent example of a "better" schema ;-)
https://github.com/stac-extensions/eo/blob/9dfcf270dbd210e74ee1e06a15c50beedc2e3b5d/json-schema/schema.json

[gadomski]

@m-mohr I did my best to ape the EO extension into the jsonschema, but full disclosure I don't play in jsonschema much so mistakes are quite possible. If you have time to take a look I'd appreciate 🙇🏼 .

[m-mohr]

The CI tests fail, could you fix those first? :-)
Or any specific issues I should look at?

[gadomski]

The CI tests fail, could you fix those first? :-)

Yeah, I'm flailing around now — please ignore, I'll ping again when I get things green 🙇🏼 .

[gadomski]

@m-mohr did my best to update the schema using the "better" version, so ready for re-review (finally).

[m-mohr]

Oops! In the meantime I created an even better version 😅 (sorry!)
https://github.com/stac-extensions/eo/blob/main/json-schema/schema.json
or
https://github.com/stac-extensions/raster/blob/main/json-schema/schema.json
I still need to generalize it for the template repository though.

It uses if/else instead of oneOf which makes the error reporting in JSON Schema less confusing to read and actually correctly validates fields "everywhere". Before it sometimes happened that parts were not validated.

[gadomski]

@m-mohr ok I've updated with The New Way, and added some more tests (for assets and item assets, respectively).

[m-mohr]

Should the count in pc:statistics have a minimum value of 0 or 1?

Otherwise LGTM.

[gadomski]

Should the count in pc:statistics have a minimum value of 0 or 1?

It could be a zero point file, that's allowed by most formats, so 0 seems right.

[m-mohr]

@gadomski Yes, but there was NONE defined. I'm not talking about pc:count, but about pc:statistics.count!

[gadomski]

Whoops. I'll open an issue, thanks!