XML option #2 feels like the best option to me, because it seems the
most flexible, most forward compatible, and plays well with AWS:
http://docs.amazonwebservices.com/AmazonSimpleDB/latest/DeveloperGuide/SDB_API_GetAttributes.html

(that's my $0.02)

_s.

>   XML option #2 which is more verbose but allows for namespaces and keys to
> contain arbitrary data
>
>   <annotations>
>     <annotation>
>       <namespace>iso</namespace>
>       <key>isbn</key>
>       <value>030759243X</value>
>     </annotation>
>     <annotation>
>       <namespace>amazon</namespace>
>       <key>url</key>
>       
> <value>http://www.amazon.com/Although-Course-You-Becoming-Yourself/dp/030759...
> </value>
>     </annotation>
>   </annotations>
>
> If we went with XML option #2 it may or may not be a problem that it isn't
> "symmetrical" with the JSON representation. On the other hand, JSON and XML
> tend to be culturally at opposite sides of the Pithiness Spectrum.


-- 
Subscription settings: 
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

Reply via email to