RESTConf defines 'fields' and 'depth' parameters to control the output of a get or query request.

See https://tools.ietf.org/id/draft-ietf-netconf-restconf-07.xml and https://datatracker.ietf.org/doc/html/rfc8040#section-4.8.3

See complex example from REST Interface Definition:

/ncmp/v1/ch/335ff/data/ds/ncmp-datastores:passthrough-running?fields=_3gpp-common-managed-element:ManagedElement/_3gpp-nr-nrm-gnbcucpfunction:GNBCUCPFunction(pLMNId;gNBId;gNBIdLength)&topic=anr-app:anr24234234:v2

 NCMP and DMI_plugin will both need to support these parameters eventually as consistent as possible independent of the underlying infrastructure and protocols.

This study needs to consider

1. The capabilities of both parameters as defined by RESTConf
2. The support (limitations?) of both parameters as implemented by the 'rests' ODL module interface (SDN-C) - Dependent on CPS-463
3. The feasibility/cost of NCMP 'translating' a fields-option without module information into a RESTConf compatible fields value. High level user story view of cost.
4. The feasibility/cost of support a 'fields' parameter for CPS cached data and/or ONAP DMI Plugin
   High level user story view of cost.
5. The feasibility/cost of support a 'depth' parameter for CPS cached data and/or ONAP DMI Plugin
   High level user story view of cost.

A/C

• Add to existing wiki (possible childpages or new parent page created by tragait )  with with findings on above -https://wiki.onap.org/display/DW/CPS-395+Spike%3A+SDNC+Interface+for+CRUD+and+Patch+Operations
• Share wit team