IS is service oriented. Each URI that can be exposed by IS represents a service. IS tends to promote different interfaces for different services.
One can design a set of services with URIs corresponding to a desired resource model. But this would tend to be static, which would be problematic. For example, the “post” of a new resource should dynamically create another URI available to clients. A “delete” would remove a URI.
But that limitation is rather moot anyway. IS supports get and post, but does not support put and delete (or other HTTP methods). So implementing a RESTful solution in IS would definitely be a challenge.
#API-Management#soa#webMethods