A developer recently asked me about standards for naming web services. I have no idea. Our architecture standard names components as "verb noun" phrases, so I suggested things like: "AuthenticateClientService" and "FindDocumentService". Yes, the "Service" portion does seem redundant, but we're thinking that it will help readily identify it when referenced out of context in future.
Is there any sort of convention for naming web services in the enterprise?
Mr. Malik asked the question awhile back, but that's all I've been able to find, and it seems no answer was provided. The many examples of WSDL's I've seen lack consistency, and seem to rely on the whim of the creator.
Your suggestions and pointers are requested and welcome.
UPDATE: I discovered some info on good service/web service naming practices.