List of changes between March 31 and May 5 versions

I have attached my list of changes.  Please review for
accuracy and completeness.

 

Satish

 

Title: Changes from March 31 Draft in M

	
	
		

			
			

				Changes from March 31 Draft in May 5 Final 
				version of BPEL4WS 1.1  
				Terminology Changes
				
The following terminology changes have occurred 

				
					
Service Links are now called Partner Links 
					

					
Service Link Types are now called Partner Link Types 
					

					
Service References are now called Endpoint References 
					

				
				
The formal syntax has also been changed to reflect these 
				terminology changes, including the replacement of the current
				partner element with a partnerLink 
				element to reflect the fact that such a link is a conversational 
				interface rather than reflective of a business relationship. A
				partner element reflective of a business 
				relationship is added as described in the next section.

				Feature Changes
				
The following changes have been made 

				
					
The terminate activity is now strictly 
					limited to executable processes. 
					

					
Partner Link Type Roles are now limited to a single WSDL 
					portType. 
					

					
A new partner element is added to allow 
					grouping of Partner Links based on expected business 
					enterprise relationships. 
					

					
Endpoint references (formerly service references) are 
					now defined as given in WS-Addressing [1]. 
					

					
Message Properties are now limited to only be simple 
					types. 
					

					
Web service interactions in abstract processes are now 
					permitted to omit references to variables for inbound and 
					outbound message data. 
					

					
Opaque assignment in abstract processes may now target 
					Boolean variables, and variables of simple but unbounded 
					types. In the latter case the semantics requires creation of 
					a unique value similar to a GUID. 
					

					
The syntax for defining variables has been changed to 
					use three mutually exclusive attributes messagetype, type 
					and element. The first points to a WSDL message type 
					definition. The second points to an XML Schema simple type. 
					The third points to an XML Schema global element definition. 
					This allows one to define variables using something other 
					than WSDL message types. Only variables that are defined 
					using messagetypes can be used as input or output targets in 
					messaging operations. 
					

					
The ability to provide an in-line WSDL message type has 
					been removed, since the vast majority of the uses of this 
					feature will be replaced by the usage of XML Schema simple 
					types and global elements. 
					

					
Correlation sets have now been added to the uniqueness 
					requirement so that it is not legal to have two web service 
					interactions outstanding if they have the same partner, port 
					type, operation and correlation set(s). 
					

					
In case of activity termination, the activities 
					wait, reply and invoke are 
					added to receive as being instantly terminated 
					rather than being allowed to finish. 
					

					
The variable provided as the value of the 
					faultVariable attribute in a catch 
					handler to hold fault data is now scoped to the fault 
					handler itself rather than being inherited from the 
					associated scope. 
					

				
				
					
					
						

							
							

								
[1] "Web Services Addressing 
								(WS-Addressing)," BEA, IBM and Microsoft, March 
								2003:

								

								
								http://msdn.microsoft.com/ws/2003/03/ws-addressing/

								

								
								http://www-106.ibm.com/developerworks/library/ws-bpel/

								

								
								http://dev2devbea.com/technologies/webservices/ws-addressing.jsp