EMA C++ RDM Usage Guide : 1 Introduction : 1.8 Conventions : 1.8.2 General Transport API Syntax
 
1.8.2 General Transport API Syntax
The Enterprise Message API uses the following general API syntax conventions:
Dot-separated notation indicates data available within a hierarchy. Each period can indicate a structure, a data memberName, an entry, or an element name.
StreamID values are assigned by the application and used across all domain models. Consumer applications assign positive StreamID values when requesting content and interactive provider applications respond using the same StreamID. Non-interactive provider applications assign negative StreamID values.
Payload generically refers to the message payload.
Integer constants are defined in all capital letters with underscores (e.g., MMT_MARKET_PRICE, SERVICE_INFO_ID). In the Enterprise Message API, they can be found in the refinitiv::ema::rdm namespace and in the Access/Include/EmaRdm.h file.
The names of Enterprise Message API FilterId values (e.g. SERVICE_INFO_ID) correspond to the flag value enumeration defined for use with the message key’s ilter (e.g., SERVICE_INFO_FILTER). Names may be shortened for clarity (e.g., DirectoryInfo).
The names of the data members correspond to the method names for both get/set in the Enterprise Message API interface, with the get prefixes removed and the first character always upper case.