BPMN2 — Review the use of RFC2119 keywords

Ensure consistent use of RFC-2119 keywords (“MUST,” “MUST NOT,” “REQUIRED,” “SHALL,” “MUST NOT,” “SHOULD,” “SHOULD NOT,” “RECOMMENDED,” “MAY,” and “OPTIONAL”).

Make the following changes in the document (Beta 1, Aug 2009, pdf)
(1) Change all must occurrences to MUST (in sections 2-12 and 14-16, excluding 3.1 and 3.2)
(2) Change all must not occurrences to MUST NOT (in sections 2-12 and 14-16, excluding 3.1 and 3.2)
(3) Change all are NOT/is NOT occurrences to are not/is not (in sections 2-12 and 14-16, excluding 3.1 and 3.2)
(4) Change all required occurrences to REQUIRED (in sections 2-12 and 14-16, except in figure 10.121; do not change occurrences of 'required' and
"required")
(5) Change all shall occurrences to SHALL (in sections 2-12 and 14-16, excluding 3.1 and 3.2)
(6) Change all shall not occurrences to SHALL NOT (in sections 2-12 and 14-16, excluding 3.1 and 3.2)
(7) Change all recommended occurrences to RECOMMENDED (in sections 2-12 and 14-16, excluding 3.1 and 3.2)
(8) In addition make the following changes

• Page 19: Include
  "A Start Event generates a token that MUST be consumed at an End Event (which is implicit if not graphically displayed)."
  instead of
  "A Start Event generates a token that must eventually be consumed at an End Event (which may be implicit if not graphically displayed)."
• Pages 131, 221, 225, 236: Include
  "All Message Flow MUST connect two separate Pools. They MAY connect to the Pool boundary or to Flow Objects within the Pool boundary. They MUST NOT
  connect two objects within the same Pool."
  instead of
  "All Message Flow must connect two separate Pools. They can connect to the Pool boundary or to Flow Objects within the Pool boundary. They cannot connect two
  objects within the same Pool."
• Page 160: Include
  "First, the transaction protocol needs to verify that all the Participants have successfully completed their end of the Transaction."
  instead of
  "First, the transaction protocol must verify that all the Participants have successfully completed their end of the Transaction."
• Page 164: Include
  "The addition of Sequence Flow between the Tasks (e.g., between "Generate Graphics" and "Include Graphics in Text") creates a dependency where the performance
  of the first Task MUST be followed by a
  performance of the second Task. This does not mean that the second Task is be performed immediately, but there MUST be a performance of the second Task after
  the performance of the first Task."
  instead of
  "The addition of Sequence Flow between the Tasks (e.g., between "Generate Graphics" and "Include Graphics in Text") creates a dependency where the performance
  of the first Task must be followed by a performance
  of the second Task. This does not mean that the second Task must be performed immediately, but there must be a performance of the second Task after the
  performance of the first Task."
• Page 197: Include
  "The implementation of the element where the OutputSet is defined determines the OutputSet that will be produced."
  instead of
  "The implementation of the element where the OutputSet is defined must determine the OutputSet that will be produced."
• Page 310: Include
  "However, if there are more than two (2) Participants, then the modeler needs to be careful to sequence the Choreography Activities in such a way that the Participants
  know when they are responsible for initiating the interactions."
  instead of
  "However, if there are more than two (2) Participants, then the modeler must be careful to sequence the Choreography Activities in such a way that the Participants
  know when they are responsible for initiating the nteractions."
• Page 313: Include
  "The data referenced in the conditions need to be visible to two (2) or more Participants in the Choreography"
  instead of
  "The data referenced in the conditions must be visible to two (2) or more Participants in the Choreography"
• Page 328: Include
  "The data used to define the loop conditions need to be visible to all Participants"
  instead of
  "The data used to define the loop conditions must be visible to all Participants"
• Page 328: Include
  "This means that the ordering of Choreography Activities need to take into account when the Participants send or receive..."
  instead of
  "This means that the ordering of Choreography Activities must take into account when the Participants send or receive..."
• Pages 335, 336: Include
  "The data are be visible to the Participants as it was data of a previously sent Message."
  instead of
  "The data must be visible to the Participants as it was data of a previously sent Message."
• Page 2: Include
  "Where permitted or requested connections are specified as conditional"
  instead of
  "Where permitted or required connections are specified as conditional"
• Page 3: Include
  "Some of these attributes are purely representational and are so marked, and some have mandated representations."
  instead of
  "Some of these attributes are purely representational and are so marked, and some have required representations."
• Page 11: Include
  "Section 8 introduces the BPMN Core that includes basic BPMN elements needed..."
  instead of
  "Section 8 introduces the BPMN Core that includes basic BPMN elements required..."
• Page 13: Include
  "... it is likely that business analysts need to understand multiple representations..."
  instead of
  "...it is likely that business analysts are required to understand multiple representations..."
• Pages 15, 124, 126: Include
  "Thus, information needed for execution, such as formal condition expressions are typically not included in a non-executable Process."
  instead of
  "Thus, information required for execution, such as formal condition expressions are typically not included in a non-executable Process."
• Pages 15, 126. Include
  "...the public Process shows to the outside world the Message Flow and the order of those Message Flow that are necessary to interact..."
  instead of
  "...the public Process shows to the outside world the Message Flow and the order of those Message Flow that are required to interact..."
• Page 20: Include
  "There are two (2) standardized Artifacts, but modelers or modeling tools are free to add as many Artifacts as necessary."
  instead of
  "There are two (2) standardized Artifacts, but modelers or modeling tools are free to add as many Artifacts as required."
• Page 51: Include
  "It is the intention of this specification to cover the basic elements necessary for the construction..."
  instead of
  "It is the intention of this specification to cover the basic elements required for the construction"
• Page 53: Include
  "For example, an EventDefinition may be contained in a Process since it may be only required there."
  instead of
  "For example, an EventDefinition would be contained in a Process if it is used only there."
• Page 131: Include
  "The following sections define how Resources can be defined..."
  instead of
  "The following sections define how required Resources can be defined..."
• Page 143: Include
  "In many business workflows, human involvement is required to complete certain..."
  instead of
  "In many business workflows, human involvement is needed to complete certain"
• Page 162: Include
  "The default setting is parallel and the setting of sequential is a restriction on the performance that may be needed due to shared resources."
  instead of
  "The default setting is parallel and the setting of sequential is a restriction on the performance that may be required due to shared resources."
• Page 163: Include
  "Although there is no explicit Process structure,..."
  instead of
  "Although there is no required formal Process structure,"
  -Page 190: Include
  "Activities and Processes often require data in order to execute."
  instead of
  "Activities and Processes often required data in order to execute."
  -Page 296: Include
  "For example, Order Id is necessary for in all Messages of Message Flow in Delivery Negotiation."
  instead of
  "For example, Order Id is required for in all Messages of Message Flow in Delivery Negotiation."
• Page 397: Include
  "In practice, it would entail a special-purpose mediator which not only provides the extraction and data assignment, but also any necessary data transformation."
  instead of
  "In practice, it would entail a special-purpose mediator which not only provides the extraction and data assignment, but also any required data transformation."
• Page 437: Include
  "Second, the activities that need to be duplicated can be removed from the main Process and placed in a derived process that is called (invoked) from all locations in
  the WSBPEL elements as needed."
  instead of
  "Second, the activities that need to be duplicated can be removed from the main Process and placed in a derived process that is called (invoked) from all locations in
  the WSBPEL elements as required."
• Page 438: Include
  "...particularly if a WSBPEL pick is requested."
  instead of
  "...particularly if a WSBPEL pick is required"
• Page 439: Include
  "Such "incomplete" models are ones in which all of the mandatory attributes have not yet been filled in, or the cardinality lowerbound of attributes and associations has
  not been satisfied."
  instead of
  "Such "incomplete" models are ones in which all of the required attributes have not yet been filled in, or the cardinality lowerbound of attributes and associations has not
  been satisfied."
• Page 4: Include
  "• how the feature will be displayed
  • whether the feature will be displayed
  • whether the feature will be supported"
  instead of
  "• how the feature shall be displayed
  • whether the feature shall be displayed
  • whether the feature shall be supported"
• Page 68: Include
  "a Conversation may additionally refer to explicitly updateable Process context data to determine whether or not a Message need to be received"
  instead of
  "a Conversation may additionally refer to explicitly updateable Process context data to determine whether or not a Message shall be received"
• Page 11: Include
  "The following abbreviations are used throughout this document:"
  instead of
  "The following abbreviations may be used throughout this document:"
• Page 14: Include
  "BPMN 2.0 can be mapped to more than one platform dependent"
  instead of
  "BPMN 2.0 may be mapped to more than one platform dependent"
• Page 15: Include
  "Collaborations, which can include Processes and/or Choreographies"
  instead of
  "Collaborations, which may include Processes and/or Choreographies"
• Page 16: Include
  "The Messages associated with the Message Flow can also be shown."
  instead of
  "The Messages associated with the Message Flow may also be shown."
  Disposition: Resolved