Comparison of current CPS core output to NCMP passthrough operation output
The following details were used to compare and analyze the current CPS core output to NCMP passthrough operation output
Model | bookstore.yang |
---|---|
Data | bookstore.json |
CPS core endpoint | /v1/dataspaces/{dataspace-name}/anchors/{anchor-name}/node |
NCMP Passthrough operation | /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-running |
Scenario 1: XPath is pointing to root i.e. '/' | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
NCMP Passthrough operation output | CPS Core output | |||||||||||
Response |
| |||||||||||
Scenario 2: Container XPath i.e '/bookstore' | ||||||||||||
NCMP Passthrough operation output | CPS Core output | |||||||||||
Response |
|
| ||||||||||
Scenario 3: List attributes XPath '/bookstore/categories[@code='02']' '/ncmp/v1/ch/PNFDemo/data/ds/ncmp-datastore:passthrough-running?resourceIdentifier=stores:bookstore/categories=02' | ||||||||||||
NCMP Passthrough output | CPS Core output | |||||||||||
Response |
|
|
Modifying CPS Core output
Parsing a model prefix
Building the data node
Open Issues
Issue | Description | Resolution |
---|---|---|
Child is in a different module | If the child is in a different module should it have a prefix | |
Output starts with non-root element | If the output starts with non-root element should it have a prefix | |
Backward incompatibility | Discuss backward incompatibility with stakeholders
Can YangTools parse it?
| |
Is this LEGAL YANG dataCan YangTools parse it? |