4 ms·
Increase the terror further by adding Jsonx to the mix: http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.ibm.dp.doc/json_jsonx.html http://www.ibm.co
by manarth 10y ago
Increase the terror further by adding Jsonx to the mix: http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.ibm.dp.doc/json_jsonx.html http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com....
- arethuza 10y agoIsn't one of their examples invalid XML? http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.ibm.dp.doc/json_jsonxconversionexample.html http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.... Shouldn't <json:string name="ficoScore"> > 640</json:string> be <json:string name="ficoScore"> > 640</json:string>
- manarth 10y agoIt's one of the many peculiarities of XML: the "less-than" bracket is not allowed in text (because it could indicate the opening of a new XML tag), but the "greater-than" bracket does not need encoding when it's in text, because it's not ambiguous.
- arethuza 10y agoI'm pretty sure most XML handling libraries would use > - never seen a raw > used in XML (though possible I might not have noticed). Edit: Forgot to say thanks for pointing that out!
- benibela 10y agoJust check what the W3C says about writing a raw >: > For characters such as > where XML defines a built-in entity but does not require its use in all circumstances, it is implementation-dependent whether the character is escaped. (https://www.w3.org/TR/xslt-xquery-serialization-31/#serphases https://www.w3.org/TR/xslt-xquery-serialization-31/#serphase...)