2010
InfoQ: WS-I closes its doors. What does this mean for WS-*?
by nhoizeySo the question remains: has interoperability pretty much been achieved for WS-* through WS-I and the improvements made with the way in which the specifications and standards are developed today, or has the real interoperability challenge moved elsewhere, still to be addressed?
2008
WSO2 Web Services Framework for PHP | WSO2 Oxygen Tank
by nhoizey & 2 othersWSO2 WSF/PHP is a complete solution for building and deploying Web services, and is the only PHP extension with the widest range of WS-* specification implementations
2007
REST vs. WS-*: War is Over (If You Want It) :: David Chappell :: Blog
by nhoizey & 1 otherREST is for data-oriented applications that focus on create/read/update/delete scenarios. Solution based on WS-* for service/method-oriented applications, especially those that need more advanced behaviors such as transactions and more-than-basic security
Radovan Janecek: Nothing Impersonal: Mental Exercise
by nhoizeyIs HTTP GET/POST enough for you? Fine. Then you are simply not the 'right target' for web services evangelists ;-)
Radovan Janecek: Nothing Impersonal: WS-Transfer and WS-Enumeration
by nhoizeyThe WS-Transfer one is nice because it allows REST style of interactions.
Radovan Janecek: Nothing Impersonal: September 2004 Archives
by nhoizey (via)Will there be still 97% of simple REST services on the web then? Yes, sure. WS-* does not compete with browser-oriented applications or simple-get-then-do-regexp interactions
Sam Ruby: Tolerance
by nhoizey (via)acceptable levels of tolerance differ depending on whether or not a given operation is safe or not
michaelhanson.blogspot.com
by nhoizey (via)to implement Web Services Security with the X.509 Certificate Profile, you also need to implement XML Signature (which includes XML Canonicalization and XML Exclusive Canonicalization) and XML Encryption. To correctly handle imports of WSDL1.1 documents (and validate the traffic they describe), you need to support the entire behemoth that is XML Schema -- in particular if you are attempting to support RPC-oriented SOAP, which informally requires you to support the entire XML Schema Datatypes specification. Don't forget support for SOAP with Attachments, either!
2006
The Cafes » REST vs. WS-*: A Parable
by benoit & 1 otherMy name’s Rusty, and I’m an air conditioning tech.
1
(12 marks)