The DDS specification should be separated into two documents
Legacy Issue Number: 19366
Source: Real-Time Innovations ( Gerardo Pardo-Castellote)
The DDS specification should be separated into two documents one for the DDS-DCPS layer and the other for DDS-DLRL layer.
Splitting the DDS specification into two separate specifications will simplify specification management and align better with the available implementations.
The DDS-DCPS layer does not have any dependencies on the DDS-DLRL layer. Â DDS-DLRL is an optional compliance point built on top of DDS-DCPS.
More than 9 vendors support DDS-DCPS whereas there are only experimental products with limited support that implement DDS-DLRL.
The current situation where there is a single specification creates confusion and complexity. It forces each revision of the specification to handle the issues submitted against bothÂ DDS-DLRL and Â DDS-DLRL. This is very cumbersomeÂ given that different companies support the different specifications and the fact that these companies have different priorities and timelines.
The current situation is hard to sustain and has delayed the RTF work to the extent that RTF 3 closed without a report.
Splitting the specification into two separate ones, one for the DDS-DCPS layer and the other for DDS-DLRL layer would solve these specification maintenance issues.
Reported: DDS 1.2 — Wed, 30 Apr 2014 04:00 GMT
Disposition: Resolved — DDS 1.4
Split the documents per instructions in the revised text section below
Updated: Fri, 6 Mar 2015 20:58 GMT