Issue 19196: Invalid use of MAY NOT keyword (bpmn2-rtf)
Source:  (, )
Nature: Clarification
Severity: Significant
Summary: In several occasions, the BPMN 2.0.1 specification uses the keywords "MAY NOT". This keywords, however, are not valid according to RFC 2119.

Probably "MUST NOT" would be correct. (Please note: the opposite of "MAY" is not "MAY NOT"!)
Resolution: 
Revised Text: 
Actions taken:
January 28, 2014: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 28 Jan 2014 11:11:13 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Frank Munkert
Employer:        
mailFrom:        fmu@omninet.de
Terms_Agreement: I agree
Specification:   Business Process Model and Notation (BPMN)
Section:         several
FormalNumber:    formal/2013-09-03
Version:         2.0.1
Doc_Year:        2013
Doc_Month:       September
Doc_Day:         01
Page:            several
Title:           Invalid use of MAY NOT keyword
Nature:          Clarification
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue
Remote Name:     host-80-81-15-144.static.customer.m-online.net
Remote User:     
HTTP User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0; MDDRJS)
Time:            11:11 AM


Description:


In several occasions, the BPMN 2.0.1 specification uses the keywords "MAY NOT". This keywords, however, are not valid according to RFC 2119.

Probably "MUST NOT" would be correct. (Please note: the opposite of "MAY" is not "MAY NOT"!)