Apply API design guidelines to SOA?

Thought occurred to me when reading Brad Adam's blog that the names we give services need to be as well thought out as the names used in APIs.  I've made attempts at this topic before, of course, but I'm wondering if it may be easier just to leverage the work that others like Brad have done on 'API conventions' to the world of SOA services.