Issue 5515: 69.3.2.15 The implementation Element, pages 69-478/479 (components-ftf)
Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com)
Nature: Uncategorized Issue
Severity: 
Summary: Implementation Element Cardinality. Why does it make sense to have an empty
implementation or to allow multiple elements such as code, description,
humanlanguage, or to have no code? Suggested changes are to place the
correct
cardinality on the implementation elements. The suggested elements
cardinality
changes will make parsing the XML much simpler and reduce code footprint,
and the
XML more understandable.


Current Format


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


Suggested New Format for implementation
-    Zero or one description, the CAD and CORBA Components DTDs define the
description this way.
-    Zero or one property file reference. Why are multiple property files
needed?
-    One code element is required for a given implementation
-    Zero or one complier element. A given source code element is compiled
by a
specific compiler. Specifying the compiler is optional.
-    Zero or one programminglanguage element.  Specifying the
programminglanguage is optional.
-    Zero or one humanlanguage element.  Specifying the humanlanguage is
optional.
-    Zero or more dependencies for a specific implementation.
-    Zero or more descriptors for a specific implementation. An
implementation
may contain multiple different components.
-    Zero or more runtimes. A given code element may be compatible with
multiple runtime environments.
-    Zero or more os. A given code element may be compatible with multiple
operating systems.
-    Zero or more processors. A given code element may be compatible with
multiple processors.
-    Zero or more extensions.


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

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


2.   69.3.2.15 The implementation Element, pages 69-478/479
Implementation Element Cardinality. Why does it make sense to have an
empty
implementation or to allow multiple elements such as code,
description,
humanlanguage, or to have no code? Suggested changes are to place the
correct
cardinality on the implementation elements. The suggested elements
cardinality
changes will make parsing the XML much simpler and reduce code
footprint,
and the
XML more understandable.


Current Format


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


Suggested New Format for implementation
-    Zero or one description, the CAD and CORBA Components DTDs define
the
description this way.
-    Zero or one property file reference. Why are multiple property
files
needed?
-    One code element is required for a given implementation
-    Zero or one complier element. A given source code element is
compiled
by a
specific compiler. Specifying the compiler is optional.
-    Zero or one programminglanguage element.  Specifying the
programminglanguage is optional.
-    Zero or one humanlanguage element.  Specifying the humanlanguage
is
optional.
-    Zero or more dependencies for a specific implementation.
-    Zero or more descriptors for a specific implementation. An
implementation
may contain multiple different components.
-    Zero or more runtimes. A given code element may be compatible
with
multiple runtime environments.
-    Zero or more os. A given code element may be compatible with
multiple
operating systems.
-    Zero or more processors. A given code element may be compatible
with
multiple processors.
-    Zero or more extensions.


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