[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebxml-bp] Dynamic (late) binding proposal - take 2 now withdiagram
Discussion|OASIS.ebBP.WI-53-55-LateBindingConditions; Topic|; Point|Conditions for Process Description; Attachment|http://www.oasis-open.org/archives/ebxml-bp/200404/msg00131.html; mm1@ > Tell: Please find the following diagram outlining one way of > formulating dynamic or late bound TimeToPerform or similar parameters. mm1: Reference attached [1]. > At the top there is a abstract superclass that does not turn up in the > document, the concrete subclasses does. > > The BindingTime speficies when binding occurs, i.e. which > collaborationEvent(s). (maybe this should also be an element?) > Default value is the value before binding occurs > TTP duration can be ORed together with Union. > > <TimeToPerform boundWhen="enclosingCollaborationInitiationEvent"> > <Union> > <StaticTimeToPerform>2h<StaticTimeToPerform> > > <RequestMessageTTP>//MessageEnvelope//ResponceTime</RequestMessageTTP> > </Union> > <TimeToPerform> > > This patterm may be used for other parameters that are candidates for > dynamic binding.. mm1: Anders and Lars, we identified these potential attributes in the meeting on Wednesday [2] 1. Duration (**) 2. Type - Provide range of enumeration values (**). a. Design b. Configuration c. Runtime 3. Default 4. Default type 5. Build conditionality into the Type for when it can be changed (**-via boundWhen) I would suggest if we identify when and to what extent the business process criteria are changed, we identify if a default is provided and if it could be accessed (3,4 above). There is also a slightly different question related to if the value is given or must be acquired. I would suggest we accommodate both, if the functionality is supported by the team. I am not certain this nuance is referenced in the model example you provided. Thanks. [1] Attachment with referenced diagram: http://www.oasis-open.org/archives/ebxml-bp/200404/msg00131.html. Actual attachment provided herein as well for interested parties. [2] Items I see in your proposal identified by (**). @mm1
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]