1. David Burdett May 11, 2004 Package Binding for WS CDL

2. 2 The Basic Idea Keep the existing CDL – essentially unchanged. –No new elements or attributes Define a new separate element - packageBinding, used to –Redefine selected parts of a package as defined in the current spec, –Complete parts of a package that were "missing" from the original definition, or –Some combination of both

3. 3 Example Choreo – Section 2.5.2.4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

4. 4 Example Choreo – Section 2.5.2.4 (cont) 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62

5. 5 Referencing the Package <package name="ConsumerRetailerChoreo" version="1.0"...... ; Note 1...... References The name attribute on the packageBinding element references a package (or another packageBinding ) Name of the Package Binding

6. 6 <package name="ConsumerRetailerChoreo" version="1.0"......... ; Note 1... ; Note 2... Replacing a value References Replacement value Elements within the packageBinding element (e.g. informationType ) specifies either the replacement value for an element (or attribute) within the original package …

7. 7 <package name="ConsumerRetailerChoreo" version="1.0"......... ; Note 1... ; Note 3... Adding in a missing value References Missing value … or the value of an element/attribute that was missing from the original definition, e.g. the informationType of the retailerRef token.

8. 8 Sample Package Binding 63 ; Note 1 64 ; Note 2 65 ; Note 2 66 ; Note 3 67 ; Note 3 68 ; Note 4 69 ; Note 4 70 ; Note 5 71 ; Note 5 72 ; Note 5 73 ; Note 5 74 If we agree with the approach, we need to work out what can get replaced or over-ridden

9. 9 Different Choreography levels Abstract Portable Concrete No endpoint information defined All endpoint information fully defined Some endpoint information defined ContinuousContinuous