Issue 6046: typo page 131 (deployment-ftf) Source: THALES (Mr. Olivier Hachet, olivier.hachet(at)thalesgroup.com) Nature: Uncategorized Issue Severity: Summary: 10) typo page 131: the 'reason' fields of the exceptions are all written 'reaon'. Resolution: Revised Text: Actions taken: August 1, 2003: received issue Discussion: End of Annotations:===== From: olivier.hachet2@fr.thalesgroup.com To: deployment-ftf@omg.org Subject: Some issues Date: Thu, 31 Jul 2003 17:44:44 +0200 X-Mailer: Internet Mail Service (5.5.2653.19) X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h6VFbFkM003494 Hi, I have found some issues listed below concerning the document ptc/2003-07-08. For some of them, I am not sure but I prefer submit them even if it's a lack of understanding : 10) typo page 131: the 'reason' fields of the exceptions are all written 'reaon'. Subject: Proposed resolutions for issues 6037, 6038, 6041, 6042, 6044, 6046 Date: Mon, 11 Aug 2003 16:40:31 -0400 Thread-Topic: Proposed resolutions for issues 6037, 6038, 6041, 6042, 6044, 6046 Thread-Index: AcNgSM5bx4pu7dN+Rd6P78kuJ0ia5g== From: "Pilhofer, Frank" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h7BKeEkG026196 Here are some proposed resolutions for Olivier's editorial issues. Issue 6037: ----------- page 16 : in the Table 1 (D& C Model Segmentation Summary), the crossing between "Execution Model" and "Management Model" should be "Execution Management Model" instead of "Target Execution Model" Proposed resolution: In section 6.2.3, in table 1, row 4, column 2, change the first line from "Target Execution Model" to "Execution Management Model". Issue 6038: ----------- page 65 : according to the UML diagram, the targetManager association described in the ApplicationManager class should only be described in the DomainApplicationManager class. Proposed resolution: In section 6.9.4.3 (associations for class ApplicationManager), remove the "targetManager" association. Issue 6041: ----------- typo page 98: "A ComponentImplementation is an abstract class that contains the defines the attributes and association..." Proposed resolution: In section 8.2.4.1 (Description of ComponentImplementation stereotype), change the second sentence of the first paragraph from A ComponentImplementation is an abstract class that contains the defines the attributes and associations that are common to the different types of component implementations (Mono- lithicImplementation and ComponentAssembly). to A ComponentImplementation is an abstract class that contains the attributes and associations that are common to the different types of component implementations (Monolithic- Implementation and ComponentAssembly). Issue 6042: ----------- typo page 89: The attribute of the ComponentImplementation class is written capacityt Proposed resolution: In section 8.2.4.2 (Attributes of ComponentImplementation stereotype), change the name of the first attribute from "capacityt" to "capacity". Issue 6044: ----------- 8) typo page 127: "Regular associations in the UML models (not aggreagations) ..." Proposed resolution: No action taken, superceded by issue 5959, which removes the text in question. Issue 6046: ----------- 10) typo page 131: the 'reason' fields of the exceptions are all written 'reaon'. Proposed resolution: In section A.3, in the IDL for exceptions PlanError, StartError, StopError, InvalidProperty and InvalidConnection, rename the "reaon" attribute to "reason".