CORBA34 — 69.3 Software Package Descriptor

69.3.2.1 The softpkg Root Element, page 69-473
Softpkg Element Cardinality. Why does it make sense to have an empty
softpkg
file or to allow multiple elements such as title, pkgtype, description,
license, or to
have no implementations? Suggested changes are to place the correct
cardinality
on the softpkg elements to be similar to the CORBA Component and Component
Assembly Descriptor definitions. The suggested elements cardinality changes
will
make parsing the XML much simpler and reduce code footprint, and the XML
more understandable.

Current Format

<!ELEMENT softpkg
( title

Suggested New Format for Softpkg

• Zero or one title ? for example, a book only has one title, not
  multiple titles.
• One or more authors ? for example, a book can have multiple authors,
  but at
  least one.
• Zero or one description, the CAD and CORBA Components DTDs define the
  description this way.
• Zero or one package type.
• Zero or one property file reference. Why are multiple property files
  needed?
• One or more implementations, since the softpkg is an implementation
  for a
  component definition then it must have at least one implementation.
• Zero or more dependencies for all implementations.
• Zero or more descriptors for all implementations. An implementation
  may
  contain multiple different components.
• Zero or more IDL files for all implementations.
• Zero or more extensions.

<!ELEMENT softpkg
( title?
, author+
, description?
, propertyfile?
, license?
, pkgtype?
, implementation+
, ( idl

Deferred

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