Re: [opensocial-and-gadgets-spec] Re: [os-templates] Declarative Data Definition - requirements

[David Byttow <da...@google.com>]

On Thu, Sep 25, 2008 at 11:39 AM, Kevin Brown <et...@google.com> wrote:

>
> The problem with this solution is that it's a 6th mapping for social data
> (JSON-RPC, XML-RPC, JSON-REST, ATOM-REST, javascript APIs, and now this).
>
> That's not really reasonable to expect developers to learn, especially
> since different sites are going to support different things. Many people are
> already frustrated at inconsistencies between implementations.
>
> I don't see that as an effective argument against defining XML markup to
wrap one or more of the other protocols (e.g. the javascript APIs on the
client). A developer does not need to learn all 6 to build an app as they
can build a fairly compelling app right now with just the javascript APIs.
This is just a layer of abstraction with side-benefits of performance and
simplicity.

One of the primary goals of this is to support on the client and/or server
seamlessly such that a developer can worry less about whether or not it will
work on a given container.

David