[JSONRPC-22] Support for alternative RFC8040 style path notation Created: 16/Aug/18 Updated: 16/Aug/18 |
|
| Status: | Open |
| Project: | jsonrpc |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Anton Ivanov | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
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. |