Should we become an OGC Community Standard?

[jbants]

Background

Since STAC aligns with OGC API Features, we should make it official and become an OGC community standard. https://www.ogc.org/standards/community/#:~:text=A%20Community%20standard%20is%20an,of%20the%20OGC%20Standards%20Baseline.

Proposal

Submit OGC Community standard documents for the STAC and STAC API specifications.

https://github.com/opengeospatial/templates/blob/master/charter_templates/community_std_work_item.adoc

Additions

STAC Spec Letter https://gist.github.com/jbants/374f0cf00ad43266fb2ec34fad0b4b2b

STAC API Spec Letter https://gist.github.com/jbants/88afecbb8017f5b73a4bedfe7b9c3f53

[m-mohr]

+1

[lossyrob]

+1

[jbants]

I've added the letters as Gists. GitHub renders them nicely.

STAC Spec Letter https://gist.github.com/jbants/374f0cf00ad43266fb2ec34fad0b4b2b

STAC API Spec Letter https://gist.github.com/jbants/88afecbb8017f5b73a4bedfe7b9c3f53

[m-mohr]

@jbants One question regarding the following:

Will the contributor retain intellectual property rights?

❏ Yes

✓ No

If yes, the contributor will be required to work with OGC staff to properly attribute the submitter’s intellectual property rights.

If no, the contributor will assign intellectual property rights to the OGC.

I'm not a lawyer and legal English is not easy to understand, but are we sure we hand over intellectual property to OGC? I'm not sure we can just transfer it to OGC. It's not even 100% clear to me who has the current rights. Radiant Earth? All contributors? In both cases, we'd need official agreement from them, right? Maybe we should tick "Yes".

Also, the links to stacspec.org are relatively generic. Should we point to tagged versions of the repos?

• https://github.com/radiantearth/stac-spec/tree/v1.0.0
• https://github.com/radiantearth/stac-api-spec/tree/v1.0.0