TMCnet News

The Godot of Web services specs is submitted to the W3C after its developers correct an ommission.
[April 28, 2006]

The Godot of Web services specs is submitted to the W3C after its developers correct an ommission.


(www.esecurityplanet.com Via Thomson Dialog NewsEdge)
WS-Policy has been submitted to the World Wide Web Consortium (W3C) for formal approval as a standard after its developers filled a hole in the spec that made companies reluctant to write to it.

The move should open the floodgates for Web services security specifications that have been held up by the omission.

WS-Policy was introduced in 2002 by IBM, Microsoft, BEA Systems and others as a means for Web service to express their requirements and policies to other Web services.

These requirements include security constraints, protocol support and message encoding information.

A number of specs are dependent on WS-Policy, including WS-Trust, WS-SecureConversation, WS-ReliableMessaging and WS-Transactions, all of which have been submitted to standards bodies for official approval.

For example, WS-Policy allows users to express policy assertions through assertion languages like WS-SecurityPolicy and WS-ReliableMessaging. It's possible to mix and match the policies.

But WS-Policy was not approved by the W3C because it lacked a definition for how to execute "nested policies." This omission caused a delay in standards development because no one wanted to write for a spec still in flux.

Nested policies enables a policy to have one or more policy within it. A clear definition of how to do nested policies had to be added to WS-Policy, which was thought to be ready for submission to the W3C last year.

This article was first published on InternetNews.com . To read the full article, click here .

Internet.com Corp.

Copyright 2003 Jupitermedia Corp. All rights reserved.
Republication and redistribution of Jupitermeida Corp. content is
Expressly prohibited without the prior written consent of Jupitermedia
Corp.. Jupitermedia Corp., shall not be liable for any errors
or delays in the Content, or for any actions taken in reliance thereon.

[ Back To TMCnet.com's Homepage ]