Does WSRF address criticisms of OGSI from the Web services community?
While the definition of WSRF has been motivated primarily by the desire to integrate recent developments in Web services architecture, in particular WS-Addressing, its design also addresses three criticisms of OGSI from the Web services community: • Too much stuff in one specification. Many would like to use parts but not all of OGSI, and while most of OGSI v1.0 is optional, some feel that use of parts obligates use of all. Response: WSRF partitions OGSI v1.0 functionality into a family of composable specifications. • Does not work well with existing Web services tooling. OGSI v1.0 uses XML Schema fairly aggressively, for example with substantial use of xsd:any, attributes, etc., and “document-oriented” WSDL operations. These features cause problems with, for example, JAX-RPC. Response: WSRF tones down the usage of XML Schema somewhat. • Too object oriented. OGSI v1.0 models a stateful resource as a Web service that encapsulates the resource’s state, with the identity and lifecycle of
