clarify how schemes are implemented as summaries

[tylanderson]

Schemes are represented as Map<string, Storage Scheme Object>, while summaries are a list of distinct values, range, or json schema.

There aren't many great examples of mappings represented in summaries AFAIK (maybe a separate issue to raise in STAC spec), so curious if anyone has thoughts on what the intended way to represent storage schemes summaries is.

I was thinking it would look like a list of entries, e.g.:

"summaries": {
    "storage:schemes": [
      {
        "aws": {
          "type": "aws-s3",
          "platform": "https://{bucket}.s3.{region}.amazonaws.com",
          "bucket": "mybucket",
          "region": "us-west-2",
          "requester_pays": true,
          "tier": "Standard"
        }
      }
    ]
  }

[m-mohr]

Hmm, this case didn't came up for me yet because we have the storage:schemes on the top-level in the collection already as we use it also for some collection assets. Then it doesn't make a lot of sense to add them to summaries, too.

Your example seems to be correct though.

[tylanderson]

Yeah this came up during implementation of the pystac extension. I'd expect summaries are the less common way to do this, over adding to collections, but as the extension spec supports it I wanted to confirm behavior