[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [ebBP] 3/14/2004: WI 55-Late Binding [RSD] Proposal for Vote
Discussion|OASIS.ebBP.WI55-Late Binding; Topic|; Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00250.html; Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00231.html; Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00042.html; Point|Summary for consideration and vote; mm1@ The fourth Work Item for summary closure is: Late Binding and Time-to-Perform Work Item 55 Work Item Summary For timeToPerform, we found it depends on the context used in the collaboration. For example, for a binary collaboration TTP may be 24 hours but at late binding be reduced to 6. How is this handled? Relates to WIs: 27 Control flow parameters (explicit support for NOF_ 58 Separate dialogs from agreements 59 Additional business transaction support Summary Resolve a. Provide an element that allows expression of late binding or extensibility for Time to Perform. b. Assign a type that may later allow for a substitution group and to support other external mechanisms. Note: This could allow the use of an external mechanism such as CAM. c. Provide guidance to the implementor on proper use of such mechanisms to bound substitution mechanism. Note: This guidance is being suggested in order to encourage the proper use of such mechanisms (David Webber). Roberts schema posted: http://www.oasis-open.org/archives/ebxml-bp/200403/msg00002.html Update pending for this Work Item. Open Items v3.0: Address late binding of more than timing parameters and influence of context. Keith/Anders/Lars: We need your express feedback on this. @mm1
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]