Paul Lindner <[EMAIL PROTECTED]> Thu, 8 Nov 2007 05:58:32 >Actually, it's the placement of URL params inside the URI that is >troublesome. URIs like: > > http://foo.com/rest/user/12345/friends/start=1/end=200?filter=NEW
Yuck! >do not fit the Verb/Noun/ProperNoun + Adjectives model Enunciate >provides. The planned way to fix this is to add a URI pattern that >will allow adjectives to be provided from the URI. It's funny that Google (like most of the portals) don't use friendly URLs themselves. I guess they don't have to do SEO! So you get http://www.google.com/search?num=50&hl=en&safe=off&client=firefox-a&rls=o rg.mozilla%3Aen-US%3Aofficial&hs=L0n&q=opensocial&btnG=Search I'd be a lot happier if we could just use http://foo.com/gdata.php?id=12345&op=friends&start=1&end=200&filter=NEW The point being that these are not URLs for consumers so who cares if they're readable. But I know I'm swimming through dangerous water here. >As far as auto-discovery? Why reinvent the wheel. Either add link >rel= tags in the user profile or extend RSD. It was more a question of either/and/or. Are we expecting Application writers to find the APIs on non-Google containers in standard places or help them out with RSD and link rel or for them to build maps between containers and API locations? Even using link rel we're heading into another problem. I might have lots of them:- <link rel="alternate" type="application/atom+xml" title="Foobar" href="http://foobar.blogspot.com/thisMightBeAtomPosts"; /> <link rel="alternate" type="application/atom+xml" title="Foobar" href="http://foobar.blogspot.com/thisMightBeGDataPeople"; /> There's probably an answer to this, if I knew more about Atom. -- Julian Bond E&MSN: julian_bond at voidstar.com M: +44 (0)77 5907 2173 Webmaster: http://www.ecademy.com/ T: +44 (0)192 0412 433 Personal WebLog: http://www.voidstar.com/ skype:julian.bond?chat *** Just Say No To DRM *** --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Container Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
