But in terms of AtomPub(as OpenSocial RESTful API is written in AtomPub), Service Document should be more recommended to use (I believe they to similar things).
> But in terms of AtomPub(as OpenSocial RESTful API is written in > AtomPub), Service Document should be more recommended to use (I > believe they to similar things).
> How should container provider do with them? > Implement both of them?
Hi Eiji,
I don't think an atom pub service doc will be very useful to a server that only serves the restful social api spec. The Atom Pub Service Document is really only useful in situations where you have a fairly small number of static resources on your server. It wasn't intended to describe dynamic services like the social apis. (By dynamic, I mean parts of the url paths to resources that are variables with many possible options).
The XRDS doc tries to accommodate this by using url templates and allowing a client to construct a request and "fill in the blanks". I don't think you'll find anything like this in the Service Doc, since it's designed to have real, working links that you can transverse to use the AtomPub service.
Abdera, the server framework, has code to generate ServiceDocs, by the way. Shindig just doesn't use it.
I see the difference between ServiceDoc and XRDS, and yes, I prefer XRDS to ServiceDoc. But in terms of compliance to the spec, isn't this making confusion? Is there any action to propose AtomPub spec team to replace ServiceDoc with XRDS?
>> But in terms of AtomPub(as OpenSocial RESTful API is written in >> AtomPub), Service Document should be more recommended to use (I >> believe they to similar things).
>> How should container provider do with them? >> Implement both of them?
> Hi Eiji,
> I don't think an atom pub service doc will be very useful to a server > that only serves the restful social api spec. The Atom Pub Service > Document is really only useful in situations where you have a fairly > small number of static resources on your server. It wasn't intended to > describe dynamic services like the social apis. (By dynamic, I mean > parts of the url paths to resources that are variables with many > possible options).
> The XRDS doc tries to accommodate this by using url templates and > allowing a client to construct a request and "fill in the blanks". I > don't think you'll find anything like this in the Service Doc, since > it's designed to have real, working links that you can transverse to > use the AtomPub service.
> Abdera, the server framework, has code to generate ServiceDocs, by the > way. Shindig just doesn't use it.
> I see the difference between ServiceDoc and XRDS, and yes, I prefer
> XRDS to ServiceDoc.
> But in terms of compliance to the spec, isn't this making confusion?
> Is there any action to propose AtomPub spec team to replace ServiceDoc
> with XRDS?
> Eiji
> 2008/6/4 David Primmer <david.prim...@gmail.com>:
> > On Tue, Jun 3, 2008 at 3:16 PM, Eiji Kitamura <agek...@gmail.com> wrote:
> >> Hi,
> >> In OpenSocial v0.8's RESTful API spec, it saids to use XRDS-Simple to
> >> discover resources.
> >> But in terms of AtomPub(as OpenSocial RESTful API is written in
> >> AtomPub), Service Document should be more recommended to use (I
> >> believe they to similar things).
> >> How should container provider do with them?
> >> Implement both of them?
> > Hi Eiji,
> > I don't think an atom pub service doc will be very useful to a server
> > that only serves the restful social api spec. The Atom Pub Service
> > Document is really only useful in situations where you have a fairly
> > small number of static resources on your server. It wasn't intended to
> > describe dynamic services like the social apis. (By dynamic, I mean
> > parts of the url paths to resources that are variables with many
> > possible options).
> > The XRDS doc tries to accommodate this by using url templates and
> > allowing a client to construct a request and "fill in the blanks". I
> > don't think you'll find anything like this in the Service Doc, since
> > it's designed to have real, working links that you can transverse to
> > use the AtomPub service.
> > Abdera, the server framework, has code to generate ServiceDocs, by the
> > way. Shindig just doesn't use it.
|
