W3C Publishes Web Services Policy 1.5 -- Visual Studio Magazine

W3C Publishes Web Services Policy 1.5

By Kurt Mackie
09/05/2007

Group devises a more flexible method of handling policy changes for Web services and service-oriented architectures.

The World Wide Web Consortium (W3C) published its Web Services Policy 1.5 Framework recommendation, which lays out a blueprint for creating extensions to a Web service. The objective of the Framework is to make life easier for developers, especially in terms of enabling security and messaging.

The Framework specifies a more modular approach to enforcing Web services policy, using XML code that operates at the domain level. Policy changes can be made "without disruption or requiring changes to lower level service descriptions," according to an announcement issued by the W3C.

Under the Framework, the service's policy can contain "policy alternatives," which in turn contain "policy assertions." A snippet of code with multiple policy assertions is shown in the W3C's recommendation (Example 1-1).

The spec's security assertions were tested by some of the companies in the W3C's Web Services Policy Working Group. The spec was also reviewed by some of OASIS' Web Services Technical Committees, including UDDI, WS-RX, WS-TX and WS-SX.

The Web Services Policy 1.5 spec was also coordinated with the W3C's WS-Addressing Working Group, which released its own recommendation on metadata addressing, which is called "Web Services Addressing 1.0."

Companies in the W3C's Web Services Policy Working Group expressed support for the Web Serves Policy 1.5 Framework in their testimonials, with some suggesting that their companies' products will utilize the spec.

The Framework will lead to "compatibility" improvements in the Web services realm, according to Don Deutsch, Oracle's vice president of standards strategy and architecture.

"By allowing interactions between Web components to be tailored at runtime based on declarative specifications, WS-Policy promotes flexibility and enhances compatibility," Deutsch stated.

The spec will also improve operations for service-oriented architectures (SOAs), according to David Orchard, BEA Systems' senior technical director.

"A key aspect of Service Oriented Architecture deployments is the description of the services, and WS-Policy can enhance service description and can represent a crucial building block for SOA and other related initiatives such as Service Component Architecture (SCA)," Orchard stated.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.