http://anders.conbere.org/journal/dataportability-needs-bring-something-table/
I've been saying this for a while now, but I think that if we want
adoption of tools like xfn and foaf that really mean something
(participants in that ecosystem not just digesters of data), we need
to have tools that bring something to the table. We need to provide
tools to help social network creators reduce the complexity of their
applications, reduce the entry cost of joining a social network, etc.
and right now importing data a) isn't at a point where it's dirt
simple for users, and b) isn't the big pain point for social network
creators.
That being said, if these tools provided ways to effectively abstract
the user relationships tables, and provided messaging tools etc. Those
are real pain points, and the easier we make those efforts the more
effective we'll be at selling this technology to up and coming social
networks.
~ Anders
This posts seems to me to be wandering all over the data portability
landscape with some fairly muddled thinking. Which I think really points
to the poor job being done by each group to explain what their part of
the solution does, why it's important and where it fits into the
landscape. So the question here for DataPortability is what we can do to
explain the concepts and help each group do a better job of explaining
themselves.
--
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
Multigrain For A Unique Taste
I just want to understand what all the different churches are, Phil.
All I hear is a lot of complaining about this project without any
substantive content about what it is doing wrong and what other
churches are doing right. If there is anything substantive being
said, I'm not hearing it and want to understand how I can.
Further, by using the religious metaphor, are you saying that the
different churches will never agree?
Regarding your question, "good enough to work the steps," I guess I'm
not clear on what steps exist other than the process this project has
collaborated to create.
This is making me think that DataPortability the organisation is really
about promoting the idea of data portability, helping explain what it
is, and working with groups that are building infrastructure or
applications and encouraging them to make it central to what they're
doing.
If that's the case then DataPortability looks less like a formal
standards organisation and more like a promotion vehicle. GetFirefox,
not Firefox; OpenidEnabled, not OpenId. It also implies that
DataPortability becomes a fairly loose clearing house for people who
believe passionately in this idea and encourages them to go out and
evangelise wherever and whenever it's needed.
The side effect of this is that no existing body should feel threatened
by DataPortability. There is no competition because what we would be
doing is promoting what they're doing not trying to replace it or choose
among alternatives.
Another side effect here is that formal governance procedures and
organisation process become much less important. The only thing that is
important is that lots of people are talking about data portability.
--
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
Always Replace The Cap