Issue 5523: Device Artifact Dependency (components-ftf)
Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com)
Nature: Uncategorized Issue
Severity: 
Summary: A component's implementation may have additional dependencies on a device's
artifacts (e.g., capacity and/or characteristics) to ensure the right type
of device is
chosen for deployment and/or the device has sufficient capacities for
deployment. To
allow for this capability add a deviceartifactdependency element to the
implementation element.


Current Format


<!ELEMENT implementation
( description
| code
| compiler
| dependency
| descriptor
| extension
| programminglanguage
| humanlanguage
| os
| propertyfile
| processor
| runtime
)* >
<!ATTLIST implementation
id ID #IMPLIED
variation CDATA #IMPLIED >


New Format


<!ELEMENT implementation
( description
| code
| compiler
| dependency
| descriptor
| extension
| programminglanguage
| humanlanguage
| os
| propertyfile
| processor
| runtime
| deviceartifactdependency
)* >
<!ATTLIST implementation
id ID #IMPLIED
variation CDATA #IMPLIED >


<!ELEMENT deviceartifactdependency EMPTY>
<!ATTLIST deviceartifactdependency
     artifactrefid       CDATA     #REQUIRED
artifactvalue       CDATA     #REQUIRED>


Note: This concept is tied to the concept of component artifact property
issue. The
artifactrefid is a reference to a component's artifact property defined in
a
component's property file. The artifactvalue is the dependency value being
requested or needed.

Resolution: 
Revised Text: 
Actions taken:
July 17, 2002: received issue
Discussion: 
Resolution:
None as this is deferred to the final report of the Components 1.1 RTF.
Revised Text:
None as this is deferred to the final report of the Components 1.1 RTF

End of Annotations:=====
From: Gerald_L_Bickle@RAYTHEON.COM 
Subject: CCM Softpkg DTD Extensions & Changes 
To: issues@omg.org, components-rtf@omg.org 
Cc: "Mike McClimens" <mikemc@mitre.org>, "Smith, Jeff"
<jesmith@mc.com>, 
   Edwin.Wrench@ITT.COM, mike.mcclimens@saalt.army.mil, 
   "Mike McClimens" <mikemc@mitre.org>, 
   David Fitkin <dwfitkin@rockwellcollins.com>,
   jeffrey.olynick@baesystems.com 
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001 
Date: Wed, 17 Jul 2002 12:57:08 -0500 
X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 5.0.8
|June 18, 2001) at 07/17/2002 
 12:57:09 PM 
X-MIME-Autoconverted: from quoted-printable to 8bit by emerald.omg.org
id g6HHsWC06347 


Document ptc/2001-11-03, CORBA Component Model


10.  Device Artifact Dependency
A component's implementation may have additional dependencies on a
device's
artifacts (e.g., capacity and/or characteristics) to ensure the right
type
of device is
chosen for deployment and/or the device has sufficient capacities for
deployment. To
allow for this capability add a deviceartifactdependency element to
the
implementation element.


Current Format


<!ELEMENT implementation
( description
| code
| compiler
| dependency
| descriptor
| extension
| programminglanguage
| humanlanguage
| os
| propertyfile
| processor
| runtime
)* >
<!ATTLIST implementation
id ID #IMPLIED
variation CDATA #IMPLIED >


New Format


<!ELEMENT implementation
( description
| code
| compiler
| dependency
| descriptor
| extension
| programminglanguage
| humanlanguage
| os
| propertyfile
| processor
| runtime
| deviceartifactdependency
)* >
<!ATTLIST implementation
id ID #IMPLIED
variation CDATA #IMPLIED >


<!ELEMENT deviceartifactdependency EMPTY>
<!ATTLIST deviceartifactdependency
     artifactrefid       CDATA     #REQUIRED
artifactvalue       CDATA     #REQUIRED>


Note: This concept is tied to the concept of component artifact
property
issue. The
artifactrefid is a reference to a component's artifact property
defined in
a
component's property file. The artifactvalue is the dependency value
being
requested or needed.