[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [ebBP] 2/23/2004: [RSD] WI55-Late Binding - v2.0 Options
Discussion|OASIS.ebBP.WI55-Late Binding; Topic|; Point|Differentiating capabilities for v2.0 and 3.0; mm1@ David, For today's call, we have agreed that you could discuss your context proposal. I would encourage everyone to remember the extensive F2F discussions to seek a near-term alternative for v2.0 and address more complex options in v3.0. We do have a note in our white paper draft for v2.0 bounding that indicates we may address a more comprehensive context approach in a later version. So, let's remain constructive in our comments, while also recognizing reasonable boundaries for v2.0. Martin, if you would like to directly comment on this, please respond to this list. Thanks. ||for Martin Roberts mmer@ Martin, I like the simplistic approach you are proposing, as XPath may not be enough and XQuery may be too complicated. Keith, can you sign up to this approach? Lars and Anders, will this meet the current requirements you both have? Proposed: Allowing an extension area for functions that evaluate to the type of the field you are working on. We could then allow the following: timeToPerform="FUNCTION(funcationName) P5D" the P5D is the value that the any processor that does not support functions would use or if the functin return an exception or normal timeToPerform="P5D" As an extra area in the BPSS we would then allow: <Functions> <function language="java" name="jOrderTime" nameID="Func1"> java static function contents </function> <function language="XQuery" name="xOrderTime" nameID="Func2"> XQuery Function </function> </functions> The key to this is that any implementation would be optional for any processor and the binding as to how to reference values in documents and receipts would be implementation dependant and not upto BPSS 2.0 spec to define. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- @mm1
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]