The OSML audience is HTML coders, not JavaScript types. As a result, I have a hard time seeing the data request tags at http://wiki.opensocial-templates.org/index.php?title=OpenSocial_Markup#D ata_Request_Tags changing to match the REST URL syntax.
FWIW, our primary requirement is that a given OpenSocial REST endpoint MUST support XRDS. The structure of the endpoint URLs is an orthogonal discussion. If you like, feel free to kick off a separate thread on that item-- I can follow up and I think we can reach closure pretty simply. -----Original Message----- 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: [opensocial-and-gadgets-spec] 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.
