)]}'
{"doc/src/docbkx/quantum-api-2.0/quantum-api-guide.xml":[{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"042a5679c6b554f8d029ace68356d38d49c674db","unresolved":false,"context_lines":[{"line_number":929,"context_line":"                response can be specified either using the"},{"line_number":930,"context_line":"                    \u003ccode\u003eContent-Type\u003c/code\u003e header, the"},{"line_number":931,"context_line":"                    \u003ccode\u003eAccept\u003c/code\u003e header or adding the"},{"line_number":932,"context_line":"                    \u003ccode\u003e.json\u003c/code\u003e extension to the request URI. \u003c/para\u003e"},{"line_number":933,"context_line":"            \u003cpara\u003e\u003c!--If conflicting formats are specified in headers and/or format extensions, the latter takes precedence. --\u003eJSON"},{"line_number":934,"context_line":"                is currently the default format for both requests and"},{"line_number":935,"context_line":"                responses. \u003c/para\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"AAAALH%2F%2FhH0%3D","line":932,"updated":"2012-09-04 22:06:19.000000000","message":"As we support JSON only, pointing out how you can specify the format seems fairly pointless, as we can just add to the options: \"You can specify no format at all and you\u0027d still be using JSON\"\n\nActually what I\u0027m considering is to remove this section at all, and state in the overview that Quantum API v2 suports JSON only.","commit_id":"a915a1ec76b561da1f5e70a4f37198d72cd1bd0c"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"d64902cb70a61eae3c3a3f070fc62eb32cc6febb","unresolved":false,"context_lines":[{"line_number":929,"context_line":"                response can be specified either using the"},{"line_number":930,"context_line":"                    \u003ccode\u003eContent-Type\u003c/code\u003e header, the"},{"line_number":931,"context_line":"                    \u003ccode\u003eAccept\u003c/code\u003e header or adding the"},{"line_number":932,"context_line":"                    \u003ccode\u003e.json\u003c/code\u003e extension to the request URI. \u003c/para\u003e"},{"line_number":933,"context_line":"            \u003cpara\u003e\u003c!--If conflicting formats are specified in headers and/or format extensions, the latter takes precedence. --\u003eJSON"},{"line_number":934,"context_line":"                is currently the default format for both requests and"},{"line_number":935,"context_line":"                responses. \u003c/para\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"AAAALH%2F%2FhHM%3D","line":932,"in_reply_to":"AAAALH%2F%2FhH0%3D","updated":"2012-09-04 22:14:55.000000000","message":"I\u0027d like to keep the section for consistency (people using other API docs will recognize it). But yes, it should strongly state json-only. I\u0027ll revise.","commit_id":"a915a1ec76b561da1f5e70a4f37198d72cd1bd0c"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"042a5679c6b554f8d029ace68356d38d49c674db","unresolved":false,"context_lines":[{"line_number":931,"context_line":"                    \u003ccode\u003eAccept\u003c/code\u003e header or adding the"},{"line_number":932,"context_line":"                    \u003ccode\u003e.json\u003c/code\u003e extension to the request URI. \u003c/para\u003e"},{"line_number":933,"context_line":"            \u003cpara\u003e\u003c!--If conflicting formats are specified in headers and/or format extensions, the latter takes precedence. --\u003eJSON"},{"line_number":934,"context_line":"                is currently the default format for both requests and"},{"line_number":935,"context_line":"                responses. \u003c/para\u003e"},{"line_number":936,"context_line":"            \u003c!--\u003ctable rules\u003d\"all\"\u003e"},{"line_number":937,"context_line":"                \u003ccaption\u003eJSON and XML Response Formats\u003c/caption\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"AAAALH%2F%2FhIE%3D","line":934,"updated":"2012-09-04 22:06:19.000000000","message":"As JSON is the only format supported I\u0027d either remove this paragraph, or explicitly state that it is the ONLY format supported.","commit_id":"a915a1ec76b561da1f5e70a4f37198d72cd1bd0c"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"d64902cb70a61eae3c3a3f070fc62eb32cc6febb","unresolved":false,"context_lines":[{"line_number":931,"context_line":"                    \u003ccode\u003eAccept\u003c/code\u003e header or adding the"},{"line_number":932,"context_line":"                    \u003ccode\u003e.json\u003c/code\u003e extension to the request URI. \u003c/para\u003e"},{"line_number":933,"context_line":"            \u003cpara\u003e\u003c!--If conflicting formats are specified in headers and/or format extensions, the latter takes precedence. --\u003eJSON"},{"line_number":934,"context_line":"                is currently the default format for both requests and"},{"line_number":935,"context_line":"                responses. \u003c/para\u003e"},{"line_number":936,"context_line":"            \u003c!--\u003ctable rules\u003d\"all\"\u003e"},{"line_number":937,"context_line":"                \u003ccaption\u003eJSON and XML Response Formats\u003c/caption\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"AAAALH%2F%2FhHI%3D","line":934,"in_reply_to":"AAAALH%2F%2FhIE%3D","updated":"2012-09-04 22:14:55.000000000","message":"Agreed. Revising.","commit_id":"a915a1ec76b561da1f5e70a4f37198d72cd1bd0c"}]}