BPMN 2 FTF typos
Issue 13: Page 79, Table 8-8 Typo extensionAttributeDefinitions is typed ExtensionDefinition
Reported by dga...@trisotech.com, Jun 08, 2009
On p.79, Table 8-8 the attribute extensionAttributeDefinitions is typed
ExtensionDefinition, it should be typed ExtensionAttributeDefinition.
==========================================================================
Issue 30: Page 141, Table 8-81 Typo in type definition "s" added
callableElements should be of type CallableElement and not CallableElements
==================================================================
Issue 32: Page 283, Figure 10-90 Typo "CancelEventDefinition" should be reploaced by "TerminateEventDefinition"
Reported by hudoneric, Jun 25, 2009
On p. 283 of the specification, we can read CancelEventDefinition element
inherits...
Since a TerminateEventDefinition exists, I assume that this is what should
go there.
=========================================================================
Issue 62 : Page 307, section 10.5.6 Copy/paste Typo "Start Event" should be "Event Gateway"
Comment 1 by dga...@trisotech.com, Jul 10, 2009
In second structural specification Start Event should be replaced by Event
Gateway.
=================================================================
Issue 63: Page 316, section 10.7 Copy/Paste Typo "Pool" should be replaced by "Lane"
In second structural specificatio Pool should be replaced by Lane
=========================================================================
Issue 74: Page 049, Table 7-1, Typo word "is' extra
For the element "Pool" the second sentence of the descriptive text is: "It
is also acts as a “swimlane” and a graphical container for partitioning a
set of Activities from other Pools, usually in the context of B2B
situations."
The word "is" at the beginning of the sentence should be deleted.
=========================================================================
Issue 75: Page 052, Table 7-2, Typo missing "a" before Process
Reported by asir...@trisotech.com, Jul 01, 2009
For element "Activity" the first sentence is: "An Activity is a generic
term for work that company performs (see page 159) in Process."
The word "a" shoud be added before the word "process".
===================================================================
Issue 76: Page 053, Table 7-2, Typo missing "or" in sentence
Reported by asir...@trisotech.com, Jul 01, 2009
For element "Choreography Task", the last sentence of the descption
is:"There are two (2) more Participant Bands and one Task Name Band."
The word "or" shoud be added after the "two (2)".
Comment 1 by dga...@trisotech.com, Jul 06, 2009
For element "Choreography Task", the last sentence of the descption
is:"There are two (2) more Participant Bands and one Task Name Band."
The word "or" shoud be added after the "two (2)".
Summary: Page 053, Table 7-2, Typo missing "or" in sentence
Labels: Validated
Comment 2 by asir...@trisotech.com, Jul 07, 2009
Same apply to last sentence of page 351.
Comment 3 by asir...@trisotech.com, Jul 07, 2009
Also apply to Page 356, Section 12.4.2, last sentence of second paragraph.
====================================================================
Issue 80: Page 087, Typo "a" should be "are"
Reported by asir...@trisotech.com, Jul 01, 2009
In sub-section "Common Artifact Definitions", the sentence reads:"The
following sections provide definitions that a common to all Artifacts."
"That a common" should be replaced by "that are common".
=====================================================================
Issue 82: Page 124, Section 8.3.15, Typo Missing "are" in frist sentence
Reported by asir...@trisotech.com, Jul 01, 2009
The first sentence of Section 8.3.15 is: "A Participant represents a
specific PartnerEntity (e.g., a company) and/or a more general PartnerRole
(e.g., a buyer, seller, or manufacturer) that Participants in a
collaboration."
The word "are" should be added to read " ..... that are Participants in a
collaboration."
=====================================================================
Issue 83: Page 145, Section 9, Typo missing "in"
Reported by asir...@trisotech.com, Jul 02, 2009
Page 145, last paragraph, first sentence reads: "In some applications it
is useful to allow more Messages to be sent between Participants when a
Collaboration is carried out than are contained the Collaboration model."
The word "in" should be added, for the sentence later part to read: " ....
are contained in the Collaboration model."
======================================================================
Issue 84: Page 146, Section 9.1 Typo word "main" should be "may"
Reported by asir...@trisotech.com, Jul 02, 2009
Section 9.1, second paragraph, first sentence reads:"A Pool may be empty,
a “black box,” or main show a Process within."
The word "main" should be replaced by "may".
======================================================================
Issue 87: Page 163, Section 10.2, Typo "An" should replace "A"
Reported by asir...@trisotech.com, Jul 02, 2009
In page 163, the second structural specification (just before section
10.2.1) reads: "A Activity MAY be a source for Message Flow; it can have
zero or more outgoing Message Flow."
The first word of the sentence "A" should be replaced by the word "An".
======================================================================
Issue 88: Page 188, Section "Event Sub-Process", Typo missing "is"
Reported by asir...@trisotech.com, Jul 02, 2009
The frst sentence after the sub-section title "Event Sub-Process"
reads: "An Event Sub-Process is a specialized Sub-Process that used within
a Process (or Sub-Process)."
The word "is" should be added for the sentence to read: "An Event Sub-
Process is a specialized Sub-Process that is used within a Process (or Sub-
Process)."
====================================================================
Issue 89: Page 188, sub-section "Event Sub-Process" Typo
Reported by asir...@trisotech.com, Jul 02, 2009
The last structural specification of page 188 reads: "The use of text,
color, size, and lines for a Sub-Process MUST follow the rules defined in
Section “Use of Text, Color, Size, and Lines in a Diagram” on page 63 with
the exception that:"
The words " a Sub-Process MUST" should be replaced by "an Event Sub-
Process MUST".
====================================================================
Issue 91: Page 231, sub-section "DataInputAssociation", Typo "an" vs "a"
Reported by asir...@trisotech.com, Jul 02, 2009
The first sentence of page 231 reads: "The DataInputAssociation can be
used to associate a item-aware element with a DataInput contained in
an Activity."
The word "a" before "item-aware" should be replaced by the word "an".
===================================================================
Issue 94: Page 308, Section 10.5.6, Typo Replace "follow" by "following"
Reported by asir...@trisotech.com, Jul 02, 2009
The fifth structural specification in page 308, reads: "Only the following
Intermediate Event triggers are valid: Message, Signal, Timer,
Conditional, and Multiple (which can only include the previous triggers).
Thus, the follow Intermediate Event triggers are not valid: Error, Cancel,
Compensation, and Link."
The word "follow" in the second sentence of the specification should be
replaced by "following".
=================================================================
Issue 95: Page 320, Section 10.8, Typo missing word "in"
Reported by asir...@trisotech.com, Jul 02, 2009
Section 10.8, second paragraph, first sentence reads: "In some
applications it is useful to allow more Activities and Events to occur
when a Process is executed or performed than are contained the Process
model."
The word "in" should be added for the end of the sentence to read " ....
than are contained in the Process model."
================================================================
Issue 100: Page 343, Section 12, Typo Two verbs used instead of one
Reported by asir...@trisotech.com, Jul 07, 2009
The sentence above Figure 12-2 reads: "Figure 12-1 shows displays the
metamodel ...".
One of the two verbs, "shows" or "displays" should be deleted.
===============================================================
Issue 109: Page 367, Section 12.4.6, Typo, word "will" to be deleted
Reported by asir...@trisotech.com, Jul 07, 2009
The second sentence of page 367 reads: "The Choreography Task that has two
Messages will is reflected by three Process Tasks."
The word "will" should be deleted.
==============================================================
Issue 112: Page 164, Table 10-5, Typo "s" added to Type
Reported by dga...@trisotech.com, Jul 08, 2009
There is also a typo on p. 164. resourceParameterBindings should be of
type
ResourceParameterBinding and not ResourceParameterBindings.
==============================================================
Issue 121: Page 361 Section 12.4.3 Typo "collpased" instead of "collapsed"
Reported by hudoneric, Jul 27, 2009
On page Page 361 Section 12.4.3 "collpased" should be read "collapsed". The
text is located on the third bullet of the section 12.4.3.
=============================================================
Issue 124: Page 044, Figure 7-4, Page 345 Figure 12-2 and Page 394 Figure 12-50 Typo in the figure
Reported by dga...@trisotech.com, Jul 29, 2009
The last Choreography activity in Figure 7-4, Figure 12-2 and Figure 12-
50 should be labeled "Handle Medecine".
====================================================================
Issue 134: Page 264 Table 10-85 Typo in table caption "cancel Activity" should be "cancelActivity"
Reported by dga...@trisotech.com, Jul 29, 2009
Page 264 Table 10-85 Typo in table caption "cancel Activity" should
be "cancelActivity"
========================================================================
5th bullet on page: add the following to the end of the bullet: "The loopType of the Choreography Task MUST be MultiInstanceParallel."
4th bullet on page: add the following to the end of the bullet: "The loopType of the Choreography Sub-Process MUST be Standard."
Table 8.42, page 72 (102 pdf), replace second column of third row with: "This attribute defines the Conversation Nodes of the parent element (e.g., a
Move Section 8.3.4 to Section 11 after Section 11.7. The Contents of Section 11 will be moved to Section 9 as described below.
The basic rule of Choreography Activity sequencing is this: ?The Initiator of a Choreography Activity MUST have been involved (as Initiator or Receiver) in the previous Choreography Activity.