The essential results will be software modules within an integrated framework. Several functionalities will be provided for the usage in design-time as well as in run-time (by service providers, service designers or service brokers). For the design-time phase they are:

• a SWS Designer, which is aimed at designing a WSMO-based Semantic Web service from an existing non-semantic Web service.
  
  
• an Organizational Memory (CBR based Recommender), a Web Service implementation of a case-based memory (learning from the past), which stores and categorises non-logical representations of WSMO objects as well as additional non-semantic data (like graphical models and templates of SWS).
  
  
• the "SIR" (Semantic Information Router) as a metadata based content management and aggregation platform (endowed with a SPARQL query interface), used by other components to query for annotated and categorized service descriptions.
  
  
• the SWS Composer for creating a Semantic Web service through composition of existing WSMO-based SWSs. It uses a case base memory for retrieving service composition templates quasi-similar to the orchestration interface of the service to be composed.
  
  

The run-time modules (for service consumers, service providers, service brokers) are given by:

• the Distributed Repository for effective storing and retrieving all semantic elements of the WSMO Framework: Goals, Ontologies, SWS and Mediators (written in WSML), whereas each repository consists of two parts: a local repository (storing of all WSMO objects created in the Semantic Web service Unit, and a local registry for advertising the SWSs.
  
  
• the Service Access Middleware provides a retrieval and execution interface for advertised SW services. The user mandates a user interface agent for fulfilling the service demand and the agent provides recommendations based on the user"s query. The matchmaking between user request and service capability are similarity and logic based.
  
  
• the SWS Executor module processes Semantic Web service WSMO descriptions using choreography and orchestration engines for executing specific SWS related rules.
  
  
• the QoS (Quality of Service) Broker provides functionalities for monitoring the SW service execution process by feeding back extracted metric data.
  
  
• the Security and Privacy Enabler realised as an artificial "immune defence system" allowing the INFRAWEBS framework to function properly under changing conditions.