[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-bpel] Issue 14: we forgot intents
|
I've made some proposed changes to the spec as part of this resolution.
You can find them here. I ran into a problem with directly reusing the XSD definition of
@requires from the assembly specification. The problem was that our
extension to WS-BPEL is defined as follows: <extensions> <extension
namespace="http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801"
mustUnderstand="yes" /> </extensions> And, unfortunately, WS-BPEL does not allow multiple namespaces to be
associated with a single extension. In the version that I have uploaded, I’ve just created a
sca-bpel:requires attribute and reused SCA’s definition of
sca:listOfQNames. I’ve also added a normative reference to the
policy spec for its exact syntax and semantics. Michael -----Original Message----- I like it. No reason to create a new attribute (it is a global attr
decl in SCA schema). This means WSDL and BPEL would use the same extension attribute with the same semantics. -Anish -- Michael Rowley wrote: > Perhaps we should have a single @sca:requires attribute, which
goes on > partnerLinks, whose contents are the same as the contents of a
service > or reference @requires attribute. The semantic of the
attribute would > be that it is translated directly into a @requires attribute on
the > service or reference that is generated for the partnerLink. > > How does that sound? > > Michael > > -----Original Message----- > From: Anish Karmarkar [mailto:Anish.Karmarkar@oracle.com] > Sent: Thursday, March 27, 2008 12:06 PM > To: OASIS BPEL > Subject: [sca-bpel] Issue 14: we forgot intents > > We resolved issue 14 on today's call, but right after the call
ended I > realized that we did not define an extension for specifying
intends in > the BPEL process. In a previous call we had informally agreed that
> specifying intends in the process made sense. Issue 14 is not just
about > > services and references but about everything that can be specified
in > the process. > > -Anish > -- > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC
that > generates this mail. You may a link to this group and all
your TCs in > OASIS > at: >
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]