Support for alternative RFC8040 style path notation

The world has won. While our path notation has some clear benefits (especially for loosely typed languages) in the long term we should converge to a subset of one of the existing specs. I propose the path part of RFC8040 (we can still supply entity, store, etc as separate parameters as now so this is just path).

Open questions are model representation and configuration/version negotiation.