Rebranding - clarifications
Hi,
I need some clarifications about the impacts of Refinitiv rebranding activity.
Let me suppose the case of EMA C++, which is impacted by the rebranding.
- A customer of mine uses an old version of my application, linking a not-rebranded version of the EMA library. Can they still use it after July 2021?
- I need to release a patch of this old version of my application (e.g. due to a bug in my application logic), but the application is still linking a not-rebranded version of the EMA library. Can still I do it after July 2021?
Thanks for your help
Best Regards,
Paolo
Best Answer
-
cc: @umer.nalla
I concur with Umer; after 31st July 2021, Refinitiv cannot publish code containing references to 'Thomson Reuters'. However, it is not a problem for you to release a patch of your product that uses a non-rebranded version of the EMA C++ API after July 2021. Non-rebranded versions will continue to work beyond that date.
Hope this helps.
Kind Regards
Tirthankar
2
Answers
-
Just to confirm the official position post-July 2021
Older version will not be supported (including emergency/blocker issues). Publishing code that references “Thomson Reuters” will result in a claim of trademark infringement against Refinitiv.
• All fixes will be done on the newly rebranded version.
• Customers can continue to use an unsupported old version. NOT RECOMMENDED.
Therefore, based on the above, you could continue to use older versions and release a patch for your application built with the older version.
However, if your customer reports an issue - which turns out to be an EMA issue and you report the issue to Refinitiv, we will only provide a fix for that issue using a newer rebranded version of EMA.
0 -
Hi @umer.nalla,
thanks for the quick reply.
Actually, I thought that "Publishing code that references “Thomson Reuters” will result in a claim of trademark infringement against Refinitiv." matched the point 2. of my original question.
I now understand that this is something different, but what precisely?
Thanks again
Paolo
0 -
I assumed that meant if we as Refinitiv publish code containing Thomson Reuters.
I will ask the API Product owner to confirm.
0 -
Thanks, looking forward for a confirmation.
Best regards,
Paolo
0 -
Thanks for the confirmation
0
Categories
- All Categories
- 6 AHS
- 37 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 中文论坛