Welcome to BPEL XML.org.

This is the official community gathering place and information resource for the WS-BPEL OASIS Standard and related specifications. BPEL uses Web services standards to describe business process activities as Web services, defining how they can be composed to accomplish specific tasks. This is a community-driven site, and the public is encouraged to contribute content.

Free Webinar: Using Lean SOA Development Tools to Accelerate Application Delivery

Location: 
https://www2.gotomeeting.com/register/419606870
Date: 
22 Oct 2008 - 14:00 - 15:00
Event Type: 
Webinar

SOA Governance

  • Understand the difference between run-time and design-time SOA governance.
  • Leverage SOA management and SOA Registry/Repository tools in your governance efforts.
  • Define governance processes that will work in the culture of your organization.
  • Determine the people in your organization that must be involved in the governance efforts.
  • Define the policies that will help your organization achieve its SOA goals.

Read more

SOA Governance

SOA Governance is the key to a successful adoption of Service-Oriented
Architecture. It is the process of establishing a desired outcome for
your efforts, and then leveraging people, policies, and processes to
make that outcome a reality. This includes technical policies and
standards that guide your design-time activities, policies and
processes that impact your project selection and funding decisions, and
finally run-time policies that impact your operational management
activities.

Read more

Learn SOA Governance with New Book from Packt

SOA Governance is a new book from Packt that teaches users to improve a company's efficiency and productivity using service-oriented architecture governance. Written by SOA Consortium member, Todd Biske, this book acts as a detailed guide to choose the right people, processes, and policies to achieve successful SOA Governance within a company.

Read more

qname and namespace context

Section 8.4.1 ("Namespace Context") specifies that namespace context must be preseved when copying attribute values or text nodes from the source to the destination. There are a number of complexities in this, and in some cases it is impossible.

For instance, attribute alpha created by <copy> #1 may require prefix P to be bound to foo.com while attribute beta created by <copy> #2 for the same element my require prefix P to be bound to bar.com. This conflict cannot be resolved.

Read more

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I