Yes and that is why the linked post and this post itself are bad. Both authors do not understand the principles of an URI in the context of the web. To a clien

Yes and that is why the linked post and this post itself are bad. Both authors do not understand the principles of an URI in the context of the web. To a client, the URI should be opaque. If a client has to start to make meaning of the contents of an URI, the server loses the ability to change its implementation (or just move resources around). Edit: Ah, its the same author for both blog posts. That explains it.