Dashboard > The DataPortability Project > ... > Action Groups > Policy
  The DataPortability Project Log In | Sign Up   View a printable version of the current page.  
  Policy
Added by daniela barbosa , last edited by Steven Greenberg on May 06, 2008  (view change)
Labels: 
(None)

Tools:

This group's Scope:

To:

  • Identify policy, political and/or legal conflicts affecting data portability plans, design, implementation and operation
  • Foster dialog about those conflicts
  • Document and organize solutions
  • Create and deliver tools to make it easier to adopt  

In a way that:

  • Promotes consensus around policy definitions, designs and strategies
  • Uses the large body of prior work
  • Presents actionable documents
  • Acknowledges the interests of all stakeholders

so that:

  • Engineers and site operators can find and use best practices for the human side of data portability

Classes of Data

The group has identified three broad classifications of data:

  • "First Party data" refers to data that I have entered myself. For the purposes of portability, it is irrelevant whether I "own" the data or not. What matters is that I entered it into the system.
  • "Second Party data" refers to data that some other end user entered, but to which I have access. This could be message board posts, member photo galleries, or address information.
  • "Third Party data" refers to aggregate or derivative data that is generated by the service itself. Third party data may or may not be originally based upon First or Second party data.

Each site, of course, will want to offer a different mix of these three as befits it's particular business model.

All of these models are reasonable and rational. Our goal should be to invent a standard way of discussing them so that users know what to ask for and sites know what is expected.

  • No portability: Sites that deal in taboo or unpopular topics may not want their users to take anything off site. Other sites whose business model is based upon offering a service free of explicit charge, but which use control over user data to force users to return, might not want to allow portability. As long as the user knows what they're agreeing to, these are reasonable.
  • First party portability: The user can freely move data that they have provided, but are discouraged from attempting to download any derivative data
    Limited second party portability: Others can mark their data as being available
  • Full second party portability: Second party data is fully available
  • Fully open: All data on the site, regardless of source, is available.

Feel free to join the live chat in the public Skype chat room for the Policy Blueprint Group. Please refer to Google Groups as the preferred platform to discuss major issues, to announce projects and to present new knowledge.

Policy Work Pages


Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators