Tell 5/23/2004: Dynamic (late) binding proposal - take 3 now withdiagram [RSD]

["Monica J. Martin" <Monica.Martin@Sun.COM>]

Discussion|OASIS.ebBP.WI-55-LateBinding Update;
Topic|;
Point|Basis for Future Conditionality Pattern;
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200405/msg00116.html;

mm1@
Anders,
I would be very interested if this pattern can be used as a basis for 
future conditionality on attributes we wish to transition to elements, 
and allow for variability in their usage.

Can we explore this under new business in tomorrow's call?

We appreciate your work on this item for the team.

Thanks.

Note: The attachments can be found on the attachment URL above.

> Tell: Please find next version 3 of the LateBinding Pattern.
>
> This version has some new apspects in it such as the possibility to 
> relate binding to Events,
> The bindingTime contains an initial set if types but could be extended 
> to handle more variations.
>
> The bindingBasis points to an runtime instance of CA-BI or BAT-BT and 
> together with the boundEvent it determines when the value is 
> instantiated. It also open up for possibly adding Timers in V3, ie if 
> nothing happens for 3 hr a Timeout could be establised.
>
> The following example show hows to pick out a TTP from the request 
> message
> <BusinessTransaction>
>  <RequestMessageTTP defaultTTP="2h" boundWhen="OverridePossible"
>                          bindingBasis="./RequestMessage" 
> boundEvent="CompletionEvent" >
>     ./MessageEnvelope//ResponceTime
>  </RequestMessageTTP>
> </BusinessTransaction>
>
> Reference path is:
> BTANameID/RequestMessage/MessageEnvelope//ResponceTime
>
> The VariableTimeToPerform and ExternaTTP and optional future elements 
> where you can can get values from a runtime "variable" (this is of 
> course not part of V2) and external is an extensionmechanism for the 
> brave ones who want to sidestep the BPSS and enter into the area of 
> possible and unforseen sideeffects.
>
> /anders 

@mm1