Building a Protocol to Improve DSR Flexibility and Integration
summary
A concrete open source protocol implements the Data Rights Protocol: JSON payloads with three required blocks—data subject identity, controller metadata, and request metadata—plus optional form data and context variables for hidden IDs. Handshakes go controller→processor with synchronous access responses or asynchronous flows (204 pending plus completion events), results served from a processor results endpoint, and webhooks for status. Claim: standardized, minimal fields plus these flexibility levers cut integration work and scale controller–processor networks without bloating APIs.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:12DSR protocol need
- 4:22Protocol handshake and API
- 7:33Protocol flexibility areas
- 9:44Key learnings
related talks
20mSecuring and Standardizing Data Rights Requests with a Data Rights Protocol
53mDomain-Driven REST
11mData as an Asset: Transforming Ownership in the Digital Age
40mDefining the data model of HTTP messages, not just the format
01h 19mMaking sense of the right to data portability
01h 18mDATA PROTECTION AS CORPORATE SOCIAL RESPONSIBILITY
31mA Tour of LF Energy's Connected Data Specifications (CDS)
01h 18mApproaches to DSA Data Access