Idea To Earn Money

One of the more interesting Web prospects is Semantic Web Services. It's always exciting to get a glimpse of a new innovative technology just before it really takes off.

Web Services require human interaction for identification and implementation, at present. Other applications can discover and invoke it, once a Web Service is deployed. They perform functions that can include anything from simple query responses to complex business processes. EXtensible Markup Language (XML) provides the extensibility and language neutrality that is the key for standards-based interoperability of Web Services. Web Services provide a standard means of interoperating between different software applications running on a variety of platforms. And invoked across the Web, located, component applications that can be published, self-described, web Services are self-contained, today.

OWL) to provide automatic Semantic Web Services thereby allowing fast interaction with Web business rules' engines, sOAP) could use an ontology (Web Ontology Language, and messaging (Simple Object Access Protocol, wSDL), binding (Web Services Description Language, uDDI), discovery and Integration, the current technologies for discovery (Universal Description, for example. There are several areas where the two could work well together. Integration could combine the business logic of Web Services with the Semantic Web's meaningful content. Has suggested that the integration of Web Services and Semantic Web technology could offer significant performance improvement for Web applications, the inventor of the Web, tim Berners-Lee.

Ontology Web Language (OWL) for services (OWL-S) may be the most viable application. Recent industrial interest in such services and the availability of tools to enable service automation suggests the possibility that fast progress can be made. And monitor Web resources offering particular services with a high degree of automation, compose, invoke, users and software agents would be able to discover, through the Semantic Web.

And take into account issues of partial failure and concurrency, developers must consider the unpredictable latency of remote access, therefore. These agents must communicate by protocol stacks that are less reliable than direct code invocation. Web Service Architecture requires that discrete software agents work together to implement functionality.

And the ontology structuring mechanisms of OWL provides the appropriate framework to do this, web sites should be able to employ a set of basic classes and properties for declaring and describing services. An important goal for Semantic Web markup languages is to establish a framework for making and sharing these descriptions. A software agent needs a computer-interpretable description of the service and the means for access, to make use of a Web Service.

An Ontology is a taxonomy ( classes and relationships) along with a set of inference rules. While the how-questions are addressed as part of WSDL, at the application level that is meant to answer the what- and why-questions about a Web Service, oWL-S is a high-level ontology.

An ontology for Web Services would make Web Services machine understandable and support automated Web Service composition and interoperability, as a result.

Thereby providing automated functions for:

* service discovery,

* service execution,

* service composition,

* service monitoring.

A Semantic Web service describes its properties and capabilities so that software can automatically determine its purpose. Neither Web Service Description Language (WSDL) nor Universal Discovery and Description language (UDDI) allows for software to determine what a Web service offers to the client. An appropriate Web service, or discover, discovery: A program must first be able to automatically find.

This includes what the inputs and outputs of the service are. A Semantic Web service provides a descriptive list of what an agent needs to be able to do to execute and fulfill the service. The software needs to know how to interact with the service to complete the necessary sequence, if executing the service is a multi-step procedure, for example. Invocation: Software must be able to automatically determine how to invoke or execute the service.

The services have to interoperate with each other seamlessly so that the combined results are a valid solution. Composition: Software must be able to select and combine a number of Web services to complete a certain objective.

Monitoring: Agent software needs to be able to verify and monitor the service properties while in operation.

With these capabilities we will be able to program agents to locate and utilize Web Services all automatically.