Why do we need a repository? Simply documenting interfaces in english (and other natural languages) on developer site web pages seems to be "good enough". I have yet to see a repository that was worth the effort.
-- Nick "If good enough is the enemy of the best, count me as an ally of the former." On Nov 25, 2007 10:37 AM, ash galal <[EMAIL PROTECTED]> wrote: > Still, we need to have some repository for discovering > and achieve a service level agreements between parties > in the REST style architectural. > I think the new initiatives (WADL)well develop > something like WSDL which I do think it could be used > temporarily to define REST interface. > This is one of the reason where REST fits well in the > human to machine interactions better than Machine to > machine interactions. > > Ashraf Galal > > --- Nick Gall <[EMAIL PROTECTED] <nick.gall%40gmail.com>> wrote: > > > "[T]he URIs of the service are most certainly part > > of the *interface* of the > > service. Thereby, every RESTful *service* has its > > own custom interface." > > > > If there were NO differences between two interfaces, > > they wouldn't just be > > uniform, they'd be identical. <grin> That said, the > > more uniform the IFaPs > > (Identifiers, Formats, and Protocols) the better. > > Uniform formats like the > > flavors of RSS, Atom, GData, and even Microsoft's > > handful of attempts are > > moves in the right direction. And WWW principles > > like "avoid aliases" help > > nudge toward uniform identifiers. > > > > Interfaces based on the REST style are much further > > along the uniformity > > curve than the typical styles associated with use of > > WSDL. In my opinion, > > attempts to spin RESTful interfaces as being just as > > custom as the typical > > WSDL-based interface are disingenuous. > > > > -- Nick > > > > On Nov 22, 2007 4:00 PM, Sanjiva Weerawarana > > <[EMAIL PROTECTED] <sanjiva%40opensource.lk>> wrote: > > > > > Mark Baker wrote: > > > > > > > > It's not a myth, RESTful systems do not need > > WSDL. It doesn't need > > > > any description languages in fact. It needs > > forms: information sent > > > > > > I think WADL folks, Sam Ruby and Leonard > > Richardson all disagree with you > > > on that. > > > > > > > I don't see what security & caching have to do > > with scalability. Are > > > > you talking about REST or HTTPS? > > > > > > Caching is a key part of the scalability > > architecture of HTTP. However, > > > that only works for HTTP and not HTTPS .. right? > > > > > > > I don't follow the "Lie: RESTful services have a > > uniform interface" > > > > argument, but it's prima facie incorrect because > > they do by > > > > definition. > > > > > > Did you look at the next page? Note I said RESTful > > *services* .. the URIs > > > of the service are most certainly part of the > > *interface* of the service. > > > Thereby, every RESTful *service* has its own > > custom interface. WADL > > > appears to agree 100% as that's what WADL is > > describing. > > > > > > I hope we don't drop down to a REST vs. WS-* > > religious war again on this! > > > > > > Sanjiva. > > > -- > > > Sanjiva Weerawarana, Ph.D. > > > Founder & Director; Lanka Software Foundation; > > http://www.opensource.lk/ > > > Founder, Chairman & CEO; WSO2, Inc.; > > http://www.wso2.com/ > > > Member; Apache Software Foundation; > > http://www.apache.org/ > > > Visiting Lecturer; University of Moratuwa; > > http://www.cse.mrt.ac.lk/ > > > > > > > > > > > > > > -- > > Nick Gall > > Phone: +1.781.608.5871 > > AOL IM: Nicholas Gall > > Yahoo IM: nick_gall_1117 > > MSN IM: (same as email) > > Google Talk: (same as email) > > Email: nick.gall AT-SIGN gmail DOT com > > Weblog: http://ironick.typepad.com/ironick/ > > Furl: http://www.furl.net/members/ngall > > > > > -- Nick Gall Phone: +1.781.608.5871 AOL IM: Nicholas Gall Yahoo IM: nick_gall_1117 MSN IM: (same as email) Google Talk: (same as email) Email: nick.gall AT-SIGN gmail DOT com Weblog: http://ironick.typepad.com/ironick/ Furl: http://www.furl.net/members/ngall
