Internet/Distributed Computing using HTTP/POST: Bridge semantic W eb and Web services under the same Internet protocol

My article "Internet/Distributed Computing using HTTP/POST: Bridge semantic
Web and Web services under the same Internet protocol" is published by IBM
DeveloperWorks and can be accessed at:

http://www-128.ibm.com/developerworks/library/ws-intdist/ 

Actually this paper discussed about two main issues: 

1. Service aggregation processes should not be a part of the service
semantics. Please pay attention to the explanation to the case of using
www.expedia.com to buy ticket, reserve hotel and rental car. Anyone who
tried to use such online services can be easily understand that the
requester is waiting for an answer other than a complex framework or process
model or mediator for service aggregation, etc. In conclusion, service
requesters do NOT care how service providers process their request but only
want to get an answer.

2. Since all functions, offered by the so-called "Web services", can be
implemented directly by using HTTP protocol without the need of any other
extra frameworks like WSDL, SOAP, etc., we can bridge semantic Web and Web
services under the same Internet protocol and unite both REST and WSDL Web
services within the same semantic service description framework. WSDL can
eventually be deprecated sooner or later since at least it is not a must in
developing semantic Web services, if we now can find an easy and simple way
to do the exactly same thing.

While McCool talked about "Rethinking the Semantic Web" in 2005 IEEE
Internet Computing Issue Nov./Dec., I suggest that we rethink about semantic
Web services. Semantic Web technology is designed for information search on
the Internet. SW targets at the static content inside the HTML document.
However, as I said before, Web services are about functions and actions. How
can we use such a static technique to deal with the dynamics in Web service,
especially now, considering I already demonstrated that service aggregation
processes should not be a part of the service semantics? Was it because that
we have to use logic to do something because logic inference and ontology
are the bases of semantic Web? Now that we do NOT need to include any
process of service aggregation into service semantics description, whatelse
can be the role of logic or OWL in describing the meaning of the functions
and actions in Web services - remeber that functions are not part of any
existing ontology languages?

Any critical comments and advice will be greatly appreciated.

Received on Friday, 20 January 2006 06:30:06 UTC