Issues for UML 1.4 Revision Task Force discussion list

To comment on any of these issues, send email to uml-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 790: UML Documentation-Typos (01)
Issue 791: UML Documentation--Typos (02)
Issue 792: UML Documentation--Typos (03)
Issue 793: UML Documentation--Typos (04)
Issue 794: UML Documentation--Typos (05)
Issue 795: UML Documentation--Typos (06)
Issue 796: UML Documentation--Typos (07)
Issue 815: Error on association owners
Issue 818: page 60 - CallConcurrencyKind
Issue 819: page 60 - EventOriginKind
Issue 820: Page 60 - PseudostateKind
Issue 821: Page 60 - visibilityKind
Issue 822: Page 60 - GraphicMarker
Issue 823: Page 60 - MultiplicityRange
Issue 824: Page 35/37 - AssociationRole
Issue 825: Page 81: message has no parent class
Issue 826: Page 98: ActionSequence has no parent class
Issue 827: Page 121 - Partition has no parent class
Issue 828: Page 16- The association from parameter to classifier has a 1-1 cardinalit
Issue 829: Page 39 - ModelElement/Dependency associations
Issue 830: Page 54 - ConstrainedStereotype
Issue 831: Page 40, table 2: Core - Standard Elements
Issue 832: Page 40 table 2:Constraints Model
Issue 833: page 40 table2: Classifier model element
Issue 834: Page 40 table2: Generalization model element
Issue 836: Page 50 table 3: Auxiliary Elements-Standard Elements (Component model ele
Issue 837: Page 50 table 3: Dependency model element
Issue 838: Page 50 table 3: Dependency Model elements (02)
Issue 839: Page 50 table 3: Component model element
Issue 840: Page 137 table 6: Model management - Standard Elements
Issue 841: Page 9 figure 2: foundation packages
Issue 842: Page 60 figure 10: Data types
Issue 843: Page 61: CallConcurrencyKind and EventOriginKind not defined
Issue 844: Page 61 "EnumerationLiteral"--editorial
Issue 845: Page 62 "PseudostateKind"--editorial
Issue 846: Page 62---editorial
Issue 847: Page 16 of UML Semantics, figure 5
Issue 848: Page 43 UML 1.1 Semantics, figure 7 --editorial
Issue 849: Page 43 of UML Semantics, figure 7
Issue 850: Page 44 UML 1.1 Semantics, figure 8
Issue 851: Page 46 of UML 1.1 Semantics, description of associations for ModelElement
Issue 852: Page 47 of UML 1.1 Semantics, description of Refinement
Issue 853: Page 47 of UML 1.1 Semantics, description of ViewElement
Issue 854: Page 98 of UML 1.1 Semantics, figure 17 (01)
Issue 855: Page 98 of UML 1.1 Semantics, figure 17 (02)
Issue 856: Page 98 of UML 1.1 Semantics, figure 17 (03)
Issue 857: Page 98 of UML 1.1 Semantics, figure 17 (04)
Issue 858: Page 98 of UML 1.1 Semantics, figure 18
Issue 859: Page 98 of UML 1.1 Semantics, figure 18 (02)
Issue 860: Page 10 UML 1.1 Semantics, duplicate entries listed
Issue 861: Page 102 of UML 1.1, StateVertex class misses description
Issue 862: UML 1.1 Semantics: Partition (pp.121 123)
Issue 864: UML 1.1 bug
Issue 866: Package dependencies (01)
Issue 867: Package dependencies (02)
Issue 868: Package dependencies (03)
Issue 869: Package dependencies (05)
Issue 871: Package dependencies (06)
Issue 872: Package dependencies (07)
Issue 873: Package dependencies (08)
Issue 874: Package dependencies (09)
Issue 875: ElementOwnership subclass of ModelElement?
Issue 876: ModelElement Associations (01)
Issue 879: ModelElement Associations (02)
Issue 880: Missing role descriptions
Issue 881: Page 44 UML 1.1 Semantics, figure 8: no component role name
Issue 882: Page 44 UML 1.1 Semantics, figure 8: no base class for ViewElement
Issue 883: Page 53 UML semantics: base class of TaggedValue not shown
Issue 922: Section 5.16.1--editorial
Issue 923: Second para, Section 5.16.1: conflict with statement on p 141
Issue 924: Figure 5 Semantics document (p. 16)
Issue 925: Well-formedness rule [4] for Association
Issue 926: Well-formedness rulw [2] for Class (Semantics, p. 27-28)
Issue 927: well-formedness rules for BehavioralFeature
Issue 928: ActivityState in Figure 22
Issue 929: No notation defined in the Notation Guide
Issue 930: diagram fragment at start of Model section on page 136
Issue 931: Figure 8 (Semantics, p. 44)
Issue 936: Predefined LinkEnd constraints shown as stereotypes in Notation Guide
Issue 937: Predefined LinkEnd constraints issue
Issue 938: Parameters/Attributes need Specification Classifiers
Issue 950: Inconsistency of UML metamodel
Issue 951: UML potential inconsistency about stereotypes
Issue 952: UML stereotypes
Issue 953: UML Notation Guide, association ends
Issue 954: UML Notation Guide, boolean properties
Issue 955: Association between Method and Operation
Issue 973: Inconsistency of UML metamodel
Issue 974: Node class issue (01)
Issue 975: Node class shown as subclass of classifier
Issue 976: Description of component shown as subclass of class
Issue 977: Comment class shown as subclass of ModelElement class
Issue 978: Description of ViewElement indicates that it is subclass of Element
Issue 979: Action class is no abstract class as indicated
Issue 980: Request class is not an abstract class as indicated
Issue 981: Behavioral Features called context
Issue 982: Figure 12 shows no attributes for exceptions
Issue 983: Reception class has wrong attribute
Issue 984: ActionSequence class issue
Issue 985: Description of ActionSequence indicates that it is composition of Actions
Issue 986: Collaborations package--editorial
Issue 987: Collaboration package: constrainingElement aggregation misdrawn
Issue 988: Figure 15, AssociationRole class issue
Issue 989: Signal label in figure 18 is not present
Issue 990: CallEvent: operation label in figure 18 is not present
Issue 1000: UML 1.0: Collaborations not well defined
Issue 1001: UML 1.o: Qualified things in Collaborations
Issue 1002: UML 1.0: Collaborations and Association (role)
Issue 1003: UML 1.0: No notation for ClassifierRole.availableFeature
Issue 1004: UML 1.0: Attachment of messages in Collaboration Diagrams
Issue 1005: UML 1.0: No notation for ModelElement.implementation etc.
Issue 1006: UML 1.0: Node/Component Instances not defined
Issue 1007: UML 1.0: Inconsistent mapping of interface circles
Issue 1008: UML 1.0: Tagged value "location"
Issue 1009: UML 1.0: Inconsistent arrow heads for dependencies
Issue 1010: UML 1.0: instances
Issue 1011: Inconsistent name space rules
Issue 1012: Inconsistent name for stereotype implementationClass
Issue 1013: UML 1.0: Stereotype "uses" applied to more than one class
Issue 1014: UML 1.0: multiplicity "unspecified" not possible
Issue 1015: UML 1.0: Inconsistent name of stereotype "import"
Issue 1016: UML 1.0: Template example cannot be representaed in model
Issue 1017: UML 1.0: "role" should be "end"
Issue 1018: UML 1.0: Unknown model element "Qualifier"
Issue 1019: Attachment of message in Sequence Diagram
Issue 1020: Inconsistent mapping of labels in Sequence Diagram
Issue 1021: More arrow types than message kinds
Issue 1022: Inconsistent format of signal/event
Issue 1023: Inconsistent definition of state machine attachment
Issue 1024: Inconsistent attachment of Activity Diagram
Issue 1025: Extension points of operations not defined
Issue 1026: Feature.owner must be optional
Issue 1027: Method visibility
Issue 1028: Wrong aggregation kind for templates
Issue 1029: Inconsistent definition of stereotype "thread"
Issue 1030: Inconsistent definition of stereotype "friend"
Issue 1031: ordered missing for Constraint.constrainedStereotype
Issue 1032: Enumeration OperationDirectionKind obsolete
Issue 1033: Misleading name Link.linkRole
Issue 1034: English contradicts OCL in rule for CompositeState
Issue 1035: Stereotypes applied to more than one ModelElement
Issue 1036: Inconsistent definition of enumeration
Issue 1037: Inconsistent definition of stereotype " process"
Issue 1038: Inconsistent definition of stereotype "thread"
Issue 1039: Well-formedness rules missing
Issue 1040: Well-formedness rules only expressed in English
Issue 1041: Missing mapping for directed constraint
Issue 1042: Confusing text
Issue 1043: Missing notation for templates
Issue 1044: Inconsistent constraint for discriminator
Issue 1045: Interface specifier not mapped
Issue 1046: Property "derived" not defined
Issue 1047: No mapping for swimlanes in Sequence Diagram
Issue 1048: No mapping for send/receive time in Sequence Diagram
Issue 1049: No mapping for "transition string"
Issue 1050: No mapping for TimingMark in Sequence Diagram
Issue 1051: No notation for ActivityState
Issue 1052: Inconsistent definition of extends relationship
Issue 1053: Deep History Vertex
Issue 1057: deferredEvent mentioned twice in Abstract Syntax
Issue 1058: internalTransition
Issue 1059: ActionState implicit deferring of events
Issue 1060: Editorial error in Semantics
Issue 1061: Missing sentence
Issue 1062: Procedure undefined
Issue 1063: Missing word - editorial
Issue 1097: Contents of section "Control Icons" is vague
Issue 1098: UML 1.1 Semantics, section 8.2, page 66
Issue 1099: Editorial issue: OCL spec 1.1, section 6.3, example 2, last row
Issue 1100: Difference between methods, attributes and operations not clear
Issue 1101: Definition of select and reject operations for Set"s is erranious
Issue 1102: OCL specification 1.1, section 7.2.2
Issue 1103: OCL specification 1.1, p. 10, 5.4.3, example 3
Issue 1104: OCL specification 1.1, p. 32
Issue 1105: OCL specification 1.1, p. 30, 7.2.4
Issue 1107: OCL specification 1.1, p. 24, 7.1.7
Issue 1108: OCL specification 1.1, p. 15, 5.14, second last paragraph
Issue 1109: OCL specification 1.1, p. 14, 5.13, example
Issue 1110: OCL Specification 1.1, section 8
Issue 1165: UML Semantics 1.1, p26, Operation::isPolymorphic
Issue 1171: Signature conflicts not well defined
Issue 1172: Features and ownedElements (1)
Issue 1174: "feature" defined twice
Issue 1176: Features and ownedElements (2)
Issue 1177: Signature conflicts not well defined (02)
Issue 1178: Package importing not well supported
Issue 1180: Return types for BehavioralFeatures
Issue 1181: Use of language-dependant type expressions
Issue 1182: Correspondence between operation and method
Issue 1183: Correspondence between operation and method (02)
Issue 1184: Set of inheritable features not defined
Issue 1185: Exotic uses of generalization
Issue 1186: Signature conflicts across an inheritance hierarchy
Issue 1187: Qualifier badly modeled
Issue 1188: Node and Component parent
Issue 1190: "implementation" association not defined
Issue 1191: Request"s parents
Issue 1192: Signal::isAsynchronous and Signal::direction not defined
Issue 1193: Action::isAsynchronous and Action::script not defined
Issue 1194: CallAction::isAsynchronous and CallAction::mode
Issue 1195: CallAction::request
Issue 1196: Well-formedness Rules for Action::actualArguments
Issue 1197: WFR for instance links
Issue 1198: MessageInstance not used
Issue 1199: Argument::type not defined
Issue 1200: AssociationEnd-AssociationEndRole inconsistencies
Issue 1201: Message::base undefined
Issue 1202: CompositeStates with non-composite subregions allowed
Issue 1203: Entry/Exit actions execution order
Issue 1204: Transition WFR badly written
Issue 1205: Bad example for LCA, main source, main target
Issue 1206: "invoked" not defined
Issue 1207: Package importing transitive
Issue 1208: Dependency wrongly mapped
Issue 1210: The meta-type of template parameters
Issue 1211: WFR for bound elements missing
Issue 1212: Namespace in case of containment
Issue 1214: "derived" not defined
Issue 1215: Notation for iteration in sequence diagram
Issue 1216: "do" action not supported
Issue 1217: Mapping of concurrent subregions
Issue 1218: RaiseAction and TimingMark are not defined
Issue 1219: Control Flow types not modeled
Issue 1220: Threads of control in Collaboration Diagrams
Issue 1221: Syntax for Sequence Expressions inconsistently used
Issue 1222: GeneralizableElement should not inherit from Namespace
Issue 1223: Modeling of realization/specification
Issue 1224: Class WFR (01)
Issue 1226: Inconsistent use of stereotypes, tagged values, and metamodel
Issue 1227: Stereotypes for superclasses do not apply to superclasses
Issue 1228: Stereotype modeled in two ways
Issue 1229: Inconsistency between stereotype tables
Issue 1230: Collaboration showing instances
Issue 1231: Collaboration::constrainingElement semantics
Issue 1232: Modeling of guards
Issue 1233: Multiple transitions from initial states should be allowed
Issue 1234: Semantics of terminate transitions
Issue 1235: UseCaseInstance badly defined
Issue 1236: Notation for state machine inheritance
Issue 1237: Extension/recommendation needed for inner/outer transitions
Issue 1248: UML Semantics, p 81, 145
Issue 1290: Interfaces and support classes
Issue 1309: Collaboration as a Classifier
Issue 1323: Why is Classifier an Aggregate of Features?
Issue 1324: Interface must also have features
Issue 1325: Page 16 lost fact that Class realizes an interface
Issue 1326: Is name space really a *composite aggregation* of model elements?
Issue 1327: Page 16 ---editorial (Element Ownership)
Issue 1328: Why does GeneralizableElement inherit from Namespace?
Issue 1329: How to stop an interface realizing a Data Type ?
Issue 1330: Class to be defined as an intension
Issue 1331: Page 35 -Diagram
Issue 1332: Page 35 Diagram (02)
Issue 1333: Page 38 para 2 line 3, one of its containers is deleted
Issue 1334: Page 40 table 2 Model Element class
Issue 1335: Aggregation of class?
Issue 1336: Page 45 dependency lines 2/3 between model elements not instances?
Issue 1337: Page 47: Dependency is a unidirectional, client-server
Issue 1338: Page 50: "instance" should be changed to "instatiate"
Issue 1339: Page 50: should stereotypes be defined at the subclass level?
Issue 1340: Page 50: table 3 component
Issue 1341: Page 50 Table 3 "refinement"
Issue 1342: Typos on pages 55 and 62
Issue 1343: Discussion on Collaborations and Interactions is confusing
Issue 1344: Page 93: Is Namespace really aggregeation of use cases?
Issue 1345: Page 93: use case
Issue 1346: Uses and extends not types of generalization
Issue 1347: Page 98: Transition is an aggregation of guards
Issue 1348: Page 136: Model package relationship
Issue 1349: Page 143: uses is a stereotyped dependency
Issue 1350: Page 143: "uses" as a stereotype on Generalization
Issue 1351: Typos on page 90, 151 plus errors in page numbering
Issue 1354: Editorials on pages iv, v, 3, and 4
Issue 1355: Page 11: Operation-Call
Issue 1356: Page 13: Packages are GeneralizableElements
Issue 1357: Page 20: Section 4.3.1 could be misleading
Issue 1358: Page 24: add link to Interface
Issue 1360: Page 24 Section 5.4.3 para 1: missing compartments
Issue 1361: Page 26: rename reponsibilities, rules, modification histories etc.
Issue 1362: Page 29: Protected member
Issue 1363: Page 30: Class scope attribute underlined
Issue 1364: Page 35/6 : Stereotypes
Issue 1365: Page 35/6: Use of word type is confusing
Issue 1366: Page 35/6: Why are attributes and association not inherited?
Issue 1367: Typos on pages 24, 40, and 50
Issue 1368: Page 52 figure 20
Issue 1369: Page 57: mathematical issue
Issue 1370: Page 58: Add index entry
Issue 1371: Page 67: Why is discriminator not discussed in terms of power types?
Issue 1372: Page 68 overlapping
Issue 1373: Page 71: Distinction between Dependency and Association
Issue 1374: Page 72: Example needs rejigging
Issue 1375: Page 79: Poor choice of arrowhead
Issue 1376: Page 80: Confusion with headings
Issue 1377: Page 82: Add explanation
Issue 1378: Page 94 --editorial
Issue 1379: Page 98: arrowhead issue
Issue 1389: Aggregation is poorly defined
Issue 1390: "Inheritance" connection used is a generalization relationship
Issue 1391: Responsibilities hardly figure in these documents
Issue 1392: General recommended use of UML
Issue 1393: Permit multiple stereotyping on relationship
Issue 1400: State diagrams: action expressions
Issue 1402: Specification for method in a derived class
Issue 1406: Extension Point
Issue 1506: UML 1.1 issue on Associations
Issue 1507: Merge "Class" and "Interface" into one class
Issue 1508: Clarify how types of attributes and parameters should be instantiated
Issue 1509: Class "Model" is too prescriptive
Issue 1510: The class "Subsystem" inherits from "GeneralizedElement" twice
Issue 1515: Reflexive association in section 5.20.2
Issue 1579: Stereotypes on Dependency, page 43 of V 1.1 (figure 7)
Issue 1634: No discription of the association between Classifier and Parameter is give
Issue 1635: Operation asSequence Issue
Issue 1636: Collection type within OCL missing
Issue 1637: Semantics for dynamic invocation of concurrent activity models are missing
Issue 1651: Changes to figure 15 and description of ClassifierRole on page 82
Issue 1663: Protocol state diagrams issue
Issue 1664: Implicit transitive import between packages
Issue 1678: States of an object not referenceable from OCL expression
Issue 1687: Collection operation size not defined for infinite collections
Issue 1689: Change events issue
Issue 1691: It"s mistake to automatically flatten collections of collections
Issue 1693: pre value of object
Issue 1694: Need way to approximate comparisons
Issue 1695: Need to have relative precedence and, or, xor
Issue 1709: Text in Figure 2.13.7.1 ActivityState seems to be incorrect
Issue 1710: Text on page 2-49 section 2.2
Issue 1781: OCL should allow the use of "let" expressions
Issue 1789: Notion of "conceptual" or "specification-only" not supported
Issue 1815: UML Semantics, section Common behavior
Issue 1886: Rules 3 and 4 for Transitions in state machines should be limited
Issue 1887: ClassifierInState does not satisfy one of its stated usages
Issue 1888: Activities operate by and on objects
Issue 1890: States leading to joins in activity models
Issue 1921: Notation section describing activity states needed
Issue 1939: Existance of classes in classes
Issue 1940: Section 5.17 of Notation Guide: No mapping is given
Issue 1943: Associations as parts of a composite.
Issue 1945: Are subsystems instantiable?
Issue 1951: Abstract class inconsistencies
Issue 1952: Diagram missing attributes
Issue 1953: Issue: inheritance inconsistencies
Issue 1954: missing association names
Issue 1955: Association attributes
Issue 1956: UML Semantics (page 109)
Issue 1966: Figure 2-18 : redundant attributes
Issue 1986: Issue: abstract class inconsistencies
Issue 1987: Issue: Name attribute inheritance
Issue 1988: Issue: Action does not define attributes
Issue 1989: Issue: Inheritance inconsistencies
Issue 1990: Issue: Missing role names
Issue 1991: issue: Missing association names
Issue 1992: MOF does not support association attributes in metamodels.
Issue 1995: Core package-backbone diagram
Issue 1999: UML RTF Issue: Normative MOF-Compatible version of UML
Issue 2001: Not instantiable
Issue 2004: Asynchronous action
Issue 2006: Synchronous request
Issue 2011: ModelElement to Partition multiplicity should be many
Issue 2012: Notation says swimlanes are packages
Issue 2013: Need well defined way to extend OCL
Issue 2014: Add OCL operation to refer to all new instances created during operation
Issue 2015: Common operations should be added to collection types in OCL
Issue 2016: Add "Let"-like construct to OCL
Issue 2017: Set of allInstances should be referrable by the class name
Issue 2018: Infix operator use should be clarified
Issue 2021: Definition of OclAny leads to problems when formalizing OCL
Issue 2022: There are issues that make OCL hard to formalize--document ad/98-10-01
Issue 2024: Generalized change events
Issue 2071: BooleanExpression written in OCL or some other language?
Issue 2073: Widen the naming characteristics
Issue 2074: Some attributes can be expressed in OCL
Issue 2279: Metamodel and semantics for aggregations
Issue 2280: On aggregation. The white diamond name should be "shareable"
Issue 2281: Use of black diamond in the metamodel
Issue 2282: Only single stereotyping is supported
Issue 2283: Interface issue
Issue 2284: Add Responsibilities as a new metatype
Issue 2292: UML Semantics, OMG-UML V1.2 Use Cases July 1998, page 2-99
Issue 2293: action state symbol/state symbol difficult to distinguish when drawn by ha
Issue 2294: Dependencies (and other relationships) with role ends
Issue 2295: UML has symbol for multiobject, not for multi-instances of other classifie
Issue 2298: Package symbol as a polygon
Issue 2305: OCL should allow one constraint to reference another
Issue 2339: Wording od OCL definition
Issue 2510: There is an association between between Constraint and ModelElement
Issue 2544: OCL Standard package
Issue 2546: (Minor) Activity diagram change recommendation
Issue 2566: The second postcondition on Integer::div is incorrect
Issue 2567: The postcondition on set::collect seems to be incorrect
Issue 2568: The postcondition seems to be incorrect for sequence::subSequence
Issue 2569: page 6-10 of OCL documentation for 1.3alphaR5
Issue 2570: pages 6-28 to 6-29 of OCL documentation
Issue 2571: Divide operator is incorrect
Issue 2572: The not-equals operator, "<>", Error in the third postcondition for String::concat on page 6-31
Issue 2573: Error in the third postcondition for String::concat on page 6-31
Issue 2626: Strange GENERAl USE RESTRICTION
Issue 2786: OCL issue
Issue 2837: role concept in UML remains rather vague
Issue 2850: Generalization should be meta-metamodel element
Issue 2921: Use of interfaces in associations
Issue 3098: OCL Error
Issue 3121: Language Name (uml-rtf)
Issue 3122: Precise "Physical" Metamodels Missing from Specification (uml-rtf
Issue 3124: "Physical" Metamodel References (uml-rtf)
Issue 3125: "Physical" Metamodel References in Diagrams (uml-rtf)
Issue 3137: OCL: Consistency in grammar description
Issue 3138: OCL: Are keywords reserved or not
Issue 3139: OCL: Class context specification grammar incomplete
Issue 3140: textual syntax cannot deal with identical class names in different package
Issue 3141: OCL: Feature calls on default target
Issue 3142: OCL: Enumeration types
Issue 3143: OCL: Enumeration types inconsistent with UML metamodel
Issue 3144: OCL: Literal collections
Issue 3145: OCL: Numeric constants missing
Issue 3146: OCL: String literals
Issue 3147: OCL: class operation has no 'self'
Issue 3148: OCL: Let-expressions
Issue 3149: OCL: Samples of invalid typing
Issue 3153: Invalid OCL expression in initial transition
Issue 3201: Why is "FinalState" a separate metaclass ?
Issue 3210: Inheritance of Stereotypes
Issue 3241: Shouldn't the UML Package be allowed to own/reference UML 'Instances'?
Issue 3243: ISSUE FOR UML, SECTION ActivityGraphs
Issue 3244: Issue Activity Package
Issue 3259: State machine name space
Issue 3273: UML RTF 1.4 Issue: Notation for call state
Issue 3274: UML RTF 1.4 Issue: State constraint on host object
Issue 3275: UML RTF 1.4 Issue: Join in collaboration
Issue 3277: UML RTF 1.4 Issue: Deferred event ambiguity
Issue 3278: UML RTF 1.4 Issue: Guard evaluation for choice points.
Issue 3279: UML RTF 1.4 Issue: ownerScope and targetScope
Issue 3280: UML RTF 1.4: Description of context role, between state machine and model
Issue 3281: UML RTF 1.4 Issue: Arrowhead semantics in collaboration unclear
Issue 3282: UML RTF 1.4 Issue: Confusing example of sequence diagram
Issue 3284: UML RTF 1.4 Issue: Flow relationship has the incorrect semantics
Issue 3287: UML RTF 1.4 Issue: Action composition meta-modelled improperly:
Issue 3288: UML RTF 1.4 Issue: What does it mean for ReturnAction to be synchronous?
Issue 3289: UML RTF 1.4 Issue: Create action in collaborations
Issue 3290: UML RTF 1.4 Issue: Duplicate association end names from Constraint.
Issue 3292: Incorrect example of constraining elements in collaborations.
Issue 3293: UML RTF 1.4 Issue: Multi-objects in collaborations
Issue 3294: UML RTF 1.4 Issue: Guard condition in collaborations poorly named.
Issue 3295: UML RTF 1.4 Issue: Messages do not have signatures
Issue 3296: Misleading description of feature inheritance on roles.
Issue 3297: UML RTF 1.4 Issue: Typo in state exit
Issue 3316: Notation for Namespace ownership
Issue 3325: "Unused" data types
Issue 3366: Design patterns and collaboration templates.
Issue 3367: Terminology: Collaboration and Collaboration Template
Issue 3369: Focus is on 2.10 Collaborations
Issue 3370: 2. In 2.10.1, 3rd paragraph, it should be "OOram", not "OOFRam".
Issue 3371: why is AssociationRole is a subtype of Association?
Issue 3372: use of the phrase "In the metamodel..." is unclear
Issue 3373: Confusing wording
Issue 3374: Page 2-114, 2nd paragraph. It should be collaboration template
Issue 3375: In 2.10.5, you give pattern a non-standard definition
Issue 3377: Ad 3.69.3. In these paragraphs, it should be "Classifier" rather than "Cla
Issue 3378: In 2.10.4, semantics of Collaboration, the 1st sentence is confusing
Issue 3383: OCL: Declarators for iterate
Issue 3384: UML 1.4 RTF issue: OCL: Iterator declarators
Issue 3385: UML 1.4 RTF issue: OCL: Precedence of relational operators
Issue 3386: UML 1.4 RTF issue: OCL: Unary operator "-" missing
Issue 3387: UML 1.4 RTF issue: OCL: navigation context in iterate
Issue 3389: UML 1.4 RTF issue: OCL: grammar is ambigous
Issue 3390: Change syntax of certain pre-defined operations
Issue 3393: UML 1.4 RTF Issue: changeability in associations
Issue 3394: UML 1.4 RTF Issue: Multiple languages for uninterpreted strings
Issue 3395: UML 1.4 RTF Issue: Ordering of attribute values
Issue 3396: UML 1.4 RTF Issue: Association generalization has notation but no semantics
Issue 3397: UML RTF 1.4 editorial comments (Part 2 Diagram Elements)
Issue 3398: UML RTF 1.4 editorial comments (Part 3 - Behavioral Elements)
Issue 3399: UML RTF 1.4 editorial comments (Part 6 - Use Case Diagrams)
Issue 3400: UML RTF 1.4 editorial comments (Part 9 - Statechart Diagrams)
Issue 3408: UML 1.4 RTF Issue: Namespace notation too specific
Issue 3530: Page 2-47, well-formedness rule #2 for Classifier
Issue 3531: 2) Page 2-49, additional operation #7 for Classifier
Issue 3558: Who owns an Event?
Issue 3631: Setting Action as abstract in UML-MetaModel MDL to correspond to Semantics
Issue 3637: The index shows incorrect section numbering for sections 2.9.4.1 to 2.9.4