Tracking change and innovation in the enterprise software development community
Testing Tools to
Support Agile
Software Delivery
Whitepaper
TargetProcess:
Plan, Track
Succeed with
Agile PM tool.
Free Download!
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Tools to get
Visual Studio
2008 Projects
Under Control
Posted by Miko Matsumura on Oct 23, 2006 08:30 AM
According to the working group: "Web Services Policy defines a flexible policy data model and an extensible grammar for expressing the capabilities, requirements and general characteristics of a Web service, and defines mechanisms for associating policies with Web service constructs."
WS-Policy is a significant standard in the realm of SOA run time governance, and has recieved the attention of many vendor organizations.
The WS-Policy working group recently published a primer which provides an introductory description to this policy language using numerous examples. The WS-Policy Primer 1.5 document lists the following organizations as editors of the working draft: Microsoft Corporation, BEA Systems, Inc., IBM Corporation, Layer 7 Technologies, and webMethods, Inc. The specification has existed since 2002, but was not submitted to the W3C (World Wide Web Consortium) standards organization until recently in spring of 2006.
The submission of the specifications to the W3C have reduced one of the major objections to adoption, and it's likely that more vendors will support WS-Policy going forward. However, one of the issues frequently raised with WS-Policy is that it does not sufficiently articulate policy semantics to the extent needed for many applications of policy in the Web Services realm. While very extensible and flexible, this flexibility does not always produce interoperability between vendor implementations.
The WS-Policy 1.5 Working Drafts can be downloaded here.
Five Ways to Fail When You Scale
The Key to SOA Governance: Understanding the Essence of Business
eBook: Key Strategies for SOA Testing
Offshore software development: Making it a success with Agile Practices
Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He presents the factors which contributed to the success of BMC's Agile adoption.
In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.
David Laribee discusses the purpose of ALT.NET, its mission and future.
Ruby on Rails has become a popular Ruby framework for creating web applications in recent years. An aspect of creating a web application is the need to repeatedly create the same base functionality.
Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.
Shaw and Fowler talk about the need for a new relationship between the business department and the IT department. Studies have shown that projects mostly fail due to miscommunication between the two.
In this article, Jim Webber, Savas Parastatidis and Ian Robinson show how to drive an application's flow through the use of hypermedia in a RESTful application.
Eccentric artist turned overnight anti-celebrity, Giles Bowkett captures the heart and soul of RubyFringe as he demonstrates his revolutionary Archaeopteryx MIDI drum pattern generator.
No comments
Reply