Along with the ROSE project, I have also taken up a project where I will build some new Kwiki Extensions. Here are couple of extensions I will be looking at implementing:
SOAP:
The call would consist of the soap keyword followed by an amphersand seperated list of urlencoded name, value pairs seperated by an equal sign. Like so:
{soap: url=http://www.foo.com/service&temp=23}
The result of the call are places in the Wiki at the location of the call.
WSDL:
The call would consist of the wsdl keyword followed by the URL of the WSDL file. Like so:
{wsdl: url=http://www.foo.com/service?wsdl}
A pseudocode description of the interface described by the WSDL is placed in the page, along with a form that allows the SOAP service described by the WSDL to be tested.
XML and XSLT
The call would consist of the xslt keyword followed by an amphersand seperated list of urlencoded name, value pairs seperated by an equal sign. The names xml and xsl would be required and specify the URLs to retrieve the XML and XSL files. Like so:
{xslt: xml=http://www.foo.com/somefile.xml&xsl=http://www.bar.com/somotherfile.xsl}
Tie Into dbXML:
Still thinking…
- Should this be through a SOAP interface on the DB, or more direct?
- Reference should be by XPath
- How can we create a way to edit the data describged by the XPath query when we edit the page?
I’m thinking there’s an XForm’s tie-in here.
Orchestration
Still thinking…
- I was a page to represent each Web service; maybe the wsdl page as described above.
- Linking pages together using a sexpr-like language?
The listing found here can be found on the here. Phil Windley updates the KwikiExtensions page fairly frequently so you can check there to see updates to the extensions. I will also be posting progress reports as I go.