Hi Diane,
Thanks. I missed that one (having been in
transit at the time).
I see Francisco’s point about having
some more verbiage regarding template:createInstance, but it is awkward to
place it in paragraph 3 of 13.4.3.
It is more appropriate to leave 13.4.3 as
follows:
“All start activities MUST be
defined in a process of this Template Profile. This implies that NO new start
activity is allowed to be added during executable completion (that is, a
message inbound activity annotated with a createInstance=”yes”
attribute).”
And to add the following to 13.4.2:
“The template:createInstance
attribute in the Template Profile is provided for use with opaque activities.”
Best,
-Charlton.
--
Adobe Systems Incorporated
+1 (408) 536-4496 p
From: Diane Jordan
[mailto:]
Sent: Monday, 13 March 2006 14:41
To: Charlton Barreto
Cc: Charlton Barreto;
Subject: Re: [wsbpel-spec-edit]
RE: Issue 82.1 - Resolution
Charlton,
See
this email for an explanation of the editing - http://www.oasis-open.org/apps/org/workgroup/wsbpel-spec-edit/email/archives/200602/msg00045.html
The
subject was misleading so you may have missed it. There were no replies
to it that I've seen or objections on the calls, but if that doesn't mean we
can't still fix it if need be.
Regards, Diane
IBM Emerging Internet Software Standards
(919)254-7221 or 8-444-7221, Mobile:
919-624-5123, Fax 845-491-5709
"Charlton Barreto"
<>
03/13/2006 05:15 PM
To
<>
cc
<>
Subject
[wsbpel-spec-edit] RE: Issue 82.1 -
Resolution
Reviewing the latest spec in CVS, I saw that the
changes for Issue 82.1 were for the most part incorporated. However, there was
one place where I had a question:
Section 13.4.3, paragraph 3 reads:
“All start activities MUST be defined in a process of
this Template Profile. This implies that NO new start activity (that is a
message inbound activity annotated with a createInstance=”yes”
attribute) is allowed to be added during executable completion. The Template
Profile introduces a new “template”createInstance” attributed
for use with opaque activities, since the standard “createInstance”
attribute defined in the common abstract process schema is not allowed on
opaque activities.”
Why was the second sentence (“The Template Profile
introduces….”) added? It is redundant since we’ve already
covered this concept earlier in Section 13.4.
The paragraph should read (conforming to our accepted
resolution of Issue 82.1):
“All start activities MUST be defined in a process of
this Template Profile. This implies that NO new start activity is allowed to be
added during executable completion (that is, a message inbound activity
annotated with a createInstance=”yes” attribute).
Best,
-Charlton.
--
Adobe Systems Incorporated
+1 (408) 536-4496 p
From: Charlton Barreto
Sent: Wednesday, 15 February 2006 14:54
To: ''
Subject: Issue 82.1 - Resolution
Attached
is a zip archive (change the extension to .zip to expand) of the spec text,
based on a clean snapshot of the latest draft, containing my approved
resolution for Issue 82.1 with Rania’s amendment.
Please
let me know if you have any questions.
-Charlton.
--
Charlton
Barreto
Sr .Computer Scientist
Adobe Systems Incorporated
345 Park Avenue, MS E15
San Jose, CA
95110-2704 USA
408.536.4496 p
415.692.5396 v
smime.p7s
