What is the need for the OASIS Provisioning Services Technical Committee?
One of the biggest challenges in provisioning is adapting to a disparate set of protocol and methodologies. This poses a challenge to both provisioning vendors and implementers of custom provisioning systems. The industry would benefit if some level of standardization could be brought to bear on this problem.
Who should be involved in the development of the Service Provisioning Markup Language (SPML)?
Any vendor that develops provisioning systems or intends to integrate with provisioning systems is encouraged to join the OASIS Provisioning Services Technical Committee, as well as any organization that develops custom built provisioning solutions or is involved in identity management.
Who will benefit from SPML and how?
Both provisioning vendors and their customers will benefit from increased standardization. The will result in lower costs, quicker implementations, and a wider range of supported systems.
How does SPML compare with related efforts at other standards organizations? When will this specification be completed?
The SPML 1.0 specification is built on the OASIS Directory Services Markup Language v2 specification, although it is focused on provisioning. Additionally there is a relationship, although not an overlap, between SPML 1.0 and federated identity standards, such as Project Liberty. The SPML 1.0 specification support identifying principles using the OASIS Security Assertion Markup Language (SAML) and Project Liberty standards. Additionally, the SPML 1.0 specification has been designed to accommodate the use of the OASIS Web Services Security (WSS) specification, XML Digital Signatures, and XML Encryption.
The SPML 1.0 specification has been approved as an OASIS Committee Draft by the OASIS Provisioning Services Technical Committee and will soon be submitted to the OASIS membership at-large for voting as an OASIS Standard.