JSONtoXML policy suggesting "_" as default for InvalidCharsReplacement?

Google Cloud Apigee
1

What is the reasoning behind the JSONtoXML policy suggesting “_” as the default for when underscores are not valid in a tag name (except in the beginning)?

https://www.w3.org/TR/2008/REC-xml-20081126/#NT-NameChar

(Generally speaking, I miss a more “intelligent” (optional) schema mapping. For example, how about CamelCase to hyphen-case etc.)

2

I don’t have the reasoning behind that. Sorry I Cannot give you much of an answer.

As for mapping between camelCase, Hyphen-Case, and PascalCase… that’s an interesting feature request. Until now I’ve seen people do that themselves with their JSON , using a JavaScript policy.

1 Like