RSS remains useful as its use of XML established naming conventions for elements and attributes documented by a specification which apparently enabled RSS to become the de facto standard as developers could --trust-- other developers to use the same element and attribute naming convention.
JSON lacks such conformity in this context hence any best practice which could and should emerge would be:
* Conformance to RSS element and attribute naming
* Conformance to the structure of RSS expressed as an XML document, i.e. a root, a channel and items
On Thursday, April 12, 2012 9:11:12 AM UTC-5, Ray Daly wrote:
...