CORBA34 — 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

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

Deferred

This proposal was generated automatically by request of the Task Force Chair Adam Mitz.