Create a generic 'dataset' / 'collection' specification, and use that to replace 'root catalog' concept.

[cholmes]

There was lots of good discussion at STAC sprint 3 and continuing in github after on collection / dataset level metadata.

Not everything is 100% sorted out, but we're homing in on a some good consensus.

The 'dataset' specification will be a more formal definition of the descriptive fields of the catalog (defined by the static catalog in the first sprint, and not really revisited much). This will be its own mini-spec, in its own folder, and other projects like GEE and OpenEO will be able to reuse it. The bulk of this work is being done right now in #164

This will likely replace the 'root catalog' concept in the static catalog, which was the idea that an item would link to the catalog that had meaningful information about it, instead of just the catalog organization that's immediately above it.

This will likely also obviate the need for the collection extension, so #174 may just result in removing it, if dataset covers all the needs of it.

Related issues + PR's
#81 #164 #35 #152 #137

[hgs-msmith]

I've attached a UML diagram as an attempt to summarize the different metadata model approaches we have discussed. We can use this during today's (9/24/18) conference call.

STAC-model.pdf

[hgs-msmith]

Here is an updated model - my attempt to incorporate the discussion during the 9/24/18 conference call.
STAC-model-060.pdf

[m-mohr]

Thanks.
Why is contact, provider etc still in the catalog? That's not the current state AFAIK. The catalog should just hold name, description and links (and properties?!). All the additional fields in catalog belong to the dataset, at least in my proposal.

[hgs-msmith]

Updated version, reflecting changes as of 11:00am EDT 10/2/18.
STAC-model-060.pdf

[m-mohr]

"Migrated" from the chat: The model from @hgs-msmith is up-to-date with two minor exceptions:

• license was moved from catalog to dataset
• provider and license are removed from the properties.

[m-mohr]

By the way, we may need/want to update the extents object later, see opengeospatial/ogcapi-features#168

[hgs-msmith]

Here is an updated diagram with the changes noted by @m-mohr:
STAC-model-060.pdf

and +1 on pressing the extents updates with WFS.

[hgs-msmith]

Finally, when we are settled on the final 0.6.0 model, let's find a better place to this diagram.

[m-mohr]

Agreed - and this diagram will need some more work for the final 0.6.0 release (stac_version added to dataset, type added for provider, ...)

[cholmes]

Closing, as I think this is all in.