Where do the WS-Secure Conversation and WS-Trust specs stand?
Nadalin: We are ready to do our interops (interoperability workshops Oct. 5 and 6 in Austin, Texas. These workshops are gatherings of companies with implementations of these specifications where feedback is exchanged.) We hope once these are complete that we don’t need to rev the specs and we can take them to standards body. That’s basically the direction we’re taking with all of our specs. We’re also working on a policy specification and the W3C is holding a workshop on policy in Oct. where we’re going to present papers. The W3C is ready to determine whether to do a technical committee on policy. Are there too many specifications, or are they a necessary evil? Nadalin: There are quite a few and you have to take this into consideration. Even at IBM, we query a standards base when starting a project to make sure we’re not duplicating efforts. There has been definite duplication in some areas like reliability and reliable messaging that need to get worked out. As standards progress, the
Related Questions
- What market trends, compliance and governance issues affect VaporStream Electronic Conversation Software?
- Is security still the major impediment to Web services deployments?
- Is security still the major impediment to Web services deployments?
- Where do the WS-Secure Conversation and WS-Trust specs stand?
- How does Java technology relate to SOA/web services?
- How does Java technology relate to SOA/web services?
