Issue 10581: Section: 2.2.3 (data-distribution-rtf)
Source:  (, )
Nature: Enhancement
Severity: Minor
Summary: The PSM mapping of BuiltinTopicKey_t is defined to be as; struct BuiltinTopicKey_t { BUILTIN_TOPIC_KEY_TYPE_NATIVE value[3]; }; But the DDS Interoperability Wire Protocol (RTPS) specifies that GUID consists of 12 bytes GuidPrefix and 4 bytes EntityId. In order to map GUID and BuiltinTopicKey, we should define BuiltinTopicKey as the following; struct BuiltinTopicKey_t { BUILTIN_TOPIC_KEY_TYPE_NATIVE value[4]; }; 

Resolution: 
Revised Text: 
Actions taken:
January 9, 2007: received isuse
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 09 Jan 2007 06:03:45 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Ertan Deniz
Company: MilSOFT
mailFrom: ertanden@gmail.com
Notification: Yes
Specification: Data Distribution Service for Real-time Systems
Section: 2.2.3
FormalNumber: ptc/06-04-09
Version: 1.2
RevisionDate: 04/09/06
Page: 278
Nature: Enhancement
Severity: Minor
HTTP User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Description
The PSM mapping of BuiltinTopicKey_t is defined to be as; struct BuiltinTopicKey_t { BUILTIN_TOPIC_KEY_TYPE_NATIVE value[3]; }; But the DDS Interoperability Wire Protocol (RTPS) specifies that GUID consists of 12 bytes GuidPrefix and 4 bytes EntityId. In order to map GUID and BuiltinTopicKey, we should define BuiltinTopicKey as the following; struct BuiltinTopicKey_t { BUILTIN_TOPIC_KEY_TYPE_NATIVE value[4]; };