resources
1 row where kind = "regulator" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: last_checked (date)
type 1
level 1
access 1
year 0
| id | type | name | url | maintainer | status | last_checked | date ▲ | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| european-banking-authority | Organizations organization | European Banking Authority | https://www.eba.europa.eu/ | European Banking Authority | changed within the last six months, or a live service active | 2026-10-21 | practitioner | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | The European Union's banking regulator, whose Pillar 3 Data Hub GLEIF's consultation reply of March 2024 argues the vLEI fits, and which a trade-press article says tested the vLEI in a proof of concept that met its core requirements. The authority's own pages were not reached, so the pilot rests on GLEIF's paper and the press. Source read 21 October 2026: https://www.gleif.org/lei-solutions/regulatory-use-of-the-lei/consultation-responses/2024-03-28-gleif-response-eba-pillar3_v1.0.pdf and https://a-teaminsight.com/blog/gleif-begins-a-new-decade-in-growth-mode/. | 1 | 0 | regulator | Finance and legal entities finance | EU | a proof of concept of the vLEI for Pillar 3 Data Hub submissions, per GLEIF's consultation reply and the trade press |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE resources (id TEXT PRIMARY KEY, type TEXT REFERENCES types(id), name TEXT, url TEXT, maintainer TEXT,
status TEXT REFERENCES statuses(id), last_checked TEXT, date TEXT, year INTEGER, level TEXT REFERENCES levels(id),
evidence TEXT REFERENCES evidence(id), access TEXT REFERENCES access(id), abstract TEXT, authors TEXT, series TEXT,
chair TEXT, minutes TEXT, recording TEXT, media TEXT, decisions TEXT, version TEXT, language TEXT, license TEXT,
release TEXT, pushed TEXT, depends TEXT, since TEXT, via TEXT REFERENCES resources(id),
summary TEXT REFERENCES notes(path), note TEXT, has_abstract INTEGER, has_summary INTEGER,
kind TEXT REFERENCES kinds(id), sector TEXT REFERENCES sectors(id), country TEXT, products TEXT);