I believe whats up for debate is what syntax to use. The 3 choices are very roughly....
1. Directly use the REST URL format <Preload id="friends" type="OS-REST" href=" http://api.myspace.com/people/@self/@friends";> 2. Create some new format <os:DataRequest key="friend_data" service="people" params="group=FRIENDS&sort=name"/> 3. Use the JSON-RPC format <Preload type="opensocial"> [{ method : people.get, id : fiend_data, userId : "@self", groupId : "@friends },...] </Preload> My objection to 1. was because XRDS makes it by definition cross-container incompatible. My objection to 2 is because it's yet another syntax for specifying how to fetch OpenSocial data. I'm certainly not arguing that 2. will not work with XRDS. On Thu, Sep 25, 2008 at 10:44 AM, Scott Seely <[EMAIL PROTECTED]> wrote: > The prefetch/pipelining syntax doesn't even imply that the referenced > endpoints need to be stable across endpoints. The datapiplining syntax is > designed such that an implementation can do all the processing on the > server, all the processing on the client, or some combination of these. If > the specs break that in some way, that's bad—please point out where that is > true. If a client side implementation relies on REST for processing, the > container needs to do the following: > > 1. Request the XRDS document for the target. > > 2. Look for the service of the type of interest. > > 3. Post to the service using the os:URI-Template provided. > > > > This then allows one implementation to have a People that looks like this: > > <Service> > <Type>http://ns.opensocial.org/2008/opensocial/people</Type> > <os:URI-Template> > http://api.example.org/people/{guid}/{selector}/{pid}<http://api.example.org/people/%7Bguid%7D/%7Bselector%7D/%7Bpid%7D> > </os:URI-Template> > </Service> > > > > And another could have: > > > > <Service> > <Type>http://ns.opensocial.org/2008/opensocial/people</Type> > <os:URI-Template> > http://api.another-example.org/people?guid={guid}&selector={selector}&pid={pid}<http://api.another-example.org/people?guid=%7Bguid%7D&selector=%7Bselector%7D&pid=%7Bpid%7D> > </os:URI-Template> > </Service> > > > > We have to publish something in the container about how to contact the > container for more data. That could be a base URI (which is what a non-XRDS > solution would probably do) or an XRDS URI. The XRDS URI has a lot of extra > benefits that make it handy, whereas convention limits what we can publish. > > > > What am I missing? > > > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *On Behalf Of *Louis Ryan > *Sent:* Thursday, September 25, 2008 10:26 AM > *To:* [EMAIL PROTECTED] > *Cc:* [EMAIL PROTECTED]; > [email protected] > *Subject:* Re: [os-templates] Declarative Data Definition - requirements > > > > I believe the issue with XRDS is that it works fine for programmatic > discovery of endpoints. The prefetch/pipelining syntax is declarative and > therefore if we choose the REST URL syntax it would require that the > referenced endpoints be stable and cross-container compatible. Im > don't know how close the URL structure of MySpaces REST APIs matches that in > Shindig for example but Im guessing there are some incompatibilities. > > > > As John mentioned and I alluded to on the other thread there was a proposal > to standardize on a URL format for REST that was cross-container compatible > without the need for XRDS. but it didn't see much traction. Would MySpace be > amenable to this? If not then we are left to choose between the RPC format > or something new. > > On Thu, Sep 25, 2008 at 8:06 AM, Scott Seely <[EMAIL PROTECTED]> wrote: > > I need to see an expansion on what is meant by "No full XRDS support." > MySpace has found XRDS to be very helpful. With XRDS, we get the following: > > · Flexibility in deployment. If/when we move endpoints, we only > need to leave the XRDS in place. > > · Discovery of extensions. We already use XRDS to advertise the > service types we offer for services that do not appear in OpenSocial. This > has been well-received by our existing customers. > > > > > > > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *On Behalf Of *Evan Gilbert > *Sent:* Wednesday, September 24, 2008 11:36 PM > *To:* [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [email protected] > *Subject:* [os-templates] Declarative Data Definition - requirements > > > > Hi all - in order to reach consensus on declarative data definition, I > think it would help to first agree on requirements. > > Requirements (not all agreed to) from previous thread: > > - Support per-view specification of data requests > - Extensible for new data types > - Must be able to parametrize a data request (i.e., <os:PeopleRequest > ... page="${page}">) > - Must be possible to pass request data to client for processing > - Only one declarative syntax - we have to agree between templates and > preloads. > - 1:1 mapping of REST/RPC params to declarative syntax. No full XRDS > support > - Cannot require using <Content> > > > Some open questoins: > > - Do we need to parameterize data requests for preloads or only for > templates? > > > - Do we need to support: > <Preload> > <os:PeopleRequest ... page="${page}"> > </Preload> > > > - Is "Cannot require using <Content>" a requirement? > > > - The following would seem to be an option using <Content> > <Content type="proxied" href="http://yoursite.com";> > <os:DataRequest key="friend_data" service="people" > params="group=FRIENDS&sort=name"/> > </Content> > > Please send feedback on requirements - new ones, clarifications, or > questions about the requirements above. > > I think if we all agree on these requirements we'll be left with a much > simpler discussion on spec choices to implement. > > > > > __._,_.___ Messages in this topic > <http://groups.yahoo.com/group/os-templates/message/151;_ylc=X3oDMTMzcW5kZTRrBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARtc2dJZAMxNTUEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMjIyMzY0NzE1BHRwY0lkAzE1MQ-->( > 4) Reply (via web post) > <http://groups.yahoo.com/group/os-templates/post;_ylc=X3oDMTJwMWtrZzdmBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARtc2dJZAMxNTUEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMjIyMzY0NzE1?act=reply&messageNum=155>| > Start > a new topic > <http://groups.yahoo.com/group/os-templates/post;_ylc=X3oDMTJmajRxdmZyBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNudHBjBHN0aW1lAzEyMjIzNjQ3MTU-> > > Messages<http://groups.yahoo.com/group/os-templates/messages;_ylc=X3oDMTJmNHJjYWwwBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNtc2dzBHN0aW1lAzEyMjIzNjQ3MTU->| > Files<http://groups.yahoo.com/group/os-templates/files;_ylc=X3oDMTJnajBlaGZhBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNmaWxlcwRzdGltZQMxMjIyMzY0NzE1>| > Photos<http://groups.yahoo.com/group/os-templates/photos;_ylc=X3oDMTJmbTMyYjFsBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNwaG90BHN0aW1lAzEyMjIzNjQ3MTU->| > Links<http://groups.yahoo.com/group/os-templates/links;_ylc=X3oDMTJndW1qN3ZiBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNsaW5rcwRzdGltZQMxMjIyMzY0NzE1>| > Database<http://groups.yahoo.com/group/os-templates/database;_ylc=X3oDMTJkZm1sY2oxBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNkYgRzdGltZQMxMjIyMzY0NzE1>| > Polls<http://groups.yahoo.com/group/os-templates/polls;_ylc=X3oDMTJnN290dTQ5BF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNwb2xscwRzdGltZQMxMjIyMzY0NzE1>| > Members<http://groups.yahoo.com/group/os-templates/members;_ylc=X3oDMTJmOWFnNHIxBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNtYnJzBHN0aW1lAzEyMjIzNjQ3MTU->| > Calendar<http://groups.yahoo.com/group/os-templates/calendar;_ylc=X3oDMTJlcDRsYXRvBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNjYWwEc3RpbWUDMTIyMjM2NDcxNQ--> > [image: Yahoo! > Groups]<http://groups.yahoo.com/;_ylc=X3oDMTJlbTJsanJ0BF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTIyMjM2NDcxNQ--> > Change settings via the > Web<http://groups.yahoo.com/group/os-templates/join;_ylc=X3oDMTJncWRxMjNwBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNzdG5ncwRzdGltZQMxMjIyMzY0NzE1>(Yahoo! > ID required) > Change settings via email: Switch delivery to Daily Digest<[EMAIL > PROTECTED]:+Digest>| Switch > format to Traditional<[EMAIL PROTECTED]:+Traditional> > Visit Your Group > <http://groups.yahoo.com/group/os-templates;_ylc=X3oDMTJlbDgza29wBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNocGYEc3RpbWUDMTIyMjM2NDcxNQ-->| > Yahoo! > Groups Terms of Use <http://docs.yahoo.com/info/terms/> | Unsubscribe > <[EMAIL PROTECTED]> > Recent Activity > > - 6 > New > Members<http://groups.yahoo.com/group/os-templates/members;_ylc=X3oDMTJnNXI0bTNwBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDdnRsBHNsawN2bWJycwRzdGltZQMxMjIyMzY0NzE1> > > Visit Your Group > <http://groups.yahoo.com/group/os-templates;_ylc=X3oDMTJmcnVkdWl1BF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDdnRsBHNsawN2Z2hwBHN0aW1lAzEyMjIzNjQ3MTU-> > Y! Messenger > > Quick file > sharing<http://us.ard.yahoo.com/SIG=13o7sl6nt/M=493064.12016274.12445679.8674578/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222371915/L=/B=jdHwDULaX9E-/J=1222364715085670/A=3848580/R=0/SIG=11umg3fun/*http://us.rd.yahoo.com/evt=42403/*http://messenger.yahoo.com> > > Send up to 1GB of > > files in an IM. > Need traffic? > > Drive > customers<http://us.ard.yahoo.com/SIG=13ogso7bi/M=493064.12016308.12445700.8674578/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222371915/L=/B=jtHwDULaX9E-/J=1222364715085670/A=3848644/R=0/SIG=131l83flq/*http://searchmarketing.yahoo.com/arp/srchv2.php?o=US2006&cmp=Yahoo&ctv=Groups5&s=Y&s2=&s3=&b=50> > > With search ads > > on Yahoo! > All-Bran > > 10 Day > Challenge<http://us.ard.yahoo.com/SIG=13oi1tt7q/M=493064.12016283.12445687.8674578/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222371915/L=/B=j9HwDULaX9E-/J=1222364715085670/A=5202323/R=0/SIG=11aijbghb/*http://new.groups.yahoo.com/allbrangroup> > > Join the club and > > feel the benefits. > . > > __,_._,___ >
