Issue 6388: Dangling references to "label" attribute (deployment-ftf)
Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
Summary: In the adopted specification, some classes used "label" attributes
for identification purposes to support traceability. Issue 5964
changed these classes to have "name" instead of "label" attributes.
However, some references to the "label" attributes still exist in
the document.


Proposed resolution:


In section 6.4.9.1, remove the paragraph that reads


        A label can optionally be associated with the AssemblyCon-
      nectionDescription. Assembly design tools might use this label
      to visualize the connection.


In section 6.8.3.1, change the fifth sentence of the first paragraph
from


      The MonolithicDeploymentDescription contains a human-readable
      label and references ArtifactDeploymentDescription elements for
      all artifacts that are part of the deployment.


to read


      The MonolithicDeploymentDescription references ArtifactDeploy-
      mentDescription elements for all artifacts that are part of
      the deployment.


In section 6.11.1.1, update the diagram for the PackageError
exception.

Resolution: 
Revised Text: 
Actions taken:
October 21, 2003: received issue
Discussion: 

End of Annotations:=====
ubject: Bug Fix Issues 
Date: Tue, 21 Oct 2003 10:10:59 -0400 
Thread-Topic: Bug Fix Issues 
Thread-Index: AcOX3SdG3qXagVVSRD23TCjkWg95ew== 
From: "Pilhofer, Frank" <fpilhofe@mc.com> 
To: <issues@omg.org> 
Cc: <deployment-ftf@omg.org> 
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h9LE6I2U018836 


Here are some new issues against the Deployment and Configuration
of Component-based Applications specification as amended by the
first vote. Section numbers are from the convenience document
ptc/03-10-01.


4) Dangling references to "label" attribute


In the adopted specification, some classes used "label" attributes
for identification purposes to support traceability. Issue 5964
changed these classes to have "name" instead of "label" attributes.
However, some references to the "label" attributes still exist in
the document.


Proposed resolution:


In section 6.4.9.1, remove the paragraph that reads


        A label can optionally be associated with the AssemblyCon-
      nectionDescription. Assembly design tools might use this label
      to visualize the connection.


In section 6.8.3.1, change the fifth sentence of the first paragraph
from


      The MonolithicDeploymentDescription contains a human-readable
      label and references ArtifactDeploymentDescription elements for
      all artifacts that are part of the deployment.


to read


      The MonolithicDeploymentDescription references ArtifactDeploy-
      mentDescription elements for all artifacts that are part of
      the deployment.


In section 6.11.1.1, update the diagram for the PackageError
exception.