0
Semantic interoperability is something optional in the REST standard, there are no rules defined as occurs in SOAP with WSDL - for example, but I understand that in REST it is important to keep it that way to make the standard flexible, at least when it comes to specification.
However, for a consistent service, it is necessary to implement procedures so that communication between systems is as transparent as possible.
What procedures to implement semantic interoperability of a REST Web Service?
What do you mean by interoperability in this case?
– MarceloBoni
Interoperability is one of the major drawbacks of a web service using REST. Is that one of the great drawbacks? Is there any way to explain it?
– Jéf Bueno
Perhaps: "The interoperability problem is real?"
– OnoSendai
@Filipemoraes As stated, your question assumes as a proven fact that there is an interoperability problem. Many professionals find just the opposite.
– OnoSendai
@Onosendai and it is proven fact that there is no problem of semantic interoperability? Because that would be what you say is "just the opposite". We have to agree that I would have to ask the question one way or the other, since the middle would be a question based on opinions, right?
– Filipe Moraes
@Filipemoraes That’s why in many cases questions are asked cascading. "Is problem X real? If so, how to mitigate it?" If X is not real (and the answer is binary, yes or no), then there is no reason to answer the second question.
– OnoSendai
@Onosendai I disagree, for me the problem is real, it is not something mandatory in the REST standard, which does not occur in SOAP - for example - since we have WSDL. Okay, maybe this flexibility isn’t a problem precisely because it allows the programmer to choose between implementing solutions. What I would like is to know these solutions, as in SOAP there is WSDL. I edited the question and removed the term "problem".
– Filipe Moraes
@Marcelobonifazio edited the question and added "semantics".
– Filipe Moraes