The spec currently requires that the model_id be unique "across the provider", but there is not guarantee that it be globally unique. This could lead to confusion if different models have identical IDs in a few different model repositories, or if the same model has different IDs in different repos in order to avoid a conflict with another model. Requiring a UUID as the model_id would effectively guarantee global uniqueness and would mean that the same ID could be reliably reused across multiple providers to reference the same model.
This issue exists to encourage discussion regarding the pros and cons of requiring a globally unique model_id. If there is consensus that this change should be made we will update the Proposal section with a proposed implementation.
Proposal
TBD
originally posted by @duckontheweb
Comment
Could the URI be the golbally unique identifier instead?
Problem Description
The spec currently requires that the model_id be unique "across the provider", but there is not guarantee that it be globally unique. This could lead to confusion if different models have identical IDs in a few different model repositories, or if the same model has different IDs in different repos in order to avoid a conflict with another model. Requiring a UUID as the model_id would effectively guarantee global uniqueness and would mean that the same ID could be reliably reused across multiple providers to reference the same model.
This issue exists to encourage discussion regarding the pros and cons of requiring a globally unique model_id. If there is consensus that this change should be made we will update the Proposal section with a proposed implementation.
Proposal
TBD
originally posted by @duckontheweb
Comment
Could the URI be the golbally unique identifier instead?