...
<OP>/ncmp/<v{vNumber}>/ch/<cmHandle>/<data|operations|{ncmpAction}>/ds/{datastore}/[rp:]{resourcePath}?{query}
Below table shows the proposed interface. actual implementation might deviate from this but can be acces in
| URI | Mandatory or Optional | |
|---|---|---|
| <OP> | the HTTP method | Mandatory |
| ncmp / | the ncmp root resource | Mandatory |
| <v{vNumber}> | version of the ncmp interface <path> is the target resource URI <query> is the query parameter list | Mandatory |
| ch/<cmHandle> | unique (string) identifier of a yang tree instance. | Mandatory |
| <data|operations|{ncmpAction}> | request category - yang data, rpc operation or a (non-modelled) ncmp api action. this could be data, operations or ncmpAction (e.g. 'sync-data') | Mandatory |
| ds/{datastore} | Mandatory | |
| <resourcePath> | the path expression identifying the resource that is being accessed by the operation. If this field is not present, then the target resource is the API itself. | Optional |
| <query><options> | Parameters with the familiar form of "name=value" pairs. Query parameters are optional to implement by the server and optional to use by the client. Each optional query parameter is identified by a URI | Optional DMI should be able to support (/pass through) ANY parameter associated with the RESTCONF message; see Section 3.4 of [RFC3986]. |
...