Source: Real-Time Innovations ( Gerardo Pardo-Castellote)
In DDS-XTYPES 1.3 there was an issue (https://issues.omg.org/browse/DDSXTY13-2) whose resolution added the precise specification of the computation of the memberId. This is now in section 126.96.36.199.1.1 'Member IDs' specifically the three-step algorithm towards the end of the section.
This algorithm fully uses 32 bits. The 4 MSB are set to zero and the remaining 28 bits computed from a hash. Because of this there is no longer a 'reserved range' for memberIds.
However the resolution of
DDSXTY13-2still left some text in section 188.8.131.52.4.4.4 that talks about reserved ranges. This text should also have been removed. In fact it seems that there was an instruction in DDSXTY13-2to remove the paragraph but it either was not applied correctly or it missed a sentence that followed the paragraph. To correct it, the following text should be removed from section 184.108.40.206.4.4.4 'Member IDs'
The remaining part of the member ID range—from 0 to 268,402,687 (0x0FFFBFFF)—is available for use by application-defined types compliant with this specification.
Reported: DDS-XTypes 1.3b1 — Fri, 21 Feb 2020 00:40 GMT
Updated: Fri, 21 Feb 2020 00:40 GMT