issue 111.1: Fixing up extensibility syntax in BPEL by using <annotation> pattern

Hello,

 

I am strongly in favor of an <extension> element as 
suggested by Assaf. It is easier to scan and does not overload the annotation 
meaning. If we make it also repeatable, we can have the standard attributes on 
it, for each feature/extension:

 

<process>

  <extension mustUnderstand="yes" 
xmlns:xxx="http://example"><xxx:timeout>10</xxx:timeout></extension>

  <extension mustUnderstand="no" 
xmlns:xxx="http://example"><xxx:optimizeFor>speed</xxx:optimizeFor></extension>

...

 

Greetings

Bernd

 

From: Alex Yiu [mailto:] 

Sent: Saturday, March 05, 2005 1:13 AM
To: 

Cc: Tony Fletcher; Assaf Arkin; 

Subject: Re: [wsbpel] issue 111.1: Fixing up 
extensibility syntax in BPEL by using <annotation> 
pattern

Hi, all,

(Tony, thanks for adding this 
sub-issue.)

Continue the discussion thread with Assaf ... 

There 
are some minor comestic preference choices: 

[A] Current proposal: 

<annotation> 
<documentation> anything goes 
</documentation>* 
xsd:any* 
</annotation> 

[B] 
Matching XSD Syntax exactly: 
<annotation> 

<documentation> anything goes </documentation>* 
<appinfo 
source="URI"?> xsd:any </appinfo>* 
</annotation> 

[C] Renaming <annotation> to <extension>: (suggested 
by Assaf) 
<extension> 
<documentation> anything goes 
</documentation>* 
xsd:any* 
</extension> 

Personally, I have not-so-strong preference order [A], [C] and [B]. 

Please voice your preference. We would try to vote on this relatively 
easy issue on F2F. 

Thanks!

Regards,
Alex 
Yiu