I agree, I am a big fan of REST but what is with the notion that the uri can't be more abstracted? api.twitter.com can be the same as twitter.com/api. They are

I agree, I am a big fan of REST but what is with the notion that the uri can't be more abstracted? api.twitter.com can be the same as twitter.com/api. They are both resources and they happen to route to the same thing. Not ideal but may be needed in evolving api as it grows like you mention.