Issue 19745: message and error ref in tOperation does not define the correct type name (bpmn2-rtf)
Source:  (, )
Nature: Clarification
Severity: Significant
Summary: In Table 8.66, the spec says the inMessageRef and outMessageRef should be type of Message, however, in the xml schema below (table 8.68), the element type of inMessageRef  and outMessageRef is a QName, not Message. similar issue happens on errorRef as well. table 8.66 says errorRef type should be Error, but the schema defines its type to a QName.
Resolution: 
Revised Text: 
Actions taken:
April 17, 2015: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 17 Apr 2015 05:05:31 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Yu Zhang
Employer:        IBM
mailFrom:        zhangyzy@cn.ibm.com
Terms_Agreement: 
Specification:   Business Process Model and Notation
Section:         8.4.4
FormalNumber:    formal/2011-01-04
Version:         2.0
Doc_Year:        2011
Doc_Month:       January
Doc_Day:         04
Page:            106
Title:           message and error ref in tOperation does not define the correct type name
Nature:          Clarification
Severity:        Significant
CODE:            3TMw8
B1:              Report Issue
Remote Name:     201.111.247.60.static.bjtelecom.net
Remote User:     
HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
Time:            05:05 AM


Description:

In Table 8.66, the spec says the inMessageRef and outMessageRef should be type of Message, however, in the xml schema below (table 8.68), the element type of inMessageRef  and outMessageRef is a QName, not Message. similar issue happens on errorRef as well. table 8.66 says errorRef type should be Error, but the schema defines its type to a QName.