Hi all,
Charlton and I have worked together to come up a new text to clarify
and describe template:createInstance attribute, based on some of
current spec text.
Basically, template:createInstance is introduced in section "13.4.2
prefix" and then describe its detailed usage in "13.4.3. Base Language
subset"
Proposal orginal version:
------------
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
template:createInstance="yes" attribute).
------------
Current spec-text version:
------------
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" attribute for use with opaque
activities, since
the standard "createInstance" attribute defined in the common
abstract
process schema is not allowed on opaque activities.
------------
-------------------------------
In section "13.4.2
Prefix"
template:
For the remainder of section 13.4, the
"template" prefix is by default associated with the template profile
namespace URI.
The Template Profile introduces a new "template:createInstance" extension attribute
to
mark an opaque activity as a start activity. This
"template:createInstance" attribute carries similar semantics to the
"createInstance" attribute of inbound message activities which are
defined in both executable processes, and the common base of abstract
processes. Please refer to Section 13.4.3 below for the detailed usage
of this attribute.
In section "13.4.3.
Base Language subset"
All start activities MUST be defined in a process of this Template
Profile. Start activities in this Template
Profile consist of either an inbound message activity with a
createInstance="yes" attribute, or an opaque activity with a
template:createInstance="yes" attribute. This implies that NO new start activity is
allowed to
be added during executable completion. That is, an inbound message activity
with a
createInstance="yes" attribute is not allowed to be added during
executable completion, except in the case of it being part
of the replacement of opaque start activities.
-------------------------------
Please let us know whether the new text looks good on you.
If we don't hear any further feedback, that will be the text for the related Action Item that I filed a week ago.
Thanks!
Regards,
Alex Yiu
