@CouchDB Thanks for the detailed response! Liking this piece http://bit.ly/bU9kNN & the section “w/o link-following, you can’t be RESTfulâ€.
RT @CouchDB: @tomayac I have _show and _list functions to do server-side JS transforms from JSON to HTML etc, because REST requires link …
.@webr3 http://bit.ly/arB38o. #Twitoaster is great for linking to Twitter conversations.
mamund why WADL when you can RUN? [mca blog] #HTTP #REST #Hypermedia http://ff.im/-nTlyl
@webr3 Reg. http://bit.ly/cVPWxP “The elems we have & potentially need to represent and(*) annotate/augment are […]†// (*) and => and/OR(?)
@webr3 (Late reply, was OoO) I guess strictly resource state. In my humble interpretation of @fielding’s words, messages are no resource.
@DarrelMiller Forgot to CC you here: http://bit.ly/aaduc3. Looking forward to @CouchDB’s response. Relax ;-)
@AndrewWahbe Checking back w/ #CouchDB folks. Promising DB approach, no matter what.
@CouchDB +1 for relaxing :-) Unsure bout #Hypertext in @fielding’s sense (“When I say hypertext†http://bit.ly/9Wlx
@dret (Late reply, was OoO) +1 that #CRUD in #REST works fine & that docs are 1st class citizen#CouchDBchDB. Unsure ab#HATEOASEOAS, though.
@gkob Hi! Hättest du nächste Woche mal Zeit? Vielleicht so am 27. oder 28. Juli? Dann würd’ ich einfach mal direkt bei euch vorbeikommen…
#WADL reinvented in JSON form? See @hadleynet‘s post http://bit.ly/aBdzAO & @jcgregorio’s API description draft http://bit.ly/bP9tTe. #REST
Wow! 1st day back at work after 4 days out &a#Googleogle has acqui#Metawebaweb. I guess that’s a huge step towards the mainstr#SemanticWebcWeb.