About a-team Marketing Services
The knowledge platform for the financial technology industry
The knowledge platform for the financial technology industry

A-Team Insight Blogs

FOW TRADEdata in Dialogue with Bloomberg to Incorporate Identifiers into Xymbology, Says IPUG

Subscribe to our newsletter

Following its letter to petition Bloomberg to allow its symbology to be included in FOW TRADEdata’s service Xymbology, the Information Providers User Group (IPUG) indicates that a dialogue has begun between the two vendors to incorporate both the BUID and the new Bloomberg Global ID (BBGID), which is at the heart of its open symbology initiative, in the service. To this end, FOW TRADEdata is currently seeking further client support to continue down this road and IPUG’s letter is therefore just the beginning.

In its letter to Bloomberg, IPUG describes the Bloomberg Open Symbology (Bsym) initiative, which was launched in November last year, as “very welcome” but notes that the vendor must now follow through with its promise of being “open”.

The Bsym initiative essentially entails the royalty free distribution of Bsym identifiers, which the vendor says is open to all, and the gradual migration from the existing BUID identifier to the new BBGID global identifier. With the aim of proving this openness, Bloomberg signed an agreement in April this year with NYSE Euronext to include its Bsym codes on NYSE’s data feed products globally. NYSE Euronext is initially adding Bloomberg Bsym codes to its OpenBook product and will then move on to distribute Bsym along with its standard security identifiers for New York Stock Exchange-listed companies across all its data products.

IPUG is therefore looking for a similar agreement to be signed with derivatives market specialist FOW TRADEdata. Its Xymbology service carries a number of market and independent software vendors’ symbology at the traded series level, but it does not as yet carry Bloomberg’s.

The industry group highlights in its letter to Bloomberg the challenge a firm faces in “the complex task of managing a wide and diverse universe of identifiers within its trading operation and especially in the area of derivatives”. It therefore asks the vendor to make the lives of its constituents that much simpler by opening up its symbology to another route to market.

The lobbying is reflective of the general desire within the user community for lower costs and easier access to instrument identifiers that have until now been largely proprietary to individual data providers.

Subscribe to our newsletter

Related content

WEBINAR

Recorded Webinar: Hearing from the Experts: AI Governance Best Practices

The rapid spread of artificial intelligence in the financial industry presents data teams with novel challenges. AI’s ability to harvest and utilize vast amounts of data has raised concerns about the privacy and security of sensitive proprietary data and the ethical and legal use of external information. Robust data governance frameworks provide the guardrails needed...

BLOG

Nature-Risk Data Proposals Hailed as Pathway to Better Investment Decisions

Proposals to improve the nature-risk data value chain has been welcomed by sustainability data leaders who said they will pave the way for better decision making and reporting by financial institutions and provide more detailed analyses for investors. The proposals offer a slate of principles to improve the quality of state-of-nature data collection and integration...

EVENT

AI in Capital Markets Summit London

Now in its 2nd year, the AI in Capital Markets Summit returns with a focus on the practicalities of onboarding AI enterprise wide for business value creation. Whilst AI offers huge potential to revolutionise capital markets operations many are struggling to move beyond pilot phase to generate substantial value from AI.

GUIDE

FRTB Special Report

FRTB is one of the most sweeping and transformative pieces of regulation to hit the financial markets in the last two decades. With the deadline confirmed as January 2022, this Special Report provides a detailed insight into exactly what the data requirements are for FRTB in its latest (and final) incarnation, and explores what needs to be done in order to meet these needs on a cost-effective and company-wide basis.