I would love an answer for this. How can we describe an api without just calling it a generic 'web service' - where that may be misinterpreted as being a SOAP w

I would love an answer for this. How can we describe an api without just calling it a generic 'web service' - where that may be misinterpreted as being a SOAP web service. And it's not strictly a REST web service. http://stackoverflow.com/questions/24482179/whats-the-best-alternative-to-describing-an-api-as-restful http://stackoverflow.com/questions/24482179/whats-the-best-a...