<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title></title><style type="text/css">.felamimail-body-blockquote {margin: 5px 10px 0 3px;padding-left: 10px;border-left: 2px solid #000088;} </style></head><body>Am 23.07.2012 15:04:07, schrieb Robert Kisteleki: <blockquote class="felamimail-body-blockquote"><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title></title><style type="text/css">.felamimail-body-blockquote {margin: 5px 10px 0 3px;padding-left: 10px;border-left: 2px solid #000088;} </style>On 2012.07.18. 15:45, Matija Grabnar wrote: > On 07/18/2012 03:08 PM, Leo Bicknell wrote: >> To that end, if RIPE could produce a template/example in a few popular >> languages (perl, python, ruby, php) to download the JSON and parse into >> the native language data structure that could get a LOT more folks using >> the data... >> > > You can fins a bunch of decoders in more languages than I count on > <a href="http://www.json.org/" target="_blank">http://www.json.org/</a> Hi, It's really nice to see the community in action :-) It is a rather encouraging sign to us! To answer Leo's original question from a different perspective: the result data you get from Atlas is a structured piece of information. We had to choose a specific encoding, and we opted for JSON (as opposed to YAML, XML, etc.) because in many cases that can be directly used in client side applications. We *could* supply other formats too, but no matter what the encoding is, you need some kind of client library to parse it. </blockquote> In my opinion, JSON is the best solution as it is strictly UTF-8 (yes, no garbled characters, anymore!) and either server-side PHP-functions or client-side Javascript-functions can decode it directly into multi-dimensional objects or arrays. And you can encode any Javascript- or PHP-datatype into JSON with one function call. Regards, Renne -- Sent with love from the new tine 2.0 email client ... Please visit <a href="http://tine20.org">http://tine20.org</a></body></html>