Name
Abstract | ||
|---|---|---|
accept and produce. The selection may be done by an abstract reasoner, such as a planner, which uses these descriptions to infer that a specific combination of Web Services will achieve a desired purpose. These services may not previously have been intended to work together. Some proponents of Semantic Web Services optimistically envision that ap- plications can be composed from distinct Web Services to operate on valuable data, execute reliably and provide accountability without much diculty. Yet there is still a gulf between this vision and reality. Software engineering expe- rience suggests that the development of reliable software requires following a methodology including analysis, design, testing, and validation. Since Web Ser- vice combinations will need to be reliable, lessons from software practice and experience should be intently applied to Semantic Web Services. How can this be done? Software generated by humans,is more likely to be reliable if it is developed from sound and well-documented designs, written according to coding standards, and subject to comprehensive testing. Since the Semantic Web Services compo- sitions are expected to be composed by a machine, the design may not be docu- |
Year | Venue | DocType |
|---|---|---|
2004 | SWS@ISWC | Conference |
Citations | PageRank | References |
0 | 0.34 | 2 |
Authors | ||
2 | ||
Name | Order | Citations | PageRank |
|---|---|---|---|
| Bruce Spencer | 1 | 113 | 19.12 |
| Sandy Liu | 2 | 54 | 8.47 |