Issue 16979: Section: 9.6.2.2 (ddsi-rtps-rtf)
Source: OCI (Mr. Adam Mitz, mitza(at)objectcomputing.com)
Nature: Uncategorized Issue
Severity: 
Summary: Page: 181
Change: This section under-specifies the key fields for all four data types.  The "inherited" DDS structures do not provide a key field that is useful for RTPS because it is vendor-specific.  This section should describe what a "key only" (KeyFlag==1) Data Submessage should contain as its payload for both SPDP and for all 3 types of SEDP.  Table 9.13 indicates that Built-In Topic Keys can be encoded as a GUID, which has no correspondence to the actual definition of Built-In Topic Keys.

Resolution: 
Revised Text: 
Actions taken:
December 27, 2011: received issue
Discussion: 

End of Annotations:=====
s is issue # 16979

Section: 9.6.2.2
Page: 181

Change: This section under-specifies the key fields for all four data types.  The "inherited" DDS structures do not provide a key field that is useful for RTPS because it is vendor-specific.  
This section should describe what a "key only" (KeyFlag==1) Data Submessage should contain as its payload for both SPDP and for all 3 types of SEDP.  
Table 9.13 indicates that Built-In Topic Keys can be encoded as a GUID, which has no correspondence to the actual definition of Built-In Topic Keys.