- From: Gilbert Pilz <gilbert.pilz@oracle.com>
- Date: Thu, 30 Jul 2009 15:03:21 -0700
- To: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
- Message-ID: <4A7218A9.8000807@oracle.com>
Hey all, You may remember that, during the discussions of our proposal for 6401 [1] at the last F2F, I mentioned several times that it would be 'relatively easy' to write an XSLT that transformed a wse:EventDescriptions element into a WSDL document that described the Event Sink interface for Raw Notifications of the Events described in the EventDescriptions? Attached is an XSLT 2.0 stylesheet that does just that, along with a sample EventDescriptions document and the Event Sink WSDL that is generated from that document. This illustrates the following points: 1.) The data model for EventDescriptions contains the necessary information to generate an Event Sink WSDL. 2.) The rules defined in Appendix F of our proposal are sufficiently rigorous to permit the independent implementation tools that transform an EventDescriptions to an Event Sink WSDL that correctly describes the corresponding Raw Notifications. People shouldn't take my word for this. They should look at the attached EventsToWSDL.xsl (which has been documented to point out which rules are being implemented by which templates) and make sure there is no "secret sauce" that isn't described in Appendix F. 3.) The implementation of such a tool is, indeed, relatively easy. It took me about 6-7 hours to write this stylesheet with some help from Tom, Doug, and Bob. Keep in mind that I tend to write one XSLT about every two years or so and that much of this time was spent reading Doug Tidwell's "XSLT, 2nd Edition". [1] http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0046.html - gp
Attachments
- text/xml attachment: EventsToWSDL.xsl
- text/xml attachment: oceanevents.xml
- text/xml attachment: oceansink.wsdl
- text/xml attachment: oceanwatch.xsd
Received on Thursday, 30 July 2009 22:04:21 UTC