astefanutti commented on issue #2158: URL: https://github.com/apache/camel-k/issues/2158#issuecomment-805597544
Another case against `/` and `:` interchangeability, is that it increases complexity of equality comparison. We used to support it for dependency references, but that led to duplicated entries issues. Sooner or later, that increased complexity causes issues, as it's been forgotten to normalise before comparing or hashing. So I went ahead and removed it for dependencies (#1903). Generally, `:` carries the semantic of "logical unit" separator, while `/` carries path-like or scoped-like semantic in tree-like structures. For the namespace, it seems there is a consensus it's a path / scope, applied to the resource location "unit", hence, if we follow the above generality, should be followed by `/`. For the type, it is less obvious to find a consensus in all the places that re-surface its serialised forms. As @johnpoth pointed out, you have `kubectl get integrations.camel.apache.org/name`. If we consider the API server REST contract as the source of truth, that command translates to the following request: ``` GET /apis/camel.apache.org/v1/namespaces/camel-k/integrations/name ``` Which is a serialised form of object reference! So maybe `[group[/version]/][namespace/]kind/name` is a solution :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
