What DataPortability Is / Isn't
A_W_Morse
- Defining Data Portability related terminology
- Advocating best practice in Data Portability
- Leading the dialogue on users' proprietory rights in their generated
content and contact data
- Encouraging contribution from all online space stakeholders
- Disseminating findings / reports to the online community
- Encouraging data repositories to enable Users to simply download
and/
or migrate content
DataPortability Is Not:
- Advocating a proprietary technology solution
- Aimed at removing revenue streams from repository sites
Benoit SIBAUD
A_W_Morse wrote:
> DataPortability Is:
Nothing about open standards or interoperability?
> DataPortability Is Not:
>
> - Advocating a proprietary technology solution
Did you mean no proprietary solutions like Skype for Chat or Clearspace
for discussion and documents?
Regards,
--
Benoīt Sibaud
Julian Bond
14:21:25
There is a difference between what DP advocates for sites as part of its
evangelism mission and what it uses itself for its own needs.
When we say DataPortability Is Not: Advocating a proprietary technology
solution it surely means not requiring participating sites to use a
closed technology standard. I don't think we'd want to exclude the use
of proprietary solutions as long as they are open in the sense that they
support data portability. But equally we wouldn't want to require the
use of a proprietary data portability standard unless it was the only
one available in a particular technical area.
Does that help at all? Arguably, DP shouldn't use closed proprietary
technology at all even for its own needs. But IM is particularly awkward
here as the only truly open standard (Jabber) is just not as good as
Skype. Or at least the current crop of clients and services. (IMHO. I
know others would not agree with that). Google Groups, PBWiki,
Confluence and Clearspace are all from commercial organisations. They
are all to some extent proprietary. Does that mean DP has to run it's
own servers using Mediawiki and Mailman (say) in order to be seen to be
doing the right thing? That seems a little harsh.
--
Julian Bond E&MSN: julian_bond at voidstar.com M: +44 (0)77 5907 2173
Webmaster: http://www.ecademy.com/ T: +44 (0)192 0412 433
Personal WebLog: http://www.voidstar.com/ skype:julian.bond?chat
Clerk Cannot Open
Elias Bizannes
http://liako.biz/2008/03/can-you-answer-my-question/
Essentially, we need to determine the question of who owns your data
On Mar 4, 2:24 am, Julian Bond <julian_b...@voidstar.com> wrote:
> Benoit SIBAUD <benoit.sib...@orange-ftgroup.com> Mon, 3 Mar 2008
Adriana
possible within the legal interpretation of ownership in the online
environment (meaning once your data is out there, you don't really
have control over it). I think it helps to differentiate between data
that you generate and data that others generate about you (in
transactions and interactions with you). To me is paramount that the
former is owned by you. The issue of the latter has to be handled via
relationships and better balance of power that currently exists
between those who gather your data/data about you and you as an
individual.
There are not many tools in existence to help you capture, manage,
analyse and share that data. It is all done via platforms in exchange
for some functionality that is usually helpful to the user. But the
infrastructure to help you 'own' your data, in a sense that you are
the most authoritative source of data about you is missing. This is
where I feel VRM comes in, as we start from wanting to 'defrag your
identity'. Without meaning to make DP a subset of VRM (it isn't, it is
more like a crucial requirement of it) I see data portability as an
essential component of my online existence, interactions and
ultimately transactions. My current focus is in making that data
portable to a place (working name MINE) where I can do stuff with it -
definitely an open source project.
This might be helpful http://www.mediainfluencer.net/2008/02/vrm-one-pager/
a brief summary of how I feel about data and where I think VRM can
address that.
Adriana
Mike Pearson
OWNERSHIP - exclusive rights to possess, enjoy, and dispose of an
object. [ref]
Note: See the related definitions for various OWNERSHIP TYPES.
Ownership Types
Loshin (2002) identifies a list of parties laying a potential claim to
data [ref]:
* Creator - The party that creates or generate data
* Consumer - The party that uses the data owns the data
* Compiler - This is the entity that selects and compiles
information from different information sources
* Enterprise - All data that enters the enterprise or is created
within the enterprise is completely owned by the enterprise
* Funder - the user that commissions the data creation claims
ownership
* Decoder - In environments where information is "locked" inside
particular encoded formats, the party that can unlock the information
becomes an owner of that information
* Packager - the party that collects information for a particular
use and adds value through formatting the information for a particular
market or set of consumers
* Reader as owner - the value of any data that can be read is
subsumed by the reader and, therefore, the reader gains value through
adding that information to an information repository
* Subject as owner - the subject of the data claims ownership of
that data, mostly in reaction to another party claiming ownership of
the same data
* Purchaser/Licenser as Owner - the individual or organization
that buys or licenses data may stake a claim to ownership
NOTE: We should cross-reference with other terminology glossaries such
as OpenID 2.0 and SAML