json-rpc "show_config" command ("path": "/devices/device/{csr1}/config/ios:interface/GigabitEthernet/{2}") gives out the following response. at least for me it's hard to parse. so my questions are: 1) is there an easy way to parse it? 2) is there a way to get a relatively easy-to-parse response through json-rpc? thanks { "jsonrpc": "2.0",   "result": {     "config": "devices {\n    device csr1 {\n        config {\n            ios:interface {\n                GigabitEthernet 2 {\n                    negotiation {\n                        auto true;\n                    }\n                    ip {\n                        address {\n                            primary {\n                                address 192.168.10.2;\n                                mask    255.255.255.0;\n                            }\n                        }\n                    }\n                    load-interval 30;\n                    service-policy {\n                        input  pm-GigabitEthernet2-in;\n                        output audi101-pm_ds-parent;\n                    }\n                }\n            }\n        }\n    }\n}\n"   },   "id": 1 } ... View more

i know nso or pyang does yang parsing as a routine job, but how to do it in my own code? e.g. based on the parsing result, generate my own output (i'm aware of pyang's -f output format options) - such as a html form to gather user input (almost the same work done by nso web ui). thanks for any tips ... View more