SEE Unit - Standardization
OASIS Submissions
Semantic Web Services Architecture and Information Model
The purpose of SEE Semantic Web Services Architecture and Information Model is to define a skeleton of an infrastructure aiming for automation of service discovery, negotiation, adaptation, composition, invocation, and monitoring as well as service interaction requiring data, protocol, and process mediation. While there are several specifications in the space to capture functionality expected from the particular components/services of the SEE infrastructure, there is no prescribed definition of how to put all of these components to work together. In a services-oriented world, many services can be discovered and selected based on requirements of service requestors, then they must be orchestrated and adapted or integrated. The contribution of SEE specification is to describe these fixed components/services of an infrastructure that MUST be provided to enable a dynamic discovery, selection, mediation, invocation and inter-operation of the Semantic Web Services to facilitate the SOA revolution towards open environments.
SEE Execution Semantics
Specification of system behavior can be viewed as control and data flow between system constituents (services in SOA), where the actual actions take place. Developers tend to create architecture for specific, current needs what results in rigid system behaviors. SOA and therefore SEE takes a quite opposite approach, where system building blocks are well-defined and ready to be utilized in various scenarios, not necessarily considered during a design time. SEE is based on event-driven architecture composed of loosely coupled services, leading to various possible Execution Semantics for a whole system since the activities of the services are stimulated by events as they occur and there are no fixed bindings between the platform services. Services can create or consume events but they cannot invoke each other directly. They can cooperate with each other on the interface level but they do not refer to each other implementation directly.
More information on OASIS can be found here.
W3C Submission
Web Service Modeling Ontology (WSMO) Submission
Web services have added a new level of functionality to the current Web by making a first step towards seamless integration of distributed software components using web standards. While current web service technologies around SOAP, WSDL and UDDI cover mainly aspects of syntactic interoperability between services through common standards, WSMO complements these standards by providing a conceptual model and language for the semantic markup describing all relevant aspects of general services which are accessible through a web service interface. The ultimate goal of such markup is to enable the (total or partial) automation of the tasks (e.g. discovery, selection, composition, mediation, execution, monitoring, etc.) involved in both intra- and inter-enterprise integration of web services. WSMO has its conceptual basis in the Web Service Modeling Framework (WSMF), refining and extending this framework and developing a formal ontology and set of languages.
More information on the Web Service Modeling Ontology (WSMO) Submission can be found here.