2006/6/5, Elliotte Harold <[EMAIL PROTECTED]>:
My notes were originally written about six months ago, and have been updated several times since. I think they're still up-to-date on the APP side, especially since they don't go too deep into the dark corners of the specs, but I may have missed some changes. If anyone feels like giving them a quick once over and letting me know if I've forgottten anything, I'd appreciate it.
Slide 43: REST isn't an architecture, it's an architectural style ;) Slide 45: app:member-type is about to be replaced with app:accept Slide 47: the entry lacks an atom:id and atom:author (entries must be valid Atom, servers are free to modify them as appropriate) Slide 48: if you send an update, why is the server response a 201 (Created) ? Slide 48 and 49: you talk about updating and deleting "entries" but are manipulating XHTML, and a resource whose IRI suggests it has a single, HTML representation (it ends in ".html", which is commonly understood as "it identifies an HTML file"). How about PUTting an Atom Entry (if you PUT XHTML, you're more likely using "bare HTTP" or WebDAV than Atom-Protocol) and using IRIs without "file extension" -like suffixes? My 2 c€nts… -- Thomas Broyer
