...
- the naming convention for ease of parse/ store/ query by XPath
- using indexes in XPAth like /node[0] if no keys defined in model
- ordering multiple keys for composite key models on storage and requests
or alternative approach for unique node type definition (in CPS XPath) with taking into account YANG models variations
Discussion results
For now there is no need to store full module identifier in the xpath field. The namespace, revision, parent module context will be taken
into account using references through dedicated fields (module_id, parent_id).
Limitation determined: only keyed collections are supported. No node identification by index is expected.
The attribute order for composite keys to be handled as dedicated task.
Both requested xpath and stored one expected to sort key attributes by attribute (leaf) name