I actually had intended to include Frank's suggestion and had forgotten.
Thank you for reminding me, I have included it.
I also think that the schema you describe would be very unfortunate as
it would require extension activities to have an arbitrarily different
syntax than we use for other activities. I believe it is in the
interests of the community that with the exception of the wrapper
element an extension activity look the same as any other activity.
Yaron
Chris Keller wrote:
> Hi Yaron,
>
> I like Frank Leymann's suggestion of changing the MAY to MUST in "MAY have
> BPEL's standard...". Couldn't we enforce that with a schema definition like
> the following?
>
> <element name="extensibleActivity" type="bpws:tExtensibleActivity"/>
>
> <complexType name="tExtensibleActivity">
> <complexContent>
> <extension base="bpws:tActivity"/>
> </complexContent>
> </complexType>
>
>
> And then based on the 92.* rules you can either process the contents of the
> extensible activity or you can't.
>
> - Chris
>
> -----Original Message-----
> From: Yaron Y. Goland [mailto:]
> Sent: Wednesday, May 25, 2005 3:27 PM
> To: wsbpeltc
> Subject: [wsbpel] Issue - 111 - Proposal For Vote
>
> I re-raise my original proposal -
> http://lists.oasis-open.org/archives/wsbpel/200503/msg00188.html
>
> Yaron
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
>
>
