[Home] [By Thread] [By Date] [Recent Entries]


It will be interesting to see what the characteristics equivalent 
to standard certification/QoS processes for web service developers 
will be (eg., Software Capability Maturity Model), how one will 
report bugs, provide Change Requests, and so on.  If software 
agents are dynamically composing services, how do they note that, 
who do they report it to (other bots?), how do they follow up, 
and so on.  It seems that a lot of necessary legal infrastructure 
is being bypassed, or that this stuff is too experimental to 
warrant it.  In either case, one questions the maturity if not the 
sophistication both present and needed.

There are a lot questionable procurement issues here.

len

From: Ken North [mailto:kennorth@s...]

There's been work on more sophisticated solutions -- for example, semantic
web
services based on an ontology language (OWL-S or WSMO). There's more
information
in "Developing Semantic Web Services" by Peter Alesso. Here's an excerpt:

http://www.webservicessummit.com/Excerpts/BuildingSemanticWS.htm

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member