Source: OCI ( Adam Mitz)
Table 8.73 "availableBuiltinEndpoints" describes the PIM's datatype BuiltinEndpointSet_t using 6 constants (note: change text in this table to indicate that each constant denotes a potential member of the Set not the Set itself). The PIM also maps these constants to EntityId_t values in 188.8.131.52.
The PSM fails to directly reference these constants for BuiltinEndpointSet_t in Table 9.4.
PIM PSM notes none DISC_BUILTIN_ENDPOINT_PARTICIPANT_ANNOUNCER needed? none DISC_BUILTIN_ENDPOINT_PARTICIPANT_DETECTOR needed? PUBLICATIONS_WRITER DISC_BUILTIN_ENDPOINT_PUBLICATION_ANNOUNCER clarify mapping PUBLICATIONS_READER DISC_BUILTIN_ENDPOINT_PUBLICATION_DETECTOR clarify mapping SUBSCRIPTIONS_WRITER DISC_BUILTIN_ENDPOINT_SUBSCRIPTION_ANNOUNCER clarify mapping SUBSCRIPTIONS_READER DISC_BUILTIN_ENDPOINT_SUBSCRIPTION_DETECTOR clarify mapping TOPIC_WRITER missing add to PSM TOPIC_READER missing add to PSM none DISC_BUILTIN_ENDPOINT_PARTICIPANT_PROXY_ANNOUNCER remove? none DISC_BUILTIN_ENDPOINT_PARTICIPANT_PROXY_DETECTOR remove? none DISC_BUILTIN_ENDPOINT_PARTICIPANT_STATE_ANNOUNCER remove? none DISC_BUILTIN_ENDPOINT_PARTICIPANT_STATE_DETECTOR remove? PSM-only BUILTIN_ENDPOINT_PARTICIPANT_MESSAGE_DATA_WRITER add to PIM? PSM-only BUILTIN_ENDPOINT_PARTICIPANT_MESSAGE_DATA_READER add to PIM?
To satisfy the PIM, the PSM must also describe how vendors add extensions to this list. Perhaps the best way to do that is to use a separate vendor-specific PID, but that should be described in the PSM to avoid vendors using reserved bits.
It would be good if the spec was consistent about naming for the PSM constants. Some start with DISC_ while others don't. Some use the brand new terms "announcer" and "detector", others don't.
Reported: DDSI-RTPS 2.2 — Mon, 18 Dec 2017 17:34 GMT
Updated: Wed, 10 Jan 2018 16:08 GMT