BPEL XML.org - Online community for the Web Services Business Process Execution Language OASIS Standard
Welcome to BPEL XML.org. This is the official community gathering place and information resource for the WS-BPEL OASIS Standard. WS-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.

• Understanding Technical Writing
  

  Technical writing is primarily concerned with communicating scientific, technical, and business information so that readers can understand and use it. It is different than writing fiction or magazine articles, where a mood may be set or--in some cases--where space must be filled and is definitely not the same as creative writing where use of action verbs and colorful adjectives and imagistic metaphors are encouraged.

  read more

• New book on Service Oriented Architecture and its Approach to Integration Published by Packt
  
• Intalio
  
• Intalio|BPMS Server
  
• Apache ODE
  
• DataDirect® Shadow® Version 7 Includes Native BPEL 2.0 Runtime and Eclipse-Based Studio with BPEL Developer
  
• Intelligent Enterprise: Roundtripping Revisited
  
• Restrictions on query language in assignments
  

  In section 8.4, after listing the to-specs:
  “The restrictions listed in 8.2.4 Default use of XPath 1.0 for Expression Languages MUST apply to XPath used as a query language.”

  Query language is only used in the Variable Variant of the to-spec, but applying the restrictions of section 8.2.4 on the query would remove the context node, thus making the variable and part attributes irrelevant.

  read more

• InfoWorld: Iona upgrades open, closed source SOA
  
• Isolated scope semantics
  I want to clarify the semantics of the Isolated Scope as defined in "Web
  Services Business Process Execution Language Version 2.0" specification.
  
  Let's define a use case as a process with two concurrent isolated scopes
  that work on a shared set of variables. What is the correct semantics of
  such process?
  
  a) 2 isolated scopes are seen as database serialization transactions.
  Once you enter each scope you work with the snapshot of variable values
  you observed. So commits in one scope will be not seen in the second

  read more