It looks like the OSML spec has the person/people stuff figured out. For person/people, there is some information at http://wiki.opensocial-templates.org/index.php?title=OpenSocial_Markup#. 3Cos:PersonRequest.3E.
<os:PersonRequest key="Viewer" id="VIEWER" fields="name,id,thumbnailUrl,books"/> <os:PeopleRequest key="PagedFriends" idSpec="VIEWER_FRIENDS" page="2" pageSize="20"/> We wouldn't need a new syntax for Person, People, Activities, or AppData as there is a different mapping independent of REST/XRDS. Does this solve the problem at hand? Is there a shortcoming in this solution that I'm not seeing? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Louis Ryan Sent: Thursday, September 25, 2008 11:14 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [email protected] Subject: Re: [os-templates] Declarative Data Definition - requirements 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}&selec tor={selector}&pid={pid} <http://api.another-example.org/people?guid=%7Bguid%7D&selector=%7Bselec tor%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=X3oDMTMzcDh mZTVkBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARtc2d JZAMxNTcEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMjIyMzY2NDgwBHRwY0lkAzE1MQ--> (5) Reply (via web post) <http://groups.yahoo.com/group/os-templates/post;_ylc=X3oDMTJwMGhlaDJvBF 9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARtc2dJZAMxNT cEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMjIyMzY2NDgw?act=reply&messageNum=157> | Start a new topic <http://groups.yahoo.com/group/os-templates/post;_ylc=X3oDMTJmY3NkdHZhBF 9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBH NsawNudHBjBHN0aW1lAzEyMjIzNjY0ODA-> Messages <http://groups.yahoo.com/group/os-templates/messages;_ylc=X3oDMTJmb251aD dqBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZn RyBHNsawNtc2dzBHN0aW1lAzEyMjIzNjY0ODA-> | Files <http://groups.yahoo.com/group/os-templates/files;_ylc=X3oDMTJnaWJrcTZiB F9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyB HNsawNmaWxlcwRzdGltZQMxMjIyMzY2NDgw> | Photos <http://groups.yahoo.com/group/os-templates/photos;_ylc=X3oDMTJmN2pyZXRk BF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRy BHNsawNwaG90BHN0aW1lAzEyMjIzNjY0ODA-> | Links <http://groups.yahoo.com/group/os-templates/links;_ylc=X3oDMTJnNjI5NmQ2B F9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyB HNsawNsaW5rcwRzdGltZQMxMjIyMzY2NDgw> | Database <http://groups.yahoo.com/group/os-templates/database;_ylc=X3oDMTJkb29yNG 51BF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZn RyBHNsawNkYgRzdGltZQMxMjIyMzY2NDgw> | Polls <http://groups.yahoo.com/group/os-templates/polls;_ylc=X3oDMTJncXFnNGRjB F9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyB HNsawNwb2xscwRzdGltZQMxMjIyMzY2NDgw> | Members <http://groups.yahoo.com/group/os-templates/members;_ylc=X3oDMTJmZGJxNGk wBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnR yBHNsawNtYnJzBHN0aW1lAzEyMjIzNjY0ODA-> | Calendar <http://groups.yahoo.com/group/os-templates/calendar;_ylc=X3oDMTJldWFyMj RuBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZn RyBHNsawNjYWwEc3RpbWUDMTIyMjM2NjQ4MA--> Yahoo! Groups <http://groups.yahoo.com/;_ylc=X3oDMTJlNnBnbXExBF9TAzk3MzU5NzE0BGdycElkA zIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTIyM jM2NjQ4MA--> Change settings via the Web <http://groups.yahoo.com/group/os-templates/join;_ylc=X3oDMTJnNGE0Y2E3BF 9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBH NsawNzdG5ncwRzdGltZQMxMjIyMzY2NDgw> (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=X3oDMTJlZ3Bidm5hBF9TAzk 3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDZnRyBHNsawN ocGYEc3RpbWUDMTIyMjM2NjQ4MA--> | 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=X3oDMTJnanVqcDB jBF9TAzk3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDdnR sBHNsawN2bWJycwRzdGltZQMxMjIyMzY2NDgw> Visit Your Group <http://groups.yahoo.com/group/os-templates;_ylc=X3oDMTJmaTRhczk2BF9TAzk 3MzU5NzE0BGdycElkAzIyNTQ4NTY4BGdycHNwSWQDMTcwNTM3NTYxOARzZWMDdnRsBHNsawN 2Z2hwBHN0aW1lAzEyMjIzNjY0ODA-> Y! Messenger Files to share? <http://us.ard.yahoo.com/SIG=13og7ddha/M=493064.12016274.12445679.867457 8/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222373680/L=/B=whkTJELaX9I-/J=12 22366480168119/A=3848578/R=0/SIG=11umg3fun/*http:/us.rd.yahoo.com/evt=42 403/*http:/messenger.yahoo.com> Send up to 1GB of files in an IM. New web site? Drive traffic now. <http://us.ard.yahoo.com/SIG=13os9pqjj/M=493064.12016308.12445700.867457 8/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222373680/L=/B=wxkTJELaX9I-/J=12 22366480168119/A=3848642/R=0/SIG=131eshi2t/*http:/searchmarketing.yahoo. com/arp/srchv2.php?o=US2004&cmp=Yahoo&ctv=Groups3&s=Y&s2=&s3=&b=50> Get your business on Yahoo! search. Y! Groups blog the best source <http://us.ard.yahoo.com/SIG=13o0519og/M=493064.12016258.12582637.867457 8/D=groups/S=1705375618:NC/Y=YAHOO/EXP=1222373680/L=/B=xBkTJELaX9I-/J=12 22366480168119/A=5191955/R=0/SIG=112mhte3e/*http:/www.ygroupsblog.com/bl og/> for the latest scoop on Groups. . <http://geo.yahoo.com/serv?s=97359714/grpId=22548568/grpspId=1705375618/ msgId=157/stime=1222366480/nc1=3848578/nc2=3848642/nc3=5191955> __,_._,___
