resources

1 row where summary = "research/papers/papers-sedi-policy-and-technology-trade-space" sorted by date descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: last_checked (date), date (date)

year 1

level 1

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
papers-sedi-policy-and-technology-trade-space Talks and presentations talk SEDI Policy and Technology Trade Space: Comprehensive Solutions vs. Incremental Solutions https://github.com/SmithSamuelM/Papers/blob/master/presentations/SEDI_Tradeoff.web.pdf {'name': 'Samuel M. Smith'} no change in six to eighteen months; still correct quiet 2026-10-15 2025-10-01 2025 practitioner an author's paper, deck, tutorial or post explaining the suite informative anyone with the link public A 207-slide deck by Samuel M. Smith dated 2025/10/01, subtitled "How to best protect citizens from exploitation with citizen-sourced, state-endorsed digital identity". It sets out the security and privacy trade-offs for SEDI (state-endorsed digital identity) and argues for KERI (Key Event Receipt Infrastructure) and ACDC (Authentic Chained Data Container) anchored issuances over unlinkable signature schemes. For policy makers and practitioners. {'name': 'Samuel M. Smith'}                           SmithSamuelM/Papers (whitepapers and presentations) smith-papers SEDI Policy and Technology Trade Space: Comprehensive Solutions vs. Incremental Solutions research/papers/papers-sedi-policy-and-technology-trade-space   1 1        

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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);