What is needed to support STAC 1.0.0 rc.1 and rc.2?

[schwehr]

From https://github.com/radiantearth/stac-spec/blob/ee637b88c3b80bc1572c2190bbe60c3f2a3691c1/CHANGELOG.md

[v1.0.0-rc.2] - 2021-03-30

Changed

• Required properties of type string require a minimum length of 1. (#1065)
• gsd must be greater than 0. (#1068)

Removed

• The remaining extensions in the spec (EO, Projection, Scientific Citation and View) have been moved out of the core specification, into their own repos in the stac-extensions GitHub organization. They must now be referred to by their schemas directly - the name shortcuts for them are no longer valid. The concept of the 'named shortcut' also goes away entirely. (#1070)

Fixed

• Collection Assets were specified as required (only in written text, not in JSON Schema), but that was incorrectly copied over from the former collection-assets extension. Collection Assets are not required.
• Clarified that the values in summaries (both for ranges and sets of values) must follow the data type of the property they summarize. (#1069)

[v1.0.0-rc.1] - 2021-03-03

Added

• Catalog and Collection now require a type parameter, to be set to Catalog or Collection for clients to more easily distinguish them easily. (#971)
• Collection specification adds Assets (previously needed Collections Asset extension to do that). (#1008)
• 'via' and 'canonical' rel types are now options in Items. (#884)
• In Extensions list there is now reference to three new (non-core) extensions: processing, file info and card4l. These would have been added to the stac-spec repo, except all non-core extensions were moved to stac-extensions org. (#1024)
• 'summaries' are now available in the Catalog spec, so both catalogs and collections can make use of it. (#903)
• There is a new recommendation to enable CORS. (#940)
• A Best Practice section on 'requester pays' cloud buckets was added. (#1021)
• A new Best Practice section explains Asset Roles, plus some lists of potential roles for people to use (in best practices, sar and eo). (#989)
• There is a new Best Practice recommendation to keep collections at consistent levels. (#1009)

Changed

• The Stats Object for Collection summaries changed min to minimum and max to maximum to align with JSON Schema. (#967)
• URIs (usually found int properties like href, url) are now validated using the iri-reference format in JSON Schema (allows international characters in URIs) (#953)
• Enhanced the way the spec talks about ID's to encourage more global uniqueness. (#883)
• Clarified how collection-level asset object properties do not remove the need for item-level asset object properties in the item-assets extension (#880)
• Made summaries to be strongly recommended - everyone should strive to implement them, as they are very useful. (#985)
• Moved examples from individual directories into a single /examples folder at the root, and evolved them to be more representative. (#955)
• Renamed "Scientific Extension" to "Scientific Citation Extension" (#990)
• Relaxed the regular expression for DOIs in the scientific extension (#910)
• proj:geometry allows all GeoJSON geometries instead of just a polygon. (#995)

Removed

• Checksum extension (field checksum:multihash). Use File Info extension (field file:checksum) instead for assets. There's no replacement for links. (#934)
• Collection Assets extension, as the core construct of Assets in a Collection is now part of the core Collection spec. No change is required except removing collection-assets from the list of stac_extensions. (#1008)
• Numerous extensions (Data Cube, Item Assets, Point Cloud, SAR, Single File STAC, Tiled Assets, Timestamps & Versioning) have been moved out of the core specification, into their own repos in the stac-extensions GitHub organization. They must now be referred to by their schemas directly - the name shortcuts for them are no longer valid. (#1024)

Fixed

• Fixed JSON Schema for providers (Collections and Items) to be an object and require a name. (#924)

[lossyrob]

I believe I've encapsulated all the work to be done here that is not already done in #309 into individual issues with the PySTAC 1.0 label

[gadomski]

Since we now support STAC v1.0.0, this issue can be closed as completed.