[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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 cbarreto@adobe.com From: Charlton Barreto
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. --
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]