Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Globally unique item IDs in best practices #1157

Open
m-mohr opened this issue Oct 5, 2021 · 1 comment
Open

Globally unique item IDs in best practices #1157

m-mohr opened this issue Oct 5, 2021 · 1 comment
Labels
bug minor a relatively small change to the spec
Milestone

Comments

@m-mohr
Copy link
Collaborator

m-mohr commented Oct 5, 2021

@gsf-sellis wrote on Gitter:

The item spec says that STAC ids are only unique within a collection. But the best practices page says "...existing providers can easily use their same ID when they translate their data into STAC - they just need to be sure it is globally unique, so may need a prefix." Do STAC ids need to be globally unique or only within a collection?

I think I might have found the source of the apparent discrepancy. In the collection spec it says:

"It is important that Collection identifiers are unique across the provider. And 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."

https://github.com/radiantearth/stac-spec/blob/master/collection-spec/collection-spec.md

So in the best practices, maybe there is some conflation of the recommendation that collection ids be globally unique, while item ids have no such requirement or even recommendation?

@m-mohr
Copy link
Collaborator Author

m-mohr commented Oct 5, 2021

I think we decided on a change in one the the RCs: Collection IDs should be globally unique, Item IDs should be unique per collection. I'm pretty sure we just did not manage to update all occurances properly, so we should update the best practices.

@m-mohr m-mohr added bug minor a relatively small change to the spec labels Oct 5, 2021
@m-mohr m-mohr added this to the 1.0.1 milestone Oct 5, 2021
@m-mohr m-mohr modified the milestones: 1.0.1, 1.1 May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug minor a relatively small change to the spec
Projects
None yet
Development

No branches or pull requests

1 participant