...ask. This requires a service description, with more defined semantics than WSDL including pre- and post-processing conditions so that conditional workflows
26 KB (3,981 words) - 01:37, 3 March 2009
...so be described as a WSDL document. In fact, [http://www.w3.org/TR/wsdl20/ WSDL 2.0] allows binding to HTTP methods and supports a RESTful interface.
...ing]), and the [http://www.w3.org/TR/wsdl20-adjuncts/ Adjuncts part of the WSDL 2.0 spec] (and specifically the [http://www.w3.org/TR/wsdl20-adjuncts/#http
25 KB (3,899 words) - 14:44, 15 June 2009
...uation goes a long way to explain why standard industry practices (write a WSDL, generate client and server bindings, implement service) have not seen wide
5 KB (633 words) - 15:42, 12 March 2009
...at this moment, anyway) as the description of these many web pages. In the WSDL, the possible (allowable) contexts for GET/PUT/POST/DELETE requests are des
So how does the agent "browse these pages"? By first requesting the WSDL instance. Since it is "computable" (i.e., has a defined syntax and semantic
58 KB (9,064 words) - 23:30, 20 April 2009
:* ''Under the hood could be a mashup driven by WSDL/RESTful interfaces among the data providers, or (at a slightly higher level
29 KB (4,320 words) - 15:48, 12 March 2009
* [http://www.w3.org/TR/sawsdl/ SAWSDL], Semantic Annotations for WSDL and XML Schema (W3C Recommendation 28 August 2007)
19 KB (2,885 words) - 15:03, 26 October 2009
...]. The end result is a file such as [http://nexml.org/nexml/phylows/tolweb?wsdl this one]
''Graphical representation of [http://nexml.org/nexml/phylows/tolweb?wsdl this] service description.''
4 KB (707 words) - 00:00, 13 March 2009
* as the web page descriptions are not always right - hit the wsdl file for what needs to be passed.
* through experimentation this appears to work (using the wsdl file parameters not the web page parameters).
10 KB (1,414 words) - 11:55, 13 March 2009