Regarding b): shouldn't we be concerned that the original 4 functions apply to a single record at a time, when the new addition of "browse" seems to apply to a collection of records?
Gah, I hate this suggestion.
REST is dandy. But I'd like to have an equally simple and elegant framework for dealing with heterogeneous collections over high latency networks.