Issue 9116: Sec. 6.16 (bpmn-ftf) Source: National TeleConsultants (Dr. Ugo Corda, ugo.corda@ntc.com) Nature: Uncategorized Issue Severity: Minor Summary: Sec. 6.16 states that "The Type attribute of the Property will map to the type attribute of the part". This seems to imply that WSDL parts are always defined with a type attribute, which is not the case (i.e. they can also be defined with an element attribute instead of a type attribute). Resolution: Revised Text: Actions taken: October 25, 2005: received issue July 26, 2006: moved to bpmn-ftf Discussion: Discussion: While the Issue is valid, it represents a part of a larger issue reviewing and repairing a lot BPEL mapping issues. Thus, this Issue will be deferred and handled by a later version of BPMN. The work could be done as part of the BPDM RFP or as part of a new RFP or RTF. Disposition: Deferred End of Annotations:===== ec. 6.16 states that "The Type attribute of the Property will map to the type attribute of the part". This seems to imply that WSDL parts are always defined with a type attribute, which is not the case (i.e. they can also be defined with an element attribute instead of a type attribute). Date: Fri, 24 Feb 2006 12:47:01 -0800 From: Monica J Martin Subject: bpmn ftf 2/23/2006: Comment on Resolution of Issues 9115 and 9116 To: bpmn-ftf@omg.org X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Although I can understand the reasoning behind the resolutions to issues 9115 and 9116, I do have a concern. An errored mapping may only create confusion. I'd opt to only show the mapping where it is accurate (albeit incomplete) and identify it as such rather than leaving the errors. This is my suggested option. Otherwise, we confuse the user community (and a trivial warning fails to rectify that). Thanks.