I was recently invited to write an article for the FreePint newsletter. The article "Embracing the Wiki Way: Deploying a Corporate Wiki" is now available. It serves as an update to my blog entry on bootstrapping a corporate wiki with more of an emphasis on tips for users.
If you're thinking about deploying a corporate wiki then hopefully the article may help you plan your strategy. There are also plenty more case studies available for you to compare with.
Edd sent me a pointer to a nice article from Scott Raymond called "Refactoring to REST" in which he outlines how his application code was improved and simplified by adopting a more RESTful design. The application here was built on Rails and used the Simply Restful plugin to nudge Rails into a more RESTful aspect.
I've noticed a similar reduction in complexity when moving to RESTful application design. I've tended to describe this as reducing the "surface area" of the application: the smaller the surface area, the less code is required. It also follows that the smaller the surface area, the less URL types are required. You end up with fewer fairly standard URL patterns which identify resources, rather than RPC-style "method" oriented URLs.
This has some nice properties. For the client a given server application becomes more easily substitutable, as there's less coupling. And on the server side it clarifies the "points of contact" of the application with the web (of data). It also makes it easier to maintain permanent links because as the URLs are simpler and more identifiable they're easier to rewrite/redirect as an application evolves or changes architecture.