Personal Data Store Project


Published on

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Personal Data Store Project

  1. 1. <ul><li>Kaliya Hamlin @identitywoman </li></ul><ul><li>Markus Sabadello </li></ul><ul><li>Joseph Boyle @Josephboyle </li></ul><ul><li>Joe Johnston @simple10 </li></ul>The Personal Data Store (PDS) Project 1
  2. 2. What is a Personal Data Store?* <ul><li>A cloud service for storing personal life bits </li></ul><ul><ul><li>Could be anything you create or do online </li></ul></ul><ul><ul><li>Could be your own server or a PDS service provider </li></ul></ul><ul><li>Under the complete control of an individual </li></ul><ul><ul><li>Like a personal bank account </li></ul></ul><ul><ul><li>Like banking, no third party (including PDS provider) has access to any of this data without permission </li></ul></ul><ul><li>Provides portability of personal data across all PDS-enabled service providers and consumers </li></ul><ul><ul><li>This standard PDS interchange capability is called PDX (personal data exchange) </li></ul></ul>2 * Also called “personal data service”, “personal data locker”, and “personal data vault”
  3. 3. Core thesis 3 Personal data stores and PDX provide a strong, user-centric foundation for both person-to-person relationships (federated social web) & person-to-business relationships (vendor relationship management)
  4. 5. PDS as foundation for P2P social web <ul><li>Allows every individual to create their own interconnected social graph based on open protocols </li></ul><ul><li>Each person can decide how open or how closed to be about every relationship </li></ul><ul><li>Provides a standard global API for social applications </li></ul><ul><ul><li>“TCP/IP for relationships” </li></ul></ul>5
  5. 6. Groups: beyond networked individualism <ul><li>Groups are not “just the same” as individual nodes </li></ul><ul><ul><li>Complex, first-class data sharing entities </li></ul></ul><ul><li>PDX can enable groups to be defined and shared interoperably across all PDX providers and consumers </li></ul><ul><li>Group relationships use the same portable authorization and access control as individual relationships: XDI link contracts </li></ul>6
  6. 7. Phil Windley* on PDX 7 “ One thing we discovered with KRL (Kynetx Rule Language) early on was that interesting rulesets were often going to tie to multiple sets of permissioned data and that having a user go through multiple ‘allow-deny’ ceremonies when they start up was a bad user experience. PDX solves that problem.”    * Founder and CTO of Kynetx ( and archictect of Kynetx Rules Language (KRL)
  7. 8. PDS as foundation for VRM <ul><li>Enable “volunteered personal information” </li></ul><ul><ul><li>A direct connection between individuals and the vendors they do business with or the organizations they belong to </li></ul></ul><ul><ul><li>The “inverse of CRM” – the customer manages the vendor as much as the vendor manages the customer </li></ul></ul><ul><li>Already being implemented by Mydex in the UK </li></ul><ul><ul><li>Participating vendors include the UK national government, several local authorities, a data aggregator, and the UK’s largest online parenting organization. </li></ul></ul>8
  8. 9. <ul><li>Tech Interop: PDX XDI </li></ul>The two halves of PDX 9 Policy Interop: PDX Trust Framework <ul><li>“ Semantic JSON” </li></ul><ul><li>Portable format for all PDX data </li></ul><ul><li>Portable authorization/access control format (XDI link contracts) </li></ul><ul><li>Includes shared PDX XDI dictionary services </li></ul><ul><li>Extensibility & mapping to other protocols/formats </li></ul><ul><li>Open Identity Exchange (OIX) service </li></ul><ul><li>Enables risk-based certification of PDX providers/consumers </li></ul><ul><li>Can support all levels of assurance/protection </li></ul><ul><li>Self-certification </li></ul><ul><li>Social certification </li></ul><ul><li>Third-party certification </li></ul>
  9. 10. XDI DATA IN PDS 10 =!1111.aaaa.bbbb.cccc <-- =alice --> $is =( =( $is$a +person +street &quot;100 Main St&quot; +city &quot;Seattle&quot; +zip &quot;98101&quot; +country &quot;USA&quot;
  10. 11. XDI MESSAGE TO PDS 11 =!2222.xxxx.yyyy.zzzz <-- =bob --> $get / =!1111.aaaa.bbbb.cccc <-- =alice --> +street +city
  11. 12. XDI LINK CONTRACTS (1) 12 =!1111.aaaa.bbbb.cccc$has$1 <-- =alice --> $is$a $has $has$a $a $get / =!1111.aaaa.bbbb.cccc <-- =alice -->
  12. 13. XDI LINK CONTRACTS (2) 13 =!1111.aaaa.bbbb.cccc$has$1$a <-- =alice --> $is$a $a $is$has =!2222.xxxx.yyyy.zzzz <-- =bob -->
  13. 14. Code <ul><li>What exists already: </li></ul><ul><ul><li>Core native XDI PDS component </li></ul></ul><ul><ul><li>Code for resolving XRI addressing of PDX documents </li></ul></ul><ul><ul><li>OpenID endpoint </li></ul></ul><ul><ul><li>Very basic web interface for managing the PDS and PDX social address book (see ) </li></ul></ul><ul><li>Next steps: </li></ul><ul><ul><li>Webfinger support </li></ul></ul><ul><ul><li>PDX web address book sync </li></ul></ul><ul><ul><li>PDX mobile address book sync </li></ul></ul><ul><ul><li>Getting existing code packaged and available </li></ul></ul>14
  14. 16. 15
  15. 17. 16
  16. 18. 17
  17. 19. Talk to us <ul><li>Hang with Markus, Joseph, or Joe at OSCON </li></ul><ul><li> </li></ul><ul><li>[email_address] </li></ul><ul><li>OR ping any of us on Twitter </li></ul><ul><li>@identitywoman </li></ul><ul><li>@josephboyle </li></ul><ul><li>@versionvega </li></ul><ul><li>@drummondreed </li></ul>19
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.