Page History

...

// xPath: /ran-network/NearRTRIC[@idNearRTRIC='11']/GNBDUFunction[@idGNBDUFunction='1']/NRCellDU[@idNRCellDU='103594001']/attributes
{
   "pLMNInfoList": [{
	   "mcc": "310",
       "mnc": "410",
       "sNSSAIList": [{
            "sNssai": "10000100",
            "status": "INACTIVE",
            "configData": [{
                "configParameter": "maxNumberOfConns",
                "configValue": 5000
            }]
        }]
    }]
}

...

As it was initially implemented there is no validation for parent data node existence when persisting data nodes. draw.io DiagramborderfalsediagramNameCPS partial data persistencesimpleViewerfalsewidthlinksautotbstyleinlinediagramDisplayNamelboxfalsediagramWidth871revision2

It is unnecessary when the whole data tree is persisted (A) because there is a data for all the levels with no gaps. 
With non-empty initial xpath it makes it possible to persist data nodes from lower levels of structure hierarchy without upper
level data nodes (B). 

From one hand it seems extra to persist upper level nodes if these nodes are never requested. From other hand it could lead to data inconsistency
if the parent node being added after child nodes (C). The case  however can be resolved by existing data check before inserting new entries.

...

• using parent xpath for insert only, direct xpath for update 
• using parent xpath for insert and update operations

The naming and default value for an option (boolean type of) to instruct the descendants update together with the data node.
The option used for data extraction is called include-descendants, false by default. same to be defined for data update operation:
is it to have same name, what's the default value. 

Also using cps-path name for xpath parameter is misleading and confusing, it needs an agreement either to leave as is or
use xpath instead.

Allowing data node persistence without a parent data nodes. Options:

...