R: R: Social API: Scope

> > > [snip]
> > >
> > > My second point/question: If we are to develop both a federation
> > > protocol and a client API, there is liable to be considerable overlap
> > > in functionality and surface area, and significant interactions.
> > > Should we not consider both together, as a single holistic whole?
> > >
> >
> > Note that there will be some interactions. However, one can imagine a
> > standardized social JS client API sharing social data from a single origin
> > embedded via an iframe without any open standards for federation.
>
> [Owen] Of course. We can consider three layers: Server-to-Server,
> Client-to-Server, and a JavaScript rich content API (which might be
> implemented by the "container" in terms of the Client-to-Server API.
>
> I think that the former two are one specification (in which the
> Client-to-Server portion and Server-to-Server portions might be overlapping
> subsets), and the latter a separate specification. It certainly shouldn't be
> *required* for every implementation of the spec to implement the rich
> content API.


[walter] i also originally read the "social API" in the charter as a client-server API rather than a javascript library spec (more like the opensocial gadget APIs). is it thus the intention to actually go for these 3 layers? Should the charter be updated to clarify this?

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

Received on Friday, 1 August 2014 16:30:43 UTC