)]}'
{"doc/arch-design/hybrid/section_user_requirements_hybrid.xml":[{"author":{"_account_id":4656,"name":"Sean M. Collins","email":"sean@coreitpro.com","username":"scollins"},"change_message_id":"5c238bac5718a9c226b53288b482734199be5e87","unresolved":false,"context_lines":[{"line_number":104,"context_line":"        xlink:href\u003d\"http://www.finra.org/Industry/Regulation/FINRARules/\"\u003eFINRA Rules\u003c/link\u003e)"},{"line_number":105,"context_line":"        in the United States. Consult a local regulatory body for more"},{"line_number":106,"context_line":"        information.\u003c/para\u003e"},{"line_number":107,"context_line":"    \u003c/section\u003e"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"    \u003csection xml:id\u003d\"workload-considerations\"\u003e"},{"line_number":110,"context_line":"      \u003ctitle\u003eWorkload considerations\u003c/title\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"1a4dcd0f_594d0bc3","side":"PARENT","line":107,"updated":"2015-08-14 19:09:54.000000000","message":"I\u0027d like to see the reason why this was removed in the commit message. \"Cleanup \u003cfile path\u003e\" is not sufficient","commit_id":"79d32c660775e09ff9389140eeb622022c6b9799"},{"author":{"_account_id":10497,"name":"KATO Tomoyuki","email":"kato.tomoyuki@jp.fujitsu.com","username":"to222"},"change_message_id":"32dd18af28fd6596b064a3d6c8046178c8ad9bd5","unresolved":false,"context_lines":[{"line_number":78,"context_line":"      potential conflicts, complexity, and platform"},{"line_number":79,"context_line":"      incompatibilities.\u003c/para\u003e"},{"line_number":80,"context_line":"    \u003cvariablelist\u003e"},{"line_number":81,"context_line":"      \u003ctitle\u003eUse cases for a hybrid cloud architecture include\u003c/title\u003e"},{"line_number":82,"context_line":"      \u003cvarlistentry\u003e"},{"line_number":83,"context_line":"      \u003cterm\u003eDynamic resource expansion or bursting\u003c/term\u003e"},{"line_number":84,"context_line":"        \u003clistitem\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"1a4dcd0f_a71e980b","line":81,"updated":"2015-08-14 00:48:00.000000000","message":"This looks strange to me as title. How about simply \"\u003ctitle\u003eUse cases for a hybrid cloud architecture\u003c/title\u003e\"?","commit_id":"501bbe47994c268b21abde8740639e6dad40917f"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a7868a85584ccdb465959df2bf899043aec78e8f","unresolved":false,"context_lines":[{"line_number":78,"context_line":"      potential conflicts, complexity, and platform"},{"line_number":79,"context_line":"      incompatibilities.\u003c/para\u003e"},{"line_number":80,"context_line":"    \u003cvariablelist\u003e"},{"line_number":81,"context_line":"      \u003ctitle\u003eUse cases for a hybrid cloud architecture include\u003c/title\u003e"},{"line_number":82,"context_line":"      \u003cvarlistentry\u003e"},{"line_number":83,"context_line":"      \u003cterm\u003eDynamic resource expansion or bursting\u003c/term\u003e"},{"line_number":84,"context_line":"        \u003clistitem\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"1a4dcd0f_19b24c07","line":81,"in_reply_to":"1a4dcd0f_a71e980b","updated":"2015-08-14 02:43:36.000000000","message":"+1","commit_id":"501bbe47994c268b21abde8740639e6dad40917f"}]}