Have Geek Brain

SOAP Web Service Method Naming Conventions

Consider a web service (such as SOAP based) that has an operation that accepts most of the data from the client. From a server point of view, it receives data, but from a client point of view, it sends data. What should you call this operation? Parameters

  • ImportData li>
  • ExportData / SendData li>

Is there a de facto standard for naming these things? What are these web services commonly called?

Thank you for your opinion.

+2


source to share


2 answers


This is a service. It's there to serve. Name operations from a client point of view.



+6


source


Here are the W3C specifications for the Simple Object Access Protocol (SOAP) v1.2 specification: https://www.w3.org/TR/soap12/ .

Section 3.1.1 says that a URI should be used to denote a function and must "[include] that function unambiguously reference ...".

Further, section 5 of this document states:



"All feature names MUST follow the format 'verb' + 'noun' + ['subject'], where:

  • 'verb' is the action that the consumer performs; and
  • 'noun' is the name of the main object on which the action is performed.

Hope this helps someone (9 years later).

+1


source






More articles:


All Articles