Proper RDM dictionaries usage questions
I've been studying the RFA and RDM usage guides and I still can't find answers to some questions.
- The RDM Usage Guide (section 5.8.3) says one should choose the dictionary with the latest version when the same dictionary is provided by multiple services. What if the versions are incompatible, i.e. the major version number differs? Is it possible at all?
- What does "same dictionary" actually mean? Are two dictionaries considered to be the same if their names match? Do their DictionaryIds need to match as well?
- Is it possible for a service directory to list *multiple* dictionaries of the same type (FIELD_DEFINITIONS, ENUM_TABLES, ...) in a single service's DictionariesUsed field?
- If a service requires a dictionary that is provided by multiple services, including itself, should one prefer the version provided by the requesting service itself, or it doesn't matter?
- Are dictionaries with the same version number and name guaranteed to be identical across multiple services?
- Is it idiomatic (or required) to decode Field and Enum dictionaries into the single RDMFieldDictionary class instance, as it is done in the Consumer sample?
References to the user guides and documentation would be very much appreciated.
Best Answer
-
As you are designing the dictionary handler for your app, please consider that you are connecting to the infrastructure (TREP or direct feed) that is supplying your data. RFA gives you an option of downloading the dictionaries from the infra, or loading the dictionaries from a local file. Downloading from infra should almost always be preferred, as it guarantees the correspondence between your dictionary and your data stream.
The dictionaries (field and enum) are per infra host you are connecting to, and if you are subscribing to multiple services from the same infra, the services will be under the same dictionaries.
One can open two sessions simultaneously, to different infras, which may be of different versions with different dictionaries. In this case the data from the session should be parsed with the appropriate dictionaries, downloaded from that infra.
If the dictionaries are uploaded from local files, it's the maintenance responsibility for the application admin to always keep the dictionaries in sync with the infra upstream.
The dictionaries with the identical version are the same.
It is customary to refer to SDK examples for info on working with the dictionaries, yes.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛