New version of wiki-data is live

I’m pleased to say that the new version of www.wiki-data.com is now live. There is also a link from our website.

Features of this new version:

- It has been developed in open source software which will provide significant flexibility to clients when the client specific version of the site is rolled out.

- Every Avox ID (AVID) is a distinct URI (Uniform Resource Identifier) enabling links to and from the entity record. There are no restrictions on the use of AVID, nor are there any license fees associated with it.

- We have put more data fields into this version of wiki-data including formerly known as name, also known as name, trading status, URL and additional operational address details.

- Users can hide/show columns, sort content in columns, click the AVID and land on a company page with a google map, filter content, challenge data values, request additional data for a record and request new records.

- Limited numbers of additional data and new record requests will be processed at no charge. We will soon have a charging mechanism in place for requesting more data and new records. Existing clients will be able to apply these requests against their existing contracts if they wish.

- There is a facility called “New app ideas” at the bottom of the screen where users can suggest and vote for new functionality.

- An email support function is also included at the bottom of the screen.

We have already started working on the client specific version of this application called “my-wiki-data” which will provide clients with more visualization, query and API functionality. We look forward to getting your feedback on both this public site and the client site as it evolves. Don’t hesitate to call if you have any questions. We hope that this new capability is helpful.

Please note that the email request function on the previous version of wiki-data was corrupted and not operational during the past two weeks. My apologies if you had tried to use that capability and received no response. It is working with this new version.

Democratization of Data (or not?)

I had an interesting conversation with someone who manages corporate customer data for a major investment bank last week. She said that she had read our blog and developed the impression that Avox was attempting to democratize entity data. In her opinion (and as it turns out, in mine), this alone is likely to degrade the overall quality level of the content.

After this discussion, it dawned on me that we had better be clear about our objectives at Avox, particularly as they relate to wiki-data.com:

1) Maximize the amount of productive "challenges" received that help us to improve quality of the data in wiki-data.com. Every challenge to records with an AVID will be verified by our expert team of analysts before being applied (assuming, of course, the challenge is proven correct). The "democratization" element of this activity equates to the opening up of a chunk of our content on wiki-data.com for the world to see and for anyone to challenge. BTW, the quality improvement benefits all our data vendor partner offerings too.

2) Provide a platform for others to link to and from. Our next release of wiki-data will incorporate additional identifiers from other firms. The AVID will be part of a URI for each entity enabling the technology community to efficiently leverage a single version of the truth. This will in turn attract more usage, more challenges, lower latency and increased accuracy.

3) Create a forum for anyone to comment on data records, propose changes in public and ultimately to add "non verified" data records which Avox or other firms can verify for clients. This is the big stretch and, if I'm honest, it's the iteration of wiki-data we are least certain about.

To be clear, Avox will never provide to clients data that has not been verified according to the terms of their service level agreements. We do however regularly get asked for large volumes of business entity data to facilitate marketing campaigns for example where data quality is not as important as it is for credit risk management or regulatory compliance. This is where information on millions of entities is sometimes required but the budget for procurement of this content is meager. Perhaps in these cases it is not necessary to have an independent and rigourous analysis performed on every entity at regular intervals and the community self checking mechanism is adequate. Moreover, a global community maintained model may be a great solution for a free and universal yellow pages capability (for example). Over time, more and more of these entities will be verified by expert third parties such as Avox and assigned identifiers as the market demands.

We don't have all the answers however our aim is to give you, the user community, a platform to access and use the content cheaply and efficiently. We are looking for your views and guideance on how to shape wiki-data.com to make it a more market friendly service that represents real value for you.

BTW, keep your eyes open for v1 of wiki-data.com later in September. You can check out Jonathan Lister's blog for progress - the software is opensource.

Ken

Wiki-data development with BT/Osmosoft

It's been a while since my last post but we have been busy working on wiki-data. Some of you will know that we have been in discussions with the open source software group at British Telecom. It's a subsidiary called Osmosoft comprised of some frighteningly clever technologists with impressive credentials and serious talent.

A group of us from Avox including senior management from our Wrexham office, our sales team including Brett Hodge who came over from Australia and myself spent a day with Osmosoft last week. They affectionately refer to these as "HackDays".

Within the space of 10 hours, this team, led by Jeremy Ruston, the Osmosoft founder, put together a brand new (I mean built from scratch) version of wiki-data with some great interactive functionality. We provided the guys with a very large dataset which they used as a base. By the end of the day, we had a platform where every AVID had its own URI (uniform resource identifier) so that anyone can link to or from it, addresses of companies are now linked to Google Maps so you can visualize where firms are based (we quickly found one in Iraq!), anyone can begin a comment string on an entity and yes, we even had an online edit function (we are going to need to figure out how to govern that one before releasing it!).

If you are interested, your best bet is to have a look at Michael Mahemoff's blog where you will find detailed descriptions of the process and outcome as well as a video of me and Paul Downey of Osmosoft running you through the platform before we ran to the pub for pints. Just click on the link (embedded in the heading) at the top of this post.

Or if you prefer: http://softwareas.com/wikidata-hackathon-wikidata-a-wiki-of-companies-data.

I'll keep you posted on what will be rolling out and when. We are extremely excited.

Ken

Who's Got the Entity Data Standard?

It's been an interesting month with many articles and editorials in publications such as Reference Data Review, Inside Reference Data, Global Investment Technology and Securities Industry News to name a few all raising the issue of standards in the business entity data space. There is no shortage of contenders. SIIA is pushing IGI (Issuer, Guarantor ID). SWIFT is considering a role by expanding BIC coverage and addressing the non-uniqueness of the BIC. Factset has made past announcements of their intention to make a public standard available. Other major data vendors such as Bloomberg, ThomsonReuters and D&B already have broad coverage. The European Central Bank is working on a data utility. So is Financial Intergroup's Allan Grody. And so is the Dubai International Financial Centre (DIFC). Avox has an initiative S&P called the CABRE (Cusip, Avox Business Reference Entity). We've also recently launched a free business entity directory (www.wiki-data.com). And of course there are the industry working groups including the EDM Council, JWG-IT and FISD all talking about standards.

This is all looking pretty positive, isn't it??? (NOT!!!).

Let's be honest here. Every commercial firm in this space would love to own the global standard for business entity identification. Think about it. The entire planet "theoretically" would have to pay you and only you for the right to get an authoritative picture of a business entity. Just think of the monopoly play here. Millions of customers needing millions of pieces of information every day. One year's profit would pay off the US national debt.

At least that's what many buyers of such information believe. It's not quite that profitable a picture. Here's why.

There can never be a monopoly provider of this data. The function that all of the above mentioned firms play is that of data aggregator. Some firms use automated matching to provide a consolidated picture, some use manual analysis and all the others a combination of both. The sources we go to are the same that anybody can go to directly.

The sources used typically include national and state business registries, regulatory authorities and tax authorities. All these organizations have an obligation to make information available to the public (although some of them have decided to put a rather hefty price tag on some important data). Some data is not publicly available and various vendors have secured rights to it but by an large, nobody had universal access to everything (the Google guys are trying...).

So where is all this spaghetti going to get us? In my opinion, it's going to get us to where you want to go. Competitive forces are pushing all vendors to be more innovative, cost effective and customer focused. A perfect world in the Avox view is one where everyone works off of the same underlying basic content that uniquely identifies a business entity. The ID becomes a secondary issue but remains important of course.

Some vendors are working to this objective. You won't be shocked to hear that Avox is one of them however a number of firms we have spoken to are also "chilling out" with respect to relinquishing value of the basic data.

Please believe me when I say that Avox does not expect to be able to solve the whole problem on our own when it comes to business entity identification. We can't. But we can help facilitate a quicker convergence onto a standard by being open and "influencing" other firms to be open.

If you buy into this view, let your vendor partners know. The sooner we connect, the sooner you can connect and that's when everyone can get on with the business of efficiently generating returns for customers.

Your Data Geek,

Ken

KYC - Global Regulatory Conflict

On June 4, GoldTier, a KYC software company hosted a speaker panel to discuss the impact of a changing global political and economic environment on the Know Your Customer (KYC) function at financial institutions. One of the discussion points exposed a great deal of frustration amongst the participants which included representatives from North American and European financial institutions.

As a KYC professional at a global financial institution, it is incumbent upon you to ensure that the head office of your firm is aware of their global exposure to any and all customers. This requires transmission of what some consider to be "sensitive" data across international borders. Countries including Singapore, Switzerland and Korea are asserted to have in place data privacy regulations that prevent such data from being sent across their borders. By definition, this would make it legally impossible for firms located outside of those countries to do business there.

This is clearly not the business reality. The problem as I see it is that compliance officers are paid to be ultra conservative and risk averse. This results in overly conservative interpretations of international regulations governing, amongst other things, data protection. This puts them and their firms in an awkward position of having to rely on the opinion of their locally based compliance function to make judgements without having the ability to regularly audit the process and data from a foreign head office. So ironically the risk averse compliance function is introducing a significant risk to their firm by not sending what is typically generic company information between geographies.

We have international clients who have realized this and have engaged with regulators in countries like Singapore to get clarity. Indeed Avox has been involved in some of these discussions directly. In most cases, there is actually no restriction on sending company information outside of these countries. How on earth would firms in these countries do business internationally if this was the case?

It's time for the business to work closely with compliance and have frank discussions with any regulatory body they believe is hampering transparency. Any country that truly prohibits communication of important decision support information outside of their borders needs to be prepared to suffer a drastic reduction in international trade. I think you will find that the reality is most regulators will not stand in the way of legitimate commerce.

Ken

Canada ready to take a reference data lead?

I've just returned from the third of three EDM Council meetings chaired by Mike Atkin, this one in Toronto. The previous recent meetings were held in Boston and London. I was pretty suprised at the contrast.

The Toronto event was well attended by most of the major banks, funds and a number of vendors. John Mulholland of RBC kindly hosted and injected much relevant and interesting comment. A representative from the cash equities business group at CIBC provided a significant amount of challenging, insightful and truly helpful comments. This helped make the Toronto meeting one of the most dynamic and relevant EDM Council meetings yet in my opinion.

It was rather shocking to see the Toronto financial community coming together with so much vigour. I've personally been trying to foster a reference data community here, (where embarrassingly, I'm based) but to little avail. Hats of to Mike and John for getting the ball rolling and to all the firms that participated for grabbing the bull by the horns. Maybe it's time for Canada to start leading the reference data charge...

Ken

wiki-data.com

If I'm perfectly honest, this exercise has been more painful than anticipated.

We started out by planning to publish a "skinny" version of every record in our CORE (COrroborated, Remediated, Enriched) Avox database. Then we realized that a good chunk of these records had been verified over a year ago for clients wanting just a one time clean-up (some folks never learn...) so those records had a reasonable chance of being out of date. As it takes a good 10 minutes per record to recheck, trolling through hundreds of thousands of stale records would take too long and cost too much for this initiative. Given that we are making this content publicly available so everyone can look at it, we thought it would be risky to publish data we knew had a high probably of being out of date.

Then in the pared down database, we found a large number of records that were not unique "legal" entities. That is to say, they were branches, departments or funds which had been included for specific Avox clients at their request. So while these are valid records from their perspective, we've excluded them from wiki-data for now with a view to starting with pure legal entities.

Then we released the database to a small trial audience and, as expected, we received helpful feedback on some quality issues which we have been in the process of addressing. This is exactly what we had hoped for as every new set of eyes that looks at the content brings with them new perspective and knowledge. The community helps improve its own asset. We also received very helpful feedback from users including some of our own staff about the layout of the search facility, the results and the issue filing process.

Perhaps most interesting and encouraging was the fact that one of our competitors provided constructive feedback. Could it be that we may be able to work with eachother to jointly improve our mutual clients' data? Let's see.

So now we feel the database, although slimmed down quite a lot, is ready for broad public viewing and consumption. There will be out of date information. There may be some duplicate values. And yes, I expect there will be some outright errors. It's all expected. All we ask is that you tell us about any problems you find. You just need to click on the "Correction" button next to the record in question.

I know it's a bit of a pain however please do share your feedback/thoughts with respect to wiki-data on this blog. You can just email me if you prefer. We also have a LinkedIn group (Avox business entity discussion forum) set up.

Ken