For 3.x, I propose that we take that further and deprecate the XML
format binding and focus specifically on JSON.
Individual implementations would still be free to support multiple
format bindings as they see fit, but within the core protocol, data
model and implementation, the requirement to provide support for
multiple data formats is unnecessarily complicates everything. Let's
pick one and be done with it.
Simplification. Making the overall spec easier to understand, easier to implement. Reduce the number of things that MUST be supported. Allow the code to be simplified and optimized by eventually eliminating the need for there to be multiple data model serializations. More required to support options are not necessarily a good thing.
What's the motivation behind this?
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/XhfmPZR28L0J.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.