Further Stac 1.0.0 changes could be added

[jeremyh]

From reading the release notes, these are things to investigate:

(many of these will go upstream to eodatasets, rather than here, as it does the Item conversion for us)

Item

• datetime is nullable, falling back to start/end
• allow null geometry
• map file:size and checksum from eo: https://github.com/stac-extensions/file
• 'canonical' rel type
• 'via' rel type
• More asset roles: https://github.com/radiantearth/stac-spec/blob/master/best-practices.md#asset-roles
• processing:level etc? https://github.com/stac-extensions/processing
• New provenance possibilities: link rel derived_from
• Extensions specified as URLs, not names.
• Specify 'Providers' identities better?
• link rel=preview
• " include both root and parent when pointing at the same file"

Catalogs/Collections

• Multiple extents (bounding boxes / intervals) are allowed per Collection?
• Stats Object for Collection summaries changed min to minimum and max to maximum
• Catalog and Collection now require a type parameter, to be set to Catalog or Collection for clients to more easily distinguish them easily.
• Collection assets specification
  • - link to related files, like the ODC product def?
• Catalog layout best-practices: https://github.com/radiantearth/stac-spec/blob/master/best-practices.md#dynamic-catalogs
• link rel=preview too?
• extensions in collections
• changed, created (common metadata) and temporal extents (collections): Timestamps must be always in UTC

Maybe

• Review how we name collections?

providers should strive as much as possible to make
their collection ids 'globally' unique, prefixing any common information with a unique string. This could be the provider's name if
it is a fairly unique name, or their name combined with the domain they operate in.

• Proj:geometry? We do technically have that info...
• 'null' is different to leaving out the field entirely. Check our usage.
• include title in links where possible