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}</
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}&selec
tor={selector}&pid={pid}</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=X3oDMTMzdmR
lajVpBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARtc2d
JZAMxNTQEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMjIyMzYzNTkzBHRwY0lkAzE1MQ-->
(3) Reply (via web post)
<http://groups.yahoo.com/group/os-templates/post;_ylc=X3oDMTJwdTl0Z3QyBF
9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARtc2dJZAMxNT
QEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMjIyMzYzNTkz?act=reply&messageNum=154>
| Start a new topic
<http://groups.yahoo.com/group/os-templates/post;_ylc=X3oDMTJmdHA0ajRtBF
9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBH
NsawNudHBjBHN0aW1lAzEyMjIzNjM1OTM->
Messages
<http://groups.yahoo.com/group/os-templates/messages;_ylc=X3oDMTJmYmRrZz
BxBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZn
RyBHNsawNtc2dzBHN0aW1lAzEyMjIzNjM1OTM-> | Files
<http://groups.yahoo.com/group/os-templates/files;_ylc=X3oDMTJnOXZwNDBzB
F9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyB
HNsawNmaWxlcwRzdGltZQMxMjIyMzYzNTkz> | Photos
<http://groups.yahoo.com/group/os-templates/photos;_ylc=X3oDMTJmMm90ZzRv
BF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRy
BHNsawNwaG90BHN0aW1lAzEyMjIzNjM1OTM-> | Links
<http://groups.yahoo.com/group/os-templates/links;_ylc=X3oDMTJnamswNWQwB
F9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyB
HNsawNsaW5rcwRzdGltZQMxMjIyMzYzNTkz> | Database
<http://groups.yahoo.com/group/os-templates/database;_ylc=X3oDMTJkdDhwcm
IxBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZn
RyBHNsawNkYgRzdGltZQMxMjIyMzYzNTkz> | Polls
<http://groups.yahoo.com/group/os-templates/polls;_ylc=X3oDMTJncTQzYmhlB
F9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyB
HNsawNwb2xscwRzdGltZQMxMjIyMzYzNTkz> | Members
<http://groups.yahoo.com/group/os-templates/members;_ylc=X3oDMTJmMjg2c2N
zBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnR
yBHNsawNtYnJzBHN0aW1lAzEyMjIzNjM1OTM-> | Calendar
<http://groups.yahoo.com/group/os-templates/calendar;_ylc=X3oDMTJlNW03cW
pvBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZn
RyBHNsawNjYWwEc3RpbWUDMTIyMjM2MzU5Mw-->
Yahoo! Groups
<http://groups.yahoo.com/;_ylc=X3oDMTJldDJxaGhhBF9TAzk3MzU5NzE0BGdycElkA
zIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTIyM
jM2MzU5Mw-->
Change settings via the Web
<http://groups.yahoo.com/group/os-templates/join;_ylc=X3oDMTJnNDRlcGhpBF
9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBH
NsawNzdG5ncwRzdGltZQMxMjIyMzYzNTkz> (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest
<mailto:[EMAIL PROTECTED]:%20
Digest> | Switch format to Traditional
<mailto:[EMAIL PROTECTED]
ry%20Format:%20Traditional>
Visit Your Group
<http://groups.yahoo.com/group/os-templates;_ylc=X3oDMTJlNHY4N2N2BF9TAzk
3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawN
ocGYEc3RpbWUDMTIyMjM2MzU5Mw--> | Yahoo! Groups Terms of Use
<http://docs.yahoo.com/info/terms/> | Unsubscribe
<mailto:[EMAIL PROTECTED]>
Recent Activity
* 6
New Members
<http://groups.yahoo.com/group/os-templates/members;_ylc=X3oDMTJnbHRjNDU
yBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDdnR
sBHNsawN2bWJycwRzdGltZQMxMjIyMzYzNTkz>
Visit Your Group
<http://groups.yahoo.com/group/os-templates;_ylc=X3oDMTJmN2l1aGlxBF9TAzk
3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDdnRsBHNsawN
2Z2hwBHN0aW1lAzEyMjIzNjM1OTM->
Y! Messenger
Group get-together
<http://us.ard.yahoo.com/SIG=13oh94lnq/M=493064.12016274.12445679.867457
8/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222370793/L=/B=S06WOELaX.E-/J=12
22363593310254/A=3848584/R=0/SIG=12ceqob45/*http:/us.rd.yahoo.com/evt=42
403/*http:/messenger.yahoo.com/feat_conf.php>
Host a free online
conference on IM.
Y! Groups blog
The place to go
<http://us.ard.yahoo.com/SIG=13otnifoa/M=493064.12016258.12582637.867457
8/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222370793/L=/B=TE6WOELaX.E-/J=12
22363593310254/A=5191953/R=0/SIG=112mhte3e/*http:/www.ygroupsblog.com/bl
og/>
to stay informed
on Groups news!
Yahoo! Groups
Join people over 40
<http://us.ard.yahoo.com/SIG=13o2mfihm/M=493064.12662708.12980600.867457
8/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222370793/L=/B=TU6WOELaX.E-/J=12
22363593310254/A=5349276/R=0/SIG=11nhsqmjq/*http:/advision.webevents.yah
oo.com/EverydayWellness/>
who are finding ways
to stay in shape.
.
<http://geo.yahoo.com/serv?s=97359714/grpId=22548568/grpspId=1705375618/
msgId=154/stime=1222363593/nc1=3848584/nc2=5191953/nc3=5349276>
__,_._,___
