Issue 6025: Scope chapter is empty (deployment-ftf) Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com) Nature: Uncategorized Issue Severity: Summary: Reformatting the submission to match the ISO format created an empty "Scope" chapter. We must fill it with some content. >From the template: "A paragraph or two. The Scope clause shall appear at the beginning of each specification and define, without ambiguity, the subject of the specification and the aspect(s) covered. It indicates the limits of applicability of the specification or particular parts of it. It shall not contain requirements. The scope shall be succinct so that it can be used as a summary for bibliographic purposes. It shall be worded as a series of statements of fact. Forms of expression such as «This specification defines [establishes] [gives guidelines for] [defines terms] [specifies] ...» shall be used. Statements of applicability of the standard shall be introduced by the wording «This specification is applicable to ...»." Resolution: Revised Text: Actions taken: July 28, 2003: received issue Discussion: End of Annotations:===== ubject: Scope chapter is empty Date: Mon, 28 Jul 2003 16:34:55 -0400 Thread-Topic: Scope chapter is empty Thread-Index: AcNVR7R8YXEehFV/RHOcqccS+uSBRQ== From: "Pilhofer, Frank" To: Cc: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h6SKVTkM031015 This is a new issue for the Deployment FTF. Reformatting the submission to match the ISO format created an empty "Scope" chapter. We must fill it with some content. >From the template: "A paragraph or two. The Scope clause shall appear at the beginning of each specification and define, without ambiguity, the subject of the specification and the aspect(s) covered. It indicates the limits of applicability of the specification or particular parts of it. It shall not contain requirements. The scope shall be succinct so that it can be used as a summary for bibliographic purposes. It shall be worded as a series of statements of fact. Forms of expression such as «This specification defines [establishes] [gives guidelines for] [defines terms] [specifies] ...» shall be used. Statements of applicability of the standard shall be introduced by the wording «This specification is applicable to ...»."!:q  Subject: Proposed resolution for issue 6025: scope chapter is empty Date: Thu, 4 Dec 2003 10:02:59 -0500 Thread-Topic: Proposed resolution for issue 6025: scope chapter is empty Thread-Index: AcO6d7UDZdAAagAmSyWQGCrirBGtTw== From: "Pilhofer, Frank" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id hB4F1ONA025924 Here is an initial proposal for the scope section. Please comment. Proposed resolution: In section 2, "Scope", replace the text "[To Do]" with the following: This specification defines metadata and interfaces to facilitate the deployment and configuration of component-based applications into heterogeneous distributed systems. The specification defines: - Metadata to describe component-based applications and their requirements (Component Data Model) and interfaces to store, browse and retrieve such metadata (Component Management Model). - Metadata to describe heterogeneous distributed systems and their capabilities (Target Data Model) and interfaces to collect and retrieve such metadata (Target Management Model). - Metadata to describe a specific deployment of an application into a distributed system (Execution Data Model) and interfaces to execute deployments (Execution Management Model). - A specialization of said metadata and interfaces for the CORBA Components Subject: Updated proposed resolution for issue 6025: scope chapter is empty Date: Wed, 17 Dec 2003 14:59:31 -0500 Thread-Topic: Proposed resolution for issue 6025: scope chapter is empty Thread-Index: AcO6d+cvYahjY0DuQSCbnFUaYX+J6wKX2d7g From: "Pilhofer, Frank" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id hBHJulNA006799 Here is the updated proposed resolution for the scope section that includes today's agreements of changing "distributed systems" to "distributed target systems" and adding a bullet about the processes that we define. However, in the fourth bullet, I changed "[...] and launch of the distributed application" to "[...] and launch of component-based applications", to be consistent with our terminology (since we're talking about component-based applications, not distibuted applications, elsewhere) and multiplicity (plural, since the process works with any component-based application, not just "the" (a specific) application). Proposed resolution: In section 2, "Scope", replace the text "[To Do]" with the following: This specification defines metadata and interfaces to facilitate the deployment and configuration of component-based applications into heterogeneous distributed target systems. The specification defines: - Metadata to describe component-based applications and their requirements (Component Data Model) and interfaces to store, browse and retrieve such metadata (Component Management Model). - Metadata to describe heterogeneous distributed target systems and their capabilities (Target Data Model) and interfaces to collect and retrieve such metadata (Target Management Model). - Metadata to describe a specific deployment of an application into a distributed target system (Execution Data Model) and interfaces to execute deployments (Execution Management Model). - A deployment process which includes installation, configuration, planning, preparation and launch of the distributed application. - A specialization of said metadata and interfaces for the CORBA Components platform.