Need for namespacing?

[renchap]

Right now, the spec specifies capability names, but we will probably need to have a central repository of all reserved capability names, probably with their status and a link to specification (or draft) to avoid conflicts.

Maybe we should also have them namespaced (maybe with a namespace name depending on the repository they are defined in, so we can avoid any central place?), but I am unsure if this could solve the issue.

[jmking-iftas]

edit: moving my questions to discussions

edit2: I think it would be helpful for you to kickstart such a list of reserved names so we can see your thinking and respond.

[oneiros]

This not directly related to this particular issue but with #29 we introduce a unique identifier for specifications and make it mandatory to prefix API endpoint paths with this.

With this in place we could relax the requirement for capability names to be globally unique. I am not sure we actually need to decide this now when not a single specification is finished, but that is something to keep in mind.

Of course, specification identifiers / namespaces would still need to be unique. And in some distant future a "proper" registry for those might be needed.

Until then, I hope that this repository here can serve as such. I would hope that at least in the beginning all provider specifications will find a home here.