-1 The only real objection is that the word "MUST" begs the question "Or else what?" Will existing components in 2.x that use non-standard URI structure not be carried into 3.x unless they're rewritten? Will new components that have non-standard URI structure be rejected out of hand, the idea being that it's better to not have endpoint access to a service than to have it through a non-standard URI? What if the non-standard nature of a component's URI reflects something native in the service it talks to, so that it's unnatural for users of said component who are familiar with the service to rework the URI to meet Camel's requirements?
I know all this is part of the "details to be worked out later", but I think these sorts of details should come sooner. Don
