PUBLIC MARKS from nhoizey with tag ws-*

So 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?

The Web Services Interoperability Organization (WS-I) today announced that three of its Profiles have been published by the International Organization for Standardization (ISO)

WSO2 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

REST 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

Des tonnes d'infos intéressantes sur SOA et les Web Services, par Pierre "Orchestra Networks" Bonnet

"The place to really watch, if you're a conservative watcher and you don't want to watch much in the industry about these emerging specifications is WS-I," he said. "It's putting together answers to technical questions that people need answered if they want things to work together for Web services interoperability."

Is HTTP GET/POST enough for you? Fine. Then you are simply not the 'right target' for web services evangelists ;-)

The WS-Transfer one is nice because it allows REST style of interactions.

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

acceptable levels of tolerance differ depending on whether or not a given operation is safe or not

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!