René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"XML.toString does not handle the case where JSON keys are not valid XML element names.","articleBody":"JSON key names are not as tightly constrained as XML element names - eg:\n {\"6\":\"x\",\" this has spaces and quotes\\\"!\":\"Ouch\"}\n is a valid JSON object, but XML.toString would convert this to \n\u003croot\u003e\u003c6\u003ex\u003c/6\u003e\u003c this has spaces and quotes\"!\u003eOuch\"\u003c/ this has spaces and quotes\"!\u003e\u003c/root\u003e\nWhich is not valid XML. One solution is to prefix element names which start with a digit with _ and replace other invalid characters with an _ too. Whilst this makes the resultant XML valid, meaning can be lost, so to retain the meaning an attribute could be added to provide the original JSON key name. This approach would result in the XML:\n\u003croot\u003e\u003c_6 JSON_Key=\"6\"\u003ex\u003c/6\u003e\u003c_this_has_spaces_and_quotes__ JSONKey=\" this has spaces and quotes\u0026quot;!\"\u003eOuch\"\u003c/_this_has_spaces_and_quotes__\u003e\u003c/root\u003e\n\nSee https://www.w3.org/TR/REC-xml/#NT-Name for constraints on XML element names. Note, \":\" should be replaced with another character as otherwise it could result in an element name which appears to contain a namespace prefix.\n","author":{"url":"https://github.com/imhogan","@type":"Person","name":"imhogan"},"datePublished":"2016-10-14T11:07:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/294/JSON-java/issues/294"}