Personal Data Store Project
Upcoming SlideShare
Loading in...5
×
 

Personal Data Store Project

on

  • 5,839 views

 

Statistics

Views

Total Views
5,839
Views on SlideShare
5,611
Embed Views
228

Actions

Likes
9
Downloads
77
Comments
0

2 Embeds 228

http://www.identitywoman.net 227
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Personal Data Store Project Personal Data Store Project Presentation Transcript

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