Re: [wsbpel] Issue - 107 - Proposal for Vote

[Alex Yiu <alex.yiu@oracle.com>]

Hi Yaron,

You move to the proposal stage of Issue 107 faster than I expect. :-)
I am for the spirit of Issue 107 in general.
However, there may be some technical details which we may still need to 
nail down.

(a)
One detail is about the syntactic issue of QNAME of "bpel:opaque".
(I am thinking out loud below ...)
Some attributes used in BPEL now are QNAME or NCNAME.
In XML Schema or WSDL 2.0, we have special value string as "##any" or 
"#any" for some of their special attribute.
We may want to use "##opaque" or "#opaque" instead (?)

(b)
Other questions are: does <opaque> have a name attribute itself?

(c)
Does it have all standard elements and attributes similar to other 
actvities?
(e.g. <source> <target> suppressJoinFailure attributes

(d)
<opaque> can be used as a place holder for a single activity.
How about some activities container? <onAlarm>,  <case>, <otherwise>?
and different kinds of Handlers?



Sorry for raising questions in this stage. However, I think we need to 
answer some of these questions before the voting.  :-)




Regards,
Alex Yiu



Yaron Y. Goland wrote:

> An activity called 'opaque' shall be introduced for the exclusive
> use of abstract processes. The opaque activity's semantics are that it
> is a place holder for a single activity. The author of an executable 
> complement of an abstract process has sole discretion as to what 
> activity to replace an opaque activity with.
>
> A QNAME bpel:opaque where the bpel namespace shall be the URI
> used by the bpel spec for its own namespace shall be made available for
> use as the value of any BPEL attributes in a BPEL abstract process that
> accept a QNAME. The reserved QNAME's semantics are that it is a place 
> holder for some other QNAME. The author of an executable complement of 
> an abstract process has sole discretion as to what QNAME to replace a 
> reserved QNAME with.
>
>
>
> To unsubscribe from this mailing list (and be removed from the roster 
> of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php. 
>
>