It certainly is exciting to obtain a peek at a brand new innovative technology right before it truly will take off. One of the most interesting Web prospects is Semantic Web Services.
Today, Web Services are self-contained, self-described, component applications that may be printed, located, and invoked over the Web. Web Services give a standard way of interoperating between different computer programs running on a number of platforms. eXtensible Markup Language (XML) offers the extensibility and language neutrality that’s the key for standards-based interoperability of Web Services. They perform functions that may include everything from simple query responses to complex business processes. When a Web Services are deployed, other applications can uncover and invoke it. At the moment, Web Services require human interaction for identification and implementation.
Tim Berners-Lee, the inventor from the Web, has recommended the integration of Web Services and Semantic Web technology could offer significant performance improvement for Web applications. Integration could combine the company logic of Web Services using the Semantic Web’s significant content. There are many places that the 2 perform well together. For instance, the present technologies for discovery (Universal Description, Discovery and Integration, UDDI), binding (Web Services Description Language, WSDL), and messaging (Simple Object Access Protocol, SOAP) can use an ontology (Web Ontology Language, OWL) to supply automatic Semantic Web Services therefore allowing fast interaction with Business online rules’ engines.
With the Semantic Web, users and software agents could uncover, invoke, compose, and monitor Web sources offering particular services having a high amount of automation. Recent industrial curiosity about such services and also the accessibility to tools to allow service automation suggests the chance that fast progress can be created. Ontology Web Language (OWL) for services (OWL-S) could be the most viable application.
Web Service Architecture mandates that discrete software agents interact to apply functionality. These agents must communicate by protocol stacks which are less reliable than direct code invocation. Therefore, developers must think about the unpredictable latency of remote access, and consider problems with partial failure and concurrency.
To utilize an internet Service, an application agent requires a computer-interpretable description from the service and also the method for access. An essential goal for Semantic Web markup languages is defined a framework to make and discussing these descriptions. Internet sites will be able to employ some fundamental classes and qualities for declaring and describing services, and also the ontology structuring mechanisms of OWL offers the appropriate framework to get this done.
OWL-S is really a high-level ontology, in the application level that is supposed to answer the what- and why-questions regarding an internet Service, as the how-questions are addressed included in WSDL. An Ontology is really a taxonomy ( classes and relationships) plus a group of inference rules.
Consequently, an ontology for Web Services will make Web Services machine understandable and support automated Web Service composition and interoperability.
Therefore supplying automated functions for:
* service discovery,
* service execution,
* service composition,
* service monitoring.
Discovery: A course must first have the ability to instantly find, or uncover, a suitable Web service. Neither Web Service Description Language (WSDL) nor Universal Discovery and outline language (UDDI) enables for software to determine which an internet service purports to the customer. A Semantic Web service describes its qualities and abilities to ensure that software can instantly determine its purpose.
Invocation: Software must have the ability to instantly figure out how to invoke or execute the service. For instance, if executing the services are a multi-step procedure, the program must understand how to communicate with the plan to complete the required sequence. A Semantic Web service supplies a descriptive listing of how much of an agent needs so that you can do in order to execute and match the service. Including exactly what the inputs and outputs from the service are.
Composition: Software must have the ability to select and mix numerous Web services to accomplish a particular objective. The help need to interoperate with one another seamlessly so the combined answers are a legitimate solution.
Monitoring: Agent software needs so that you can verify and monitor the service qualities during operation.
Using these abilities we can program agents to discover and apply Web Services all instantly.