CPS REST interface today Accepts only application/json format. The configuration from the Netconf device is read in the XML format and only having the yang schema allows to properly convert such XML into JSON (i.e. known problem of conversion of XML node(s). CPS has access to such schema, so can do properly the conversion. For the "actor" that receives the configuration in the XML format, wants to push such configuration to CPS, and has no access to the YANG schema, it is impossible today to convert such XML config to JSON format acceptable by CPS. On the other hand, if such an actor would have access to YANG schema, it is possible to write a converter on the client's side, however, such logic should be present in the CPS, which holds the yang schemas and could do the such conversion automatically.

The proposal is to support application/xml Content-Type for the endpoint that modifies the configuration of the anchor.

That story is about data creation only