Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • I don't even want to use XML if it was not because our users use XML rather than JSON. I'm also considering a JSON version for this as an alternative and for the future organizations that would need integration between their system to our system. Commented May 19, 2017 at 1:16
  • 1
    @rpmansion Right I saw your reason for using it which is why I gave you my recommendations. If you want to create a JSON version of this, you might want to start with JSON and then back-port it to XML. JSON is more syntactically simple (which is it's advantage in this case.) It's possible to build XML structures that cannot be directly translated to JSON or are awkward. Being a little passive-aggressive about it and pointing out that you have XML simply to support 'old' ways of doing things is probably OK here. Commented May 19, 2017 at 14:55