Page History

...

1. name =  dataspace  [ + anchor-name ]      We will need some token to separate them e.g. |
   1. &name=xnfProxy
   2. &name=xnfProxy|nodeInAthlone
   3. &dataspace=xnfProxy&anchor-name=nodeInAthlone
      
      (we still have the issue of naming the parts in documentation and in error scenarios ie. if the 'dataspace' does not exist but maybe its OK to us that term then)
2. uuid = unique id (generated by the DB). This wil eb be useful to share an 'instance' with other applications without having to share dataspace name
   1. &uuid

...

GET <server>/cps/v1/nodes?name=xnfproxy|nodeInAthlone&xpath="..."

(the same can be used for PUT and DELETE operations)

GET <server>/cps/v1/dataspaces/{dataspace_id}/anchors → returns Anchor-points

GET <server>/cps/v1/dataspaces/{dataspace_id}/anchors/{anchor-point-id}/nodes?xpath="..."  → returns Node(s)If we also support getting trees (more then one level) I'm note sure if we need another url or another parameter

GET <server>/cps/v1/node-trees?name=xnfproxy&xpathdataspaces/{dataspace_id}/anchors/{anchor-point-id}/nodes?schemaNodeIdentifier="..."  → returns Node(s)

GET <server>/cps/v1/dataspaces/{dataspace_id}/nodes?name=xnfproxy&includeChildrenLevels=3&xpath="..." → returns Node(s)

(the same can be used for PUT and DELETE operations)

getting modules seems straight-forward enough:

...