Difference between revisions of "Web services transport protocol"
Charliemccay (talk | contribs) |
Charliemccay (talk | contribs) |
||
Line 1: | Line 1: | ||
+ | Status report from Roberto Ruggeri 22/3/07 | ||
+ | |||
We received a good deal of feedback on the Web Services profile and it’s actually being used in many countries around the world. IHE is also starting building profiles that are based upon it starting with the PIX/PDQ using HL7 v3 and Web Services and the new XDS profile (that I am writing) that uses SOAP/WSDL and MTOM for binary attachments. | We received a good deal of feedback on the Web Services profile and it’s actually being used in many countries around the world. IHE is also starting building profiles that are based upon it starting with the PIX/PDQ using HL7 v3 and Web Services and the new XDS profile (that I am writing) that uses SOAP/WSDL and MTOM for binary attachments. | ||
Latest revision as of 16:49, 22 March 2007
Status report from Roberto Ruggeri 22/3/07
We received a good deal of feedback on the Web Services profile and it’s actually being used in many countries around the world. IHE is also starting building profiles that are based upon it starting with the PIX/PDQ using HL7 v3 and Web Services and the new XDS profile (that I am writing) that uses SOAP/WSDL and MTOM for binary attachments.
All the specs that are referenced by the Web Services profile have been either approved by major standards bodies (WS-Trust and WS-SecureConversation approved by OASIS this week, WS-Addressing approved by W3C) or very close to being approved (WS-ReliableMessaging by OASIS). Once that happens we will take the WS profile to normative.
You should expect a minor revision soon as I incorporate the feedback from our latest ballot cycle.
In the meantime all the referenced specs are implemented in an interoperable fashion in all the major web services platform and very little is expected to change between the implemented specs and the approved standards. The fact that the HL7 WS profile is not yet normative should not deter you from starting implementation today and realizing its value.