Issue 4110: Semantics of firing compound transitions still appears to be circular
Issue 4932: Starting state machine
Issue 4937: Sending a signal after a delay
Issue 5107: Starting a state machine
Issue 5593: Namespace issue (UML 1.4 formal/2002-09-67, 2.5.3.26 Namespace )
Issue 5886: behaviour of the shallow history state and deep history state
Issue 5977: saying {nonunique} on one end of a binary association is meaningless
Issue 6071: Conditional Node and Loop Node notation missing
Issue 6082: Suspension Region
Issue 6083: More examples
Issue 6086: More explanation needed on Figure 339
Issue 6088: Parameterization of lifelines
Issue 6111: Reentrancy 1
Issue 6114: State extension
Issue 6126: Target pin notation
Issue 6137: Promote local conditions to ExecutableNode
Issue 6150: Notation for method
Issue 6200: UML 2 Super/Metamodel/redefinition and substitutability
Issue 6346: Activity OCL
Issue 6353: Deployment a dependency?
Issue 6368: Join nodes that destroy tokens
Issue 6372: Notes versus curly braces
Issue 6395: UML 2 Super / State machines / Transition triggers cannot be redefined
Issue 6405: UML 2 super / Dependencies / improper subsetting?
Issue 6409: UML 2 Super/Interactions/missing OCL constraints
Issue 6422: Section 9.3.3
Issue 6430: UML2 super/ad-03-04-01/Derived attributes and associations
Issue 6433: 03-04-01 Chap 2 p. 112/Components: Different ways to wire components
Issue 6441: Integration between behavioral "sublanguages": Interactions and Activities
Issue 6445: Clarification of use case semantics
Issue 6452: UML 2 Super / Missing OCL constraints
Issue 6455: instantiations of Classifiers
Issue 6460: UML 2 Issue: definition of navigability
Issue 6462: UML 2 Issue: AssociationEnd
Issue 6464: UML 2 Issue: isUnique
Issue 6466: UML 2 Issue: Qualified pathnames
Issue 6470: Section 7.11.2 Association
Issue 6487: Conditions for parameter sets
Issue 6489: Ports in Protocol State Machines
Issue 6495: ptc-03-09-15/Separate classification and generalization in Core::Basic
Issue 6497: ptc-03-09-15/Need for examples to include instance models
Issue 6498: ptc-03-09-15/Explain the new association modeling constructs
Issue 6500: Federated models - UML2 issue
Issue 6616: UML Superstructure FTF : isRoot property disappeared
Issue 6624: freeing namespace
Issue 6637: UML 2 Infra/Metamodel/missing derivation indicators
Issue 6645: UML 2.0 Superstructure Kernal/Packages
Issue 6681: UML2 Super/Kernel Classes
Issue 6700: UML 2.0 Kernel Operations Diagram and Features Diagram and mdl
Issue 6866: Part subtype
Issue 6878: UML 2 Infrastructure / rule for redefinition of Property
Issue 6921: Inheritance of 'Enumerations' is not detailed
Issue 6922: Redefinitions of OCL constraints must be aligned with MOF2.0/UML2.0 class R
Issue 6927: UML 2 Super / Interactions / Ambiguous diagram tags
Issue 6975: missing illustrations of graphical paths for create and destroy messages
Issue 6990: manage simultaneity of events
Issue 6991: transtion
Issue 7051: StateMachine - Constraints
Issue 7161: UML 2 Super/Interactions/Need constraints that cover multiple Lifelines
Issue 7166: show object flow or interactions
Issue 7223: Questions about DataTypes and generalization
Issue 7227: UML2 Super/Deployment/inheritance
Issue 7229: UML2 Super/Deployments/Manifestation
Issue 7246: Figure 78
Issue 7247: Connector - "provided Port" and "required Port" not defined Constraint 1
Issue 7248: Connector - inconsistencies in Constraint [2]
Issue 7249: Connector - inconsistencies in Constraint[3]
Issue 7250: Connector - inconsistencies in Constraint[4]
Issue 7251: Connector - inconsistencies in Constraint[5]
Issue 7254: completion transitions
Issue 7255: Priority of the joint transition
Issue 7303: simple time model" in CommonBehavior
Issue 7304: Notation sections for TimeObservation and DurationObservation
Issue 7329: large overlap between structural features and variables
Issue 7337: inconsistency in the action model
Issue 7338: metaattribute isReadOnly
Issue 7339: Property defines an association "datatype" which is redundant
Issue 7364: section on connectors in the component chapter
Issue 7372: surface notation for state machines
Issue 7375: useless example on p.330, Figure 247
Issue 7392: Interactions model sequences of events
Issue 7398: Provide exception handling for all behaviors.
Issue 7400: AssociationClass
Issue 7406: TimeObservationAction and DurationObservationAction
Issue 7620: Coupling between StateMachines and Activities
Issue 7910: isComposite inconsistency in UML 2.0 and MOF 2.0
Issue 7951: UML 2 Super Basic Interactions
Issue 7952: Alternative entry and exit point notation is ambiguous
Issue 7958: should retain Comment and its associations to Element
Issue 7967: An observed time value must be written into a structural feature
Issue 7969: Section: 9.14.1
Issue 7993: Use case extension inconsistencies
Issue 7994: Presentation Options
Issue 7997: Too much navigability from Generalizations
Issue 8012: Section: Classes, Behavior
Issue 8014: Disjointness should be independent of generalization
Issue 8016: Action for retrieving activity instance
Issue 8020: constrainedElement direction
Issue 8022: Derived union notation
Issue 8023: Association specialization semantics
Issue 8024: End objects of a link In the semantics of AssociationClass
Issue 8026: Contextualized attribute values Figures 121
Issue 8029: underlined association name
Issue 8034: Notation for classifierBehavior
Issue 8042: Terminology Issue
Issue 8071: ClassifierInState not supported in UML2.0 ?
Issue 8077: Properties on Association for end objects
Issue 8087: All sections
Issue 8101: Clarify the differences between redefining element and redefined element.
Issue 8102: Multiple typos in ptc/04-10-02
Issue 8106: Section: 8.3.2
Issue 8111: Section: 9.3.4
Issue 8113: Section: 9.3.6
Issue 8114: Section: 9.3.7
Issue 8118: Section: 8.3.2
Issue 8119: Section: 8.3.2
Issue 8126: Section: 9.3.11
Issue 8142: Section: 10.3.11
Issue 8155: Section: 11.3.11
Issue 8168: Figure 89 on page 158 is incorrect
Issue 8203: Property string {bag} is redundant
Issue 8231: Section: 12.3.14
Issue 8246: namespace
Issue 8249: Section: 12.3.33
Issue 8260: Section: 12.3.40
Issue 8274: UML2/Infra section 11.6.2/ Enumerations should not have attributes
Issue 8278: section 7.3.17 /EnumerationLiteral should not be an InstanceSpecification
Issue 8295: Section: 13.3.2
Issue 8306: Section: 13.3.11
Issue 8310: Section: 13.3.17
Issue 8332: inconsistent description
Issue 8335: ReadStructuralFeatureAction
Issue 8336: RemoveStructuralFeatureValueAction specification
Issue 8342: Section: 14.3.18
Issue 8353: Section: 14
Issue 8385: UML 2 Super / Components / realizingClassifier
Issue 8386: Section: 8.3.4
Issue 8387: Section: 8.3.1
Issue 8414: Section: 14
Issue 8447: Section 15
Issue 8450: Default values for ValueSpecification are not specified properly
Issue 8460: UML 2 Super / Kernel / invalid restriction in isConsistentWith()
Issue 8464: Section: 16.3.1
Issue 8470: Section: Actions
Issue 8471: Decision node
Issue 8472: Section: Activities
Issue 8473: Activities section
Issue 8474: Section: Classes
Issue 8475: Section: Interactions
Issue 8479: Section: Activities - clarification
Issue 8480: Section: Activities : Why is exception type needed?
Issue 8489: ExpansionRegion (behavior in the shorthand notation)
Issue 8492: Section: Activities, LoopNode
Issue 8494: Add constraints on conditional, loop, sequence to rule out node contents
Issue 8495: Add constraints on ConditionalNode
Issue 8498: Constrain conditional node to have body pins if there is a result pin.
Issue 8501: SequenceNode should have way to set output pins in CompleteStructured
Issue 8594: Section: 17
Issue 8601: Section: 18.3.6
Issue 8612: Section: 15.3.8 (second issue)
Issue 8616: Section: D.4
Issue 8668: UML 2 Super / Activities / missing subsets
Issue 8671: Section 12 (02)
Issue 8673: Figure 179 (Control nodes)
Issue 8682: A test cannot be empty
Issue 8684: Add a Constraint
Issue 8686: reword sentence
Issue 8687: rewording isuse?
Issue 8688: UML 2 Different constraints for Property in Super and Infra
Issue 8689: editorial in section 12
Issue 8692: Section: 7.3.36
Issue 8693: Section: 10.3.1
Issue 8695: Key Qualifiers Missing in MOF
Issue 8698: CombinedFragment Loop notation
Issue 8699: UML2-rtf issue: communication diagram
Issue 8700: Meaning of relationship between iteration clause and Lifeline.selector clau
Issue 8702: Section: Actions
Issue 8705: Section: 8.3.1
Issue 8721: Client/supplier on dependencies
Issue 8722: Misleading statement about multiplicity in AssociationClass
Issue 8723: Disjointness should be independent of generalization
Issue 8724: DataStoreNode has uniqueness, reverse constraint inherited from ObjectNode
Issue 8725: Clarify multiple inputs to expansion regions
Issue 8726: Element to Constraint navigation
Issue 8727: The create stereotype on Usage dependency
Issue 8731: Activities
Issue 8738: StructuredActivityNode, Semantics, third paragraph, first sentence,
Issue 8741: In Figure 12, ownedAttribute is bidirectional, in Figure 95, it is unidirec
Issue 8742: represents and occurrence keywords are switched
Issue 8743: Clarify which classifier or operation this is referring to
Issue 8744: CollaborationUse: Constraint 1,
Issue 8747: Notation for connector end multiplicities.
Issue 8748: Operation calls on behavior ports
Issue 8750: External exceptions.
Issue 8756: Section: Classes
Issue 8757: 1. Deployment
Issue 8758: Association in UseCase diagram
Issue 8760: Events in Sequence diagram
Issue 8761: Arguments of Message
Issue 8763: Nested Nodes
Issue 8764: Section: 14.3.3
Issue 8765: Section: 14.3.3 Page: 508+
Issue 8768: Section: Classes
Issue 8771: Section: Action/Activity
Issue 8773: Page: 330
Issue 8774: Notation of Attributes and Associations subsections
Issue 8776: Section: 9.3.7
Issue 8777: Section: 8.3.1
Issue 8778: Section: 8.3.1 Page: 156 ff
Issue 8779: ConditionalNode inputs used by more than one test
Issue 8780: Input tokens to LoopNodes should be destroyed when the loop is done
Issue 8785: Return message
Issue 8786: Arguments of Message
Issue 8787: Numbering
Issue 8788: Variables
Issue 8854: multiplicity should not be used/shown in an communicates association
Issue 8855: Issue 7368 - make Classifier::useCase navigable
Issue 8861: Section: 12.3.2 Action
Issue 8866: Section: Classes
Issue 8876: Page: 369/370
Issue 8877: Page: 129
Issue 8878: Page: 532
Issue 8880: 9.1 BehavioralFeature package
Issue 8882: Section: 10.1 Types Diagram
Issue 8883: UML 2.0 Super/Use Cases/Subject of a Use Case
Issue 8887: Section: 11.3.6 Classifiers diagram
Issue 8888: Section: 11.3.13 TypedElement (as specialized)
Issue 8889: Section: 11.5.1 DataType (as specialized)
Issue 8890: Section: 15.3.12
Issue 8891: Page: 423
Issue 8893: UseCase and Actors
Issue 8895: ObjectNode
Issue 8897: OutputPin
Issue 8898: Syntax of Transition
Issue 8899: reply messages in interactions
Issue 8900: Page: 157,162,163
Issue 8903: page 97, Chapter 10.2.2. MultiplicityElement
Issue 8904: page 134, Chapter 11.4.1
Issue 8920: Page: 62
Issue 8921: Meaning of navigability
Issue 8936: event parameters
Issue 8945: Page: 420
Issue 8946: Section: 9.3.5
Issue 8951: UML 2 Super / Actions / Compliance Levels of Actions
Issue 8952: UML 2 - Invalid subsetting of composition ends
Issue 8964: Interaction::lifeline should be ordered
Issue 8965: Section: 14.3.20
Issue 8966: Core::Constructs::Operation
Issue 8967: UML SuperStructure - Inconsistency re State Machine terms
Issue 8970: Behavior
Issue 8972: Page: 255
Issue 8973: Page: 346-347
Issue 8974: Missing notation for association classes
Issue 8975: UML2 Super / 14.3.13 Interaction
Issue 8977: Property ownership must be consistent across association redefinitions
Issue 8987: Section: 6.5
Issue 9001: Section: Common Behavior
Issue 9002: Section: Common Behavior (02)
Issue 9003: Section: Classes
Issue 9004: Section: Classes (02)
Issue 9005: Section: Common Behavior
Issue 9006: Section: Actions
Issue 9007: Section: Common Behaviors
Issue 9008: Section: Classes
Issue 9009: Section: Activities
Issue 9011: Section: Classes
Issue 9012: Section: Classes
Issue 9013: Section: Activities
Issue 9014: Section: Activities
Issue 9015: Section: Classes
Issue 9017: Section: 16.3.3
Issue 9024: "ownedType" is not a valid element
Issue 9076: Page: 53-55
Issue 9078: Section: Activities
Issue 9081: Section: 14.3.20 Message (from BasicInteractions)
Issue 9101: (merged) compliance level L1
Issue 9102: (merged) compliance levels L2 and L3
Issue 9111: Page: 492-493
Issue 9120: section, 12.3.27 ExpansionRegion(from ExtarStructureActivities
Issue 9124: Need more flexible notation for activity partitions
Issue 9125: keyword, "buildcomponent", and a stereotype, "buildComponent"
Issue 9138: inconsistency wrt UML2 classifier behavior
Issue 9141: Section 8.3.2 sub-section "Notation" starting on page 149
Issue 9142: Section 8 Issue - Component Realization-Classifier multiplicity
Issue 9143: Section: 7.3.36 Operation
Issue 9145: Page: 107
Issue 9146: Section 7.2.1 of ptc/04-10-14
Issue 9172: Section: 15.3.15
Issue 9179: Section: Appendix A: Diagrams
Issue 9225: No notation for associating Exceptions with Operations
Issue 9230: choice of terminolgy for TransitionKind is non-intuitive
Issue 9232: Page: 161
Issue 9233: On page 26, Figure 7.9
Issue 9234: Operation should be a specialization of TypedElement and MultiplicityElemen
Issue 9235: Figure 12.18: Small typo: "subsets ownedMember" not "ownedmember"
Issue 9236: constraints owned by these properties have no context
Issue 9237: Section: Classes
Issue 9241: Operation::ownedParameter should be ordered in XMI?
Issue 9242: /qualifiedName attribute missing on Core::Constructs::NamedElement
Issue 9243: XMI file: Core::Constructs::Operation::bodyCondition should have upper boun
Issue 9244: Unclear relationship between the Basic and Abstractions packages
Issue 9245: Description of Element
Issue 9246: Element and Comment in Basic
Issue 9247: No ReadParameterAction or WriteParameterAction
Issue 9249: 7.3.4 Association Class
Issue 9256: Optional name attribute in NamedElement is misleading and insufficient
Issue 9330: Page: 338, 339
Issue 9337: 7.3.41 Parameter (from Kernel, AssociationClasses)"
Issue 9338: 7.3.41 Parameter (from Kernel, AssociationClasses)"
Issue 9339: consistent ordering of Association::memberEnd and ownedEnd
Issue 9340: Section: 14.4
Issue 9341: reference to Figure 12.87 missing
Issue 9351: UML 2.1/Superstructure/ call triggers vs signal triggers
Issue 9352: UML 2 Superstructure / CommonBehaviors / Incorrect types in text
Issue 9362: Page: 625
Issue 9369: Section: 7.3.9
Issue 9370: Section: Sequence diagrams
Issue 9371: All associations ends in the UML2 metamodel itself should be navigable
Issue 9372: Show an example of correct notation for the metamodel
Issue 9373: Use the new 'dot' notation in examples
Issue 9374: AssociationClass is severely underspecified
Issue 9375: Section: 7.3.7
Issue 9395: Fig 12.10
Issue 9398: UML 2/Templates -- single argument?
Issue 9400: Notation for ordering action input and output pins
Issue 9401: ControlNodes in ActivityPartitions
Issue 9402: Reception has no notation for its signal
Issue 9403: No ObjectEvent corresponding to SendObjectAction
Issue 9406: UML2: No notation for indicating Operation::raisedException
Issue 9407: UML2: No notation for BehavioredClassifier::ownedTrigger
Issue 9413: UML 2 Super / Composite Structure / ambiguous constraint
Issue 9416: Section: 12.3.48
Issue 9445: Link notation for instance diagrams does not cope with multiple classifiers
Issue 9464: UML 2 Super / Components / connectors to interfaces
Issue 9513: UML 2.2 RTF issue - line styles for profiles
Issue 9514: page 467, Section 13.3.24
Issue 9556: Question on InfrastrucutreLibrary::BehavioralFeatures::Parameter
Issue 9576: Section: 13.3.24 Signal (from Communications)
Issue 9577: New Issue on multiple guillemot pairs for same element
Issue 9578: assembly connectors
Issue 9597: Fig 7.14
Issue 9598: ptc/06-01-02:14.3.14, Notation
Issue 9599: New issue on notation for multiple stereotypes
Issue 9605: packagedElement
Issue 9617: Section: 7.3.10
Issue 9619: Section: 9.3.13 - connectors
Issue 9622: the default for a Property should not be inconsistent with its type
Issue 9700: UML's support for null values and semantics is unclear
Issue 9701: Unnecessary restriction on aggregations being binary
Issue 9702: No way of specifying element documentation
Issue 9703: Unclear usage of LiteralExpression::type
Issue 9704: "Property::lowerValue" is not a good name
Issue 9705: ValueSpecification::isComputable()
Issue 9706: Definition of stereotype placement requires a name
Issue 9710: 11.3.26 OpaqueAction
Issue 9718: UML 2/ Super / SendSignalEvent erratum
Issue 9720: Action inputs/outputs
Issue 9750: A notation for Trigger
Issue 9751: UML/OCL spec mismatch-Constraint.context vs Constraint.constrainedElement
Issue 9752: Section: 11.1.3
Issue 9754: Section: 7.3.33
Issue 9760: Section: 9.14.2
Issue 9800: What exactly is a state list?
Issue 9803: Editorial bug in 2.1 Superstructure Convenience document
Issue 9805: Default value types
Issue 9806: General ordering cycles
Issue 9807: Section: 8.3.1
Issue 9808: Completion event modeling
Issue 9812: Page: 64 & 112 Section: 9.2
Issue 9813: Section: 9.2
Issue 9814: Section: 9.3.11
Issue 9817: Section: 7.2
Issue 9818: discrepancies between package dependencies and XMI file for Superstructure
Issue 9819: Section: Appendix F
Issue 9820: Section: Figure 14.5
Issue 9821: Section: 9.3.11
Issue 9822: Section: 7.3.44
Issue 9823: Section: 7
Issue 9824: Section: 15.3.14 Transition
Issue 9825: Notation (p 154, formal/05-07-04 )
Issue 9826: Section 10.2.1 "Class" (in Basic)
Issue 9827: Section 11.4.1 "Classifier" (in Constructs)
Issue 9828: Section 11.4.1 "Classifier" (in Constructs)
Issue 9829: Section: 12.3.8
Issue 9830: Stereotype attributes inherited from Class
Issue 9831: UML 2: "isLeaf"
Issue 9833: text of specs and corresponding XMI specs should be clarified
Issue 9834: Relationships
Issue 9839: Section: 15.3.12
Issue 9840: Section: 15.3.12, p 588, 589
Issue 9841: EnumerationLiteral should constrain InstanceSpecification
Issue 9842: Guidance for Representing Enumeration Values
Issue 9843: Figure 7.4 invalid redefines
Issue 9855: Section: Activities
Issue 9856: Section: Activities - Weight description
Issue 9857: Section: Activities - Weight notation
Issue 9858: Section Activities: Default weight
Issue 9859: ReadLinkAction
Issue 9860: Section: Activities - Pin ordering semantics
Issue 9861: Section: Activities - Preserving order of multiple tokens offered.
Issue 9862: Section: Actions - InputPin semantics wording
Issue 9863: Section: Actions - Output of read actions for no values
Issue 9864: Section: Activities - Semantics of fork node wording
Issue 9865: Section: Activities - Multiple activity parameters nodes for a single inout
Issue 9866: Section: Activities - Offer ordering on joins
Issue 9867: Section: Activities - Join node edge constraint
Issue 9868: Section: Activities - ForkNode semantics wording
Issue 9869: Section: Activities - Output pin semantics clarification
Issue 9870: Actions on non-unique properties with location specified
Issue 9871: Section: Activities - isSingleExecution default
Issue 9872: Section: Activities -StartClassifeirBehaviorAction and classifier behaviors
Issue 9873: Section: Common Behavior - isReentrant should default to true
Issue 9875: Section: Activities - Action semantic clarification
Issue 9877: Notation for stereotypes on Comments and other elements
Issue 9878: PrimitiveTypes access by UML (M1) models
Issue 9881: Bad cross reference for InterfaceRealization Notation
Issue 9885: text-diagram out of synch in Infrastructure 11.4.1
Issue 9886: OCL Syntax in expressions
Issue 9887: Optional values and evaluation of defaults
Issue 9888: Move Property::isId from MOF to UML
Issue 9889: Unclear which Property has aggregation
Issue 9890: Clarify isRequired
Issue 9891: ExtensionEnd description refers to old use of navigability
Issue 9923: Section: 13 & 14 swradio Issue - Common and Data Link Layer Facilities
Issue 9961: navigating from link to link ends
Issue 9962: Subclasses of InstanceSpecification
Issue 9963: No default value specified for Generalization::isSubstitutable
Issue 9999: Association::isDerived should be derived
Issue 10000: Missing inheritance in 9.3.12
Issue 10001: Merged Metam.:Property::class with redefinition of non-inherited property
Issue 10003: Section: 9.12.1
Issue 10004: Section: 9.13
Issue 10005: Section: 9.10.3
Issue 10006: Section: 9.19.1
Issue 10007: Section: 9.16.1
Issue 10044: Profile Structure Diagrams are missing from Annex A
Issue 10045: 11.3.47 on StructuralFeatureAction (and related sections on subclasses)
Issue 10074: Invalid mandatory compositions and associations
Issue 10076: Section: 14.3.20
Issue 10079: Invalid redefinitions introduced into metamodel
Issue 10080: Section: 11.3.5
Issue 10081: Section: 13.2
Issue 10082: Section: 15.3.8
Issue 10083: proper content for Figure 13.8
Issue 10086: Section: Annex C.1
Issue 10087: Figure 7.31
Issue 10140: Section: 7.3.3
Issue 10144: redefined properties
Issue 10145: 12.3.26 ExpansionNode
Issue 10146: 12.3.27 ExpansionRegion
Issue 10147: UML 2 state machines / entry point outgoing transitions
Issue 10151: UML 2: Semantics of isOrdered need to be clarified
Issue 10345: Section: 7
Issue 10347: Section: 17.5
Issue 10351: Section: 12.3.2 Action
Issue 10353: UML2: Parameter::isException overlaps with Operation::raisedException
Issue 10354: issue regarding required and provided interfaces
Issue 10356: Page 60 of the pdf
Issue 10376: uml.xsd schema file in ptc/2006-04-05 is not correctly generated
Issue 10379: Section: 7.3.38
Issue 10382: Meaning of Constraint visibility
Issue 10383: Section: 13.3.25
Issue 10388: Activity shape
Issue 10411: Section: Chapter: 7.3.2.4 View
Issue 10413: Constraint.context vs Constraint.constrainedElement
Issue 10441: UML2: ReadSelfAction with a context cannot access behavior owned attributes
Issue 10469: Figure 13.8 shows the wrong diagram
Issue 10474: Connector contract is inflexible
Issue 10498: Section: 15
Issue 10512: Section: 15
Issue 10513: Section: 13.2
Issue 10515: Section: 7
Issue 10521: AcceptCallAction has not operation
Issue 10526: UML 2 Superstructure/Components/overly stringent constraints
Issue 10529: Section: 14.3.14
Issue 10530: Section: 14.3.10
Issue 10536: A_end_role should not be bidirectional
Issue 10537: A_outgoing_source and A_incoming_target should not be bidirectional
Issue 10590: UML 2.1 Spec, Interactions: 14.3.18 - InteractionUse
Iss