OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Updated Committee Spec docs and RDDL


Hi everyone,
 
  In order to shortcut further delays, I've taken the liberty (with Diane's okay) to update the specification with the latest cover page(s) metadata as well as update the RDDL file. There's one new bit of metadata that was recently approved by the Board of Directors concerning trademarks. More information can be found here: http://www.oasis-open.org/who/trademark.php. Note that the last paragraph in the status section contains a field for any additional terms that should be trademarked and will need to be updated.
 
Regards,
 
Mary
 
---------------------------------------------------
Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org  
web: www.oasis-open.org
phone: 603.232.9090
 
OASIS Symposium:
"eBusiness and Open Standards:
Understanding the Facts, Fiction, and Future"
15-18 April 2007 San Diego, CA USA
http://www.oasis-open.org/events/symposium/
 
 

wsbpel-v2.0-CS01.doc

Title: OASIS Web Services Business Process Execution Language (WS-BPEL) 2.0
http://www.oasis-open.org
  www.oasis-open.org About OASIS OASIS Members Join OASIS OASIS News OASIS Events Members Only XML Cover Pages XML.org  

Web Services Business Process Execution Language (WS-BPEL)

31 January 2007

Introduction

This document describes version 2.0 of the WS-BPEL namespace. It also contains a directory of links to related resources using the Resource Directory Description Language (RDDL) 2.0.

Namespace URI Versioning Policy

It is the intent of the OASIS WS-BPEL Technical Committee that the WS-BPEL v2.0 namespace URI will not change arbitrarily with each subsequent revision of the corresponding WSDL or XML Schema documents but rather change only when a subsequent revision, published in conjunction with a Committee Specification, results in non-backwardly compatible changes from a previously published Committee Specification.

Under this policy, the following are examples of backwards compatible changes that would not result in assignment of a new namespace URI:

  • addition of new global element, attribute, complexType and simpleType definitions
  • addition of new operations within a WSDL portType or binding (along with the corresponding schema, message and part definitions)
  • addition of new elements or attributes in locations covered by a previously specified wildcard
  • modifications to the pattern facet of a type definition for which the value-space of the previous definition remains valid or for which the value-space of the preponderance of instance would remain valid
  • modifications to the cardinality of elements for which the value-space of possible instance documents conformant to the previous revision of the schema would still be valid with regards to the revised cardinality rule

Related Resources for WS-BPEL v2.0

Normative Reference:

WS-BPEL v2.0

XML Schemas for WS-BPEL v2.0:

ws-bpel_abstract_common_base.xsd

ws-bpel_executable.xsd

ws-bpel_plnktype.xsd

ws-bpel_serviceref.xsd

ws-bpel_varprop.xsd

Related Namespaces



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]