DDS-XTypes 1.2 RTF Avatar
  1. OMG Issue

DDSXTY12 — TypeObject semantics underspecified and inconsistent

  • Key: DDSXTY12-24
  • Legacy Issue Number: 18300
  • Status: closed  
  • Source: ZettaScale Technology ( Erik Hendriks)
  • Summary:

    Section specifies that a TypeObject can include just a single TypeLibrary while in section it is claimed that a TypeObject can recursively contain other TypeLibraries.

    Of course this is confusing: which is it?

    Also does a typeID need to be globally unique or just in the TypeLibrary in which it is contained?

    Finally, and even more important, since the TypeObject may recursively refer to other (existing) types by their typeID, it is difficult to communicate the meta-data to a node that has no a-priori knowledge about it. The current TypeObject representation is compact, but only able to check whether two existing representations are compatible. It can't be used to drive meta-data based tooling a logger or a service that connects the DDS to a database.

  • Reported: DDS-XTypes 1.1 — Wed, 12 Dec 2012 05:00 GMT
  • Disposition: Resolved — DDS-XTypes 1.2
  • Disposition Summary:

    Added clarification for TypeLibrary

    Added clarification in section that a single TypeLibrary which may recursively contain more TypeLibrary objects

  • Updated: Thu, 22 Jun 2017 16:42 GMT