{"action":"created","issue":{"url":"https://api.github.com/repos/alphagov/tech-and-data-standards/issues/16","repository_url":"https://api.github.com/repos/alphagov/tech-and-data-standards","labels_url":"https://api.github.com/repos/alphagov/tech-and-data-standards/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/alphagov/tech-and-data-standards/issues/16/comments","events_url":"https://api.github.com/repos/alphagov/tech-and-data-standards/issues/16/events","html_url":"https://github.com/alphagov/tech-and-data-standards/issues/16","id":134806852,"number":16,"title":"XML as an API data format","user":{"login":"pmackay","id":115115,"avatar_url":"https://avatars0.githubusercontent.com/u/115115?v=3","gravatar_id":"","url":"https://api.github.com/users/pmackay","html_url":"https://github.com/pmackay","followers_url":"https://api.github.com/users/pmackay/followers","following_url":"https://api.github.com/users/pmackay/following{/other_user}","gists_url":"https://api.github.com/users/pmackay/gists{/gist_id}","starred_url":"https://api.github.com/users/pmackay/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pmackay/subscriptions","organizations_url":"https://api.github.com/users/pmackay/orgs","repos_url":"https://api.github.com/users/pmackay/repos","events_url":"https://api.github.com/users/pmackay/events{/privacy}","received_events_url":"https://api.github.com/users/pmackay/received_events","type":"User","site_admin":false},"labels":[{"id":297915449,"url":"https://api.github.com/repos/alphagov/tech-and-data-standards/labels/API","name":"API","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-02-19T08:45:19Z","updated_at":"2017-04-25T08:35:28Z","closed_at":null,"body":"I would appreciate any input on this. If a stakeholder requests it as an supported format for an API, is that reasonable? How many APIs are being developed that include XML? Or is it considered legacy and clients should simply update to be able to process JSON?\n"},"comment":{"url":"https://api.github.com/repos/alphagov/tech-and-data-standards/issues/comments/296959799","html_url":"https://github.com/alphagov/tech-and-data-standards/issues/16#issuecomment-296959799","issue_url":"https://api.github.com/repos/alphagov/tech-and-data-standards/issues/16","id":296959799,"user":{"login":"g-ling","id":5887311,"avatar_url":"https://avatars3.githubusercontent.com/u/5887311?v=3","gravatar_id":"","url":"https://api.github.com/users/g-ling","html_url":"https://github.com/g-ling","followers_url":"https://api.github.com/users/g-ling/followers","following_url":"https://api.github.com/users/g-ling/following{/other_user}","gists_url":"https://api.github.com/users/g-ling/gists{/gist_id}","starred_url":"https://api.github.com/users/g-ling/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/g-ling/subscriptions","organizations_url":"https://api.github.com/users/g-ling/orgs","repos_url":"https://api.github.com/users/g-ling/repos","events_url":"https://api.github.com/users/g-ling/events{/privacy}","received_events_url":"https://api.github.com/users/g-ling/received_events","type":"User","site_admin":false},"created_at":"2017-04-25T08:35:27Z","updated_at":"2017-04-25T08:35:27Z","body":"Where I work, we use XML message payloads in SOAP based web services all the time. Even on new services. When we discuss interface API with external 3rd parties XML is usually the most commonly offered option. Typically always validated against .xsd schema. I get comfort in using SOAP/XML as it has a rich tool set and standards that are still widely used as 'rossjones' mentions above.  However I also like REST/JSON for internal API's as they are quicker to pull together. We are recently considering publishing both XML & JSON API's.  The coding tech thats available these days make it almost trivial to consume either XML, JSON, YAML, etc, its really does not matter too much.\r\nWhat I'm hoping will come from this site is some finer guidance on the construction of  API's. In the absence of such I Google best practices. \r\nLiving in hope of some good clear standards to emerge - if JSON is king then please define example structures to allow wider usage and clear understanding. Same for SOAP/XML. "}}
{"actor":{"display_login":"g-ling"}}