This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Based on the current state of section 2.6, it looks like the JSON wire protocol intends to follow Selenium's lead and use separate URLs for each command. Since the session ID, command name, and parameters are included in each request anyway, this seems unnecessarily complex. A strictly-conforming server would be required to parse values from the URL for seemingly no other purpose than to validate the JSON payload. Perhaps it would be simpler for both clients and servers if one URL were used for all commands.
I would also like to add that it would further simplify client and server implementations if the JSON wire protocol only used the POST HTTP method. Selenium currently uses GET, POST, PUT, and DELETE, which makes it difficult to abstract clients from the underlying transport, because the HTTP method has to be specified for every command.
This was discussed at the last face to face and was decided that we will remove some of the duplication between JSON and the URL as some found that it was useful.