Issue 6234: UML Superstructure: 03-08-02 / Typos (uml2-superstructure-ftf) Source: oose Innovative Informatik eG (Mr. Tim Weilkiens, tim.weilkiens(at)oose.de) Nature: Uncategorized Issue Severity: Summary: Some more typos: p. 191, figure 134 Figure 134 does not show a deployment specification. p. 194, Manifestation "A manifestation is the concrete physical unit of one..." instead of "A manifestation is the concrete physical of one..." p. 200, table 9 The manifestation relationship is shown with a solid line. Notation definition on p. 195 specifies a dashed line. p. 228, Presentation Option, last line "...than the operation name,..." instead of "...than the operaiton name,..." p. 233, CreateObjectAction The definition is not quite clear. The first constraint says "The classifier cannot be abstract". But the description says "The semantics is undefined for creating objects from abstract classifiers." The last one means that abstract classifiers are allowed, but the semantic is undefined. So the constraint is wrong. On the other hand if the constraint is correct, the sentence about the abstract classifier is suerfluous. p. 259, TestIdentifyAction, first line "...are identical objects." instead of "...are identical objects.t" p.286, 3rd paragraph from bottom "An activity with a classifier context..." instead of "An activity with a a classifier context..." p. 304, Semantics, first line "When an activity is invoked,.." instead of "When an activity in invoked,..." p. 355, Examples "The diagram on the left uses a decision diamond; the one on the left uses parameter sets to express the same notion". Text refers twice to the diagram on the left. The figure 279 does not show what the text describes. p. 473, below figure 373 "A choice pseudostate is shown as a diamond-shape symbol as exemplified by Figure 374". Fig. 374 does not show a diamond-shape symbol, but the circle notation. p. 497, Rationale below figure 394 "The rationale for statemachine extension..." instead of "The rationale for statemachie extension..." Resolution: see above Revised Text: Actions taken: September 8, 2003: received issue March 8, 2005: closed issue Discussion: ?? Pg. 191 figure 134: replace figure 134 with the following diagram: :AppServer Order.jar «artifact» Orderdesc.xml «deployment spec» «deploy» ?? Pg. 190 last sentence on the page, replace the incorrect figure reference: “…(as in Figure 132)…” with the correct one: “…(as in Figure 134)..” ?? Pg. 194 replace the definition of Manifestation (1st sentence in sectin 10.3.10) by the following sentence: “A manifestation is the concrete physical rendering of one or more model elements by an artifact.” ?? Table 9 (pages 199 and 200) o The solid lines seem to happen because of the incorrect mapping from Visio graphics to Adobe, since the lines are actually drawn as dashed. The recommendation is to redraw both the Deployment and Manifestation notation entries in this table using FrameMaker graphics. o Also, along the way, fix all the invalid page cross-references in the “References” fields for the Association, Dependency, and Generalization entries in the table ?? Pg. 228, last sentence of the Presentation Options section of CallOperationAction, change the word “operaiton” to “operation”. ?? Pg. 233 Description: remove the sentence: “The semantics is undefined for creating objects from abstract classifiers or from association classes”. ?? Pg. 259, 1st sentence of section 11.3.42: remove the superfluous “t” following the period at the end of this sentence. ?? Pg. 286 3rd paragraph from the bottom, 1st sentence, replace the phrase: “…with a a classifier…” with: “…with a classifier…” ?? Pg. 304 Semantics section of ActivityParameterNode, replace the phrase in the first line: “When an activity in invoked…” with “When an activity is invoked…” ?? Pg. 355 Examples section: o remove the second sentence of the first paragraph of this section: “The diagram on the left uses a decision diamond; the one one the left uses parameter sets to express the same notion” o label the currently unlabeled box at the right of the top diagram in figure 279 “Ship Item”. ?? The item flagged on pg. 473 (below figure 373) is resolved by the solution to issue 6229. ?? Pg. 497 Rationale section of StateMachine first sentence: replace the word “statemachie” by the word “statemachine”. End of Annotations:===== ubject: UML Superstructure: 03-08-02 / Typos Date: Mon, 8 Sep 2003 09:40:51 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: UML Superstructure: 03-08-02 / Typos Thread-Index: AcN13IbMQyB439rXQfasjO9chFZXCg== From: "Tim Weilkiens" To: Cc: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h887e8e4016658 UML Superstructure: 03-08-02 Some more typos: p. 191, figure 134 Figure 134 does not show a deployment specification. p. 194, Manifestation "A manifestation is the concrete physical unit of one..." instead of "A manifestation is the concrete physical of one..." p. 200, table 9 The manifestation relationship is shown with a solid line. Notation definition on p. 195 specifies a dashed line. p. 228, Presentation Option, last line "...than the operation name,..." instead of "...than the operaiton name,..." p. 233, CreateObjectAction The definition is not quite clear. The first constraint says "The classifier cannot be abstract". But the description says "The semantics is undefined for creating objects from abstract classifiers." The last one means that abstract classifiers are allowed, but the semantic is undefined. So the constraint is wrong. On the other hand if the constraint is correct, the sentence about the abstract classifier is suerfluous. p. 259, TestIdentifyAction, first line "...are identical objects." instead of "...are identical objects.t" p.286, 3rd paragraph from bottom "An activity with a classifier context..." instead of "An activity with a a classifier context..." p. 304, Semantics, first line "When an activity is invoked,.." instead of "When an activity in invoked,..." p. 355, Examples "The diagram on the left uses a decision diamond; the one on the left uses parameter sets to express the same notion". Text refers twice to the diagram on the left. The figure 279 does not show what the text describes. p. 473, below figure 373 "A choice pseudostate is shown as a diamond-shape symbol as exemplified by Figure 374". Fig. 374 does not show a diamond-shape symbol, but the circle notation. p. 497, Rationale below figure 394 "The rationale for statemachine extension..." instead of "The rationale for statemachie extension..." Tim Weilkiens Trainer, Consultant, Coach OMG Representative of oose.de GmbH --- E-Mail tim.weilkiens@oose.de Fon ++49 +40 41 42 50 - 25 Fax ++49 +40 41 42 50 - 50 oose.de Dienstleistungen für innovative Informatik GmbH Oberstraße 14b, D-20144 Hamburg Amtsgericht Hamburg HRB 66648 Geschäftsführer Bernd Oestereich OMG Issue No: 6234 Title: UML Superstructure: 03-08-02 / Typos Source: oose.de Dienstleistungen fur innovative Informatik (Mr. Tim Weilkiens, tim.weilkiens@oose.de) Summary: Some more typos: · p. 191, figure 134 Figure 134 does not show a deployment specification. · p. 194, Manifestation "A manifestation is the concrete physical unit of one..." instead of "A manifestation is the concrete physical of one..." · p. 200, table 9 The manifestation relationship is shown with a solid line. Notation definition on p. 195 specifies a dashed line. · p. 228, Presentation Option, last line "...than the operation name,..." instead of "...than the operaiton name,..." · p. 233, CreateObjectAction The definition is not quite clear. The first constraint says "The classifier cannot be abstract". But the description says "The semantics is undefined for creating objects from abstract classifiers." The last one means that abstract classifiers are allowed, but the semantic is undefined. So the constraint is wrong. On the other hand if the constraint is correct, the sentence about the abstract classifier is superfluous. · p. 259, TestIdentifyAction, first line "...are identical objects." instead of "...are identical objects.t" · p.286, 3rd paragraph from bottom "An activity with a classifier context..." instead of "An activity with a a classifier context..." · p. 304, Semantics, first line "When an activity is invoked,.." instead of "When an activity in invoked,..." · p. 355, Examples "The diagram on the left uses a decision diamond; the one on the left uses parameter sets to express the same notion". Text refers twice to the diagram on the left. The figure 279 does not show what the text describes. · p. 473, below figure 373 "A choice pseudostate is shown as a diamond-shape symbol as exemplified by Figure 374". Fig. 374 does not show a diamond-shape symbol, but the circle notation. · p. 497, Rationale below figure 394 "The rationale for statemachine extension..." instead of "The rationale for statemachie extension..." Discussion: · Pg. 191 figure 134: replace figure 134 with the following diagram: · Pg. 190 last sentence on the page, replace the incorrect figure reference: ..(as in Figure 132).. with the correct one: ..(as in Figure 134)... · Pg. 194 replace the definition of Manifestation (1st sentence in sectin 10.3.10) by the following sentence: .A manifestation is the concrete physical rendering of one or more model elements by an artifact.. · Table 9 (pages 199 and 200) o The solid lines seem to happen because of the incorrect mapping from Visio graphics to Adobe, since the lines are actually drawn as dashed. The recommendation is to redraw both the Deployment and Manifestation notation entries in this table using FrameMaker graphics. o Also, along the way, fix all the invalid page cross-references in the .References. fields for the Association, Dependency, and Generalization entries in the table · Pg. 228, last sentence of the Presentation Options section of CallOperationAction, change the word .operaiton. to .operation.. · Pg. 233 Description: remove the sentence: .The semantics is undefined for creating objects from abstract classifiers or from association classes.. · Pg. 259, 1st sentence of section 11.3.42: remove the superfluous .t. following the period at the end of this sentence. · Pg. 286 3rd paragraph from the bottom, 1st sentence, replace the phrase: ..with a a classifier.. with: ..with a classifier.. · Pg. 304 Semantics section of ActivityParameterNode, replace the phrase in the first line: .When an activity in invoked.. with .When an activity is invoked.. · Pg. 355 Examples section: o remove the second sentence of the first paragraph of this section: .The diagram on the left uses a decision diamond; the one one the left uses parameter sets to express the same notion. o label the currently unlabeled box at the right of the top diagram in figure 279 .Ship Item.. · The item flagged on pg. 473 (below figure 373) is resolved by the solution to issue 6229. · Pg. 497 Rationale section of StateMachine first sentence: replace the word .statemachie. by the word .statemachine.. Disposition: Resolved Internet www.oose.de