Issue 17896: Redefinition does not allow for overloading (uml25-ftf)
Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org)
Nature: Revision
Severity: Significant
Summary: Feature redefinitions may either be explicitly notated with the use of a {redefines <x>} property string on the Feature or implicitly by having a Feature with the same name as another Feature in one of the owning Classifier’s more general Classifiers. In both cases, the redefined Feature shall conform to the compatibility constraint on the redefinitions. 

By allowing reuse of the name to cause redefinition, you prevent overloading. A class should be allowed to more than one operation with the same name with different argument lists. 

Resolution: 
Revised Text: 
Actions taken:
September 26, 2012: received issue
Discussion: 

End of Annotations:=====
s is issue # 17896

Problem: 9.028

Severity: Major
Type: Problem
Location: 9.4.4 p 119
Title: Redefinition does not allow for overloading.
Current Text
Feature redefinitions may either be explicitly notated with the use of a {redefines <x>} property string on the Feature or implicitly by having a Feature with the same name as another Feature in one of the owning Classifier.s more general Classifiers. In both cases, the redefined Feature shall conform to the compatibility constraint on the redefinitions. 
 
By allowing reuse of the name to cause redefinition, you prevent overloading. A class should be allowed to more than one operation with the same name with different argument lists. 
 
Source: Michael Jesse Chonoles