Re: [ebxml-bp] Comments on NameID/IDRef and UID and Late Binding andDocument References

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

>Webber: Dale,
>Your suggestions are exactly what the BPSS context mechanism
>draft proposes too.
>
>Here's a fragment of that XML (from figure 3.2) so you can see
>how you can add linkage between a business rule and a
>time-to-perform / respond item.
>
><ebContext> <!-- namespace declarations and header omitted for clarity -->
>
> <conditions>
>
>  <context condition="doc:orderType='URGENT'"
>
>       <condition name=="bpss:timeToAcknowledgeAcceptance*" value="P10M"
>
>label=="URGENT TIMEOUT" as:member="P5M,P10M,P15M" />
>
> </conditions>
>
><ebContext>
>
>By placing a pointer via a URI from the CPA to this XML context
>instance - we have what we need here.
>
>In the CPA you can review the XML and verify the business
>constriants between you and your partner.  In the BPSS, you can
>reference the CPA to retrieve the context XML and then drive
>the actual binding at runtime using the <context> conditions .
>
>Hope that makes this clearer.
>
>Thanks, DW.
>
>p.s. You had indicated that there is already an appropriate spot
>       in the CPA that we can use to set this BPSScontextURI value,
>       and it would be good if we could get agreement on this with
>       the CPP/A team.
>
mm1: Dave, the CPPA references the BPSS instance used, rather than the 
other way around.