-
Key: DEPL4-23
-
Legacy Issue Number: 7940
-
Status: closed
-
Source: Zuehlke Engineering ( Frank Pilhofer)
-
Summary:
Sections 6.8.9, 6.8.10 and 6.8.11 describe the ResourceDeployment-
Description, InstanceResourceDeploymentDescription and Connection-
ResourceDeploymentDescription elements, which identify the resources
that were chosen to satisfy a requirement.There are three minor editorial issues here:
(1)
In 6.8.11.2 (ConnectionResourceDeploymentDescription Attributes),
the targetName attribute always identifies an Interconnect or a Bridge,
but never a Node.Proposed resolution:
Update the description for the targetName attribute; change the text
in parentheses from(i.e., the name of a Node, Interconnect or Bridge)
to
(i.e., the name of an Interconnect or Bridge)
(2)
Also in 6.8.11.2 (ConnectionResourceDeploymentDescription Attributes),
the targetName provides a scope for the resource, not for a requirement.Proposed resolution:
Update the description for the targetName attribute; change the
second half of the first sentence (after the comma) from[...], to provide scope for the requirementName.
to
[...], to provide scope for the resourceName.
(3)
Finally, I'd like to clarify in section 6.8.10 (InstanceResource-
DeploymentDescription) that the resourceName is within the scope of
the node that this instance is deployed on.Proposed resolution:
In section 6.8.10.5 (InstanceResourceDeploymentDescription semantics),
add the following text:An InstanceResourceDeploymentDescription is always used in the context
of an InstanceDeploymentDescription, which identifies the node that a
component instance is deployed on. This node provides scope for the
resourceName. -
Reported: DEPL 1.0 — Fri, 19 Nov 2004 05:00 GMT
-
Disposition: Resolved — DEPL 4.0
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT