WS-SecurityPolicy member familiarization has begun
WS-SecurityPolicy is a keystone in enabling secure web services. This specification provides a set of WS-Policy assertions for describing the desired security characteristics of web service messages. More specifically it provides the ability for the expression of requirements related to WSS, WS-SecureConversation and WS-Trust. This specification has been under development within the OASIS WS-SX TC for over a year now. I’m happy to say that the OASIS member familiarization period for the specification began this month. So what does that mean?
At OASIS a specification must be approved by at least 15% of the membership to become an OASIS standard. When a specification is deemed mature enough by a an OASIS Technical Committee (TC) it is submitted to the OASIS staff. The staff then initiates a member familiarization period on the first of the month after the request is made. The membership has 15 days to become familiar with the specification. On the 15th of the month the specification is placed on a ballot on which the voting representative for each member company at OASIS can cast a vote in favor or opposed to the specification becoming an OASIS standard.
If your company is an OASIS member and you are not familiar with the specification now is the time. Copies of the specification in all of you favorite document formats can be found at the WS-SecurityPolicy namespace location: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702
Will I be back here asking for your vote come the 15th of June? You’d better believe it.
June 5th, 2007 at 11:43 am
[…] Continue… by mgoodner Anonymous comments are disabled […]
June 14th, 2007 at 8:55 am
Congratulations on the new blog!
Just wanted to say your explanation of the OASIS rules show what a farce it is. Why is 15% of the OASIS membership a magic number? You can get 15% of the population to do almost anything - even approve of the job Bush is doing ;-). I especially love the oxymoron “OASIS standard.”
WS-SecurityPolicy is a standard because of the community of implementers and users involved. Having it be an OASIS standard is a pretty substance-free gesture. Sorry you’ll have to invest some time in getting it there, but maybe you can use it as a milestone to hold a big party celebrating all the real work that’s gone into the specification.
September 4th, 2007 at 6:06 pm
[…] I see now that I never addressed my own post on WS-SecurityPolicy being up for approval as an OASIS standard (yes it was approved) a brief recap of the WS-* specifications approved as standards this year […]