what's missing?

0 views
Skip to first unread message

marccanter

unread,
Nov 26, 2007, 9:01:04 PM11/26/07
to DataPortability
shared micro-content databases - sort of like Freebase or Twine - but
free and open to all - open source

exchange photo albums

aggregate the aggregators - how do we do that?

get OpenSocial to go beyond "OpenWidgets"

a PeopleDNS would be nice - I believe Joel DeGan still has the domain

ever heard of ThreadsML? Danny - tell them about it.

whatever happened to the Attribute Exchange - is it just too difficult
to implement? What alternatives are there?



Josh Patterson

unread,
Nov 26, 2007, 9:38:29 PM11/26/07
to DataPortability
Hey Marc, welcome to the group.
My group, floe.tv, is working on a media mixer. We ran into some
testers who really got high on the concept of the application being
"inherently installed" on the internet, and it being able to just
"auto discover" your data by an "openID" type id-system. Thats where
we started and where I coined the term "DHCP for data" (which loosely
fits), and then we began extrapolating a series of "what ifs" and
trying to fit existing comp sci abstractions onto the problem, as
there really isnt anything new under the sun.

Yeah, data discovery is a big deal right now, basically "run time"
discovery of data. I'm not a huge fan of trying to cache data into 3rd
party silos, but people are taking shots at that. So we said "what if
the internet really was one big machine? what if we looked at all
storage as one big disk? one big database? how do we handle those,
algorithm wise, in comp sci?" and we went from there, drawing up a
model, and building a reference abstraction stack (think like the OSI
Network Model):
http://cowbell.floe.tv/WRFS_11_20_2007.html
and then we started filling in the layers with different existing tech
(dont wanna reinvent that wheel). Our goal is to work with Faraday
(Chris, Ashley, Paul, etc) in constructing a reference implementation
that is open meets our goals in terms of the desired user experience.
Feel free to criticize, comment, discuss, etc the WRFS document, its
very much a sketch right now.

Josh Patterson

Chris Saad

unread,
Nov 27, 2007, 2:01:30 AM11/27/07
to DataPortability
Marc - some ideas re: your comments:

On Nov 27, 12:01 pm, marccanter <marccan...@gmail.com> wrote:
> shared micro-content databases - sort of like Freebase or Twine - but
> free and open to all - open source

How does this help the data portability model though? What would be in
those databases? Semantic information about 'concepts'?

>
> exchange photo albums

I think this would need an open standard for 'photos' so we can put it
into the stack - or does someone have a better idea?

>
> aggregate the aggregators - how do we do that?

Well if there is a personal address book 2.0, aggregation of
aggregators is not so necessary is it?

>
> get OpenSocial to go beyond "OpenWidgets"

Ben is working with Myspace - and if we can come up with a
DataPortability reference design we can compliment Google OpenWidget

>
> a PeopleDNS would be nice - I believe Joel DeGan still has the domain

What's he doing with it - is there a technology/idea to go with the
name?

>
> ever heard of ThreadsML? Danny - tell them about it.

Danny tell us about it :)

>
> whatever happened to the Attribute Exchange - is it just too difficult
> to implement? What alternatives are there?

Paul, Josh's?

Brian Suda

unread,
Nov 27, 2007, 4:08:14 AM11/27/07
to datapor...@googlegroups.com
2007/11/27, Chris Saad <chris...@gmail.com>:

> > exchange photo albums
>
> I think this would need an open standard for 'photos' so we can put it
> into the stack - or does someone have a better idea?

--- i think we can look at the way we are already "consuming" photos,
via RSS feeds. I subscribe to friend's flickr photos via RSS. RSS also
has an enclosure element, so it is possible to move binary files
around with some basic metadata attached in the RSS tags, description,
title. The other information can be passed with extentions, like
GeoRSS for lat/lon.

I would equate an album to a feed, then there is apple“s failed
photocasting as well.

Also, as RSS Pull technology begins to feel the weight of bandwidth
issues when scaling, people are experimenting with PUSH. So rather
then me pulling every hour to see if a friend has updated, i
subscribe, then the system pushes/pings me with the new data. Some of
this is jabber, but could easily be the Atom Publishing Protocol.

If it was up to me, that is how i would implement any
"exchange"/notification of binary data.

-brian

--
brian suda
http://suda.co.uk

Danny Ayers

unread,
Nov 27, 2007, 5:40:00 AM11/27/07
to datapor...@googlegroups.com
Hi Marc,

Great to see you in these parts!

On 27/11/2007, marccanter <marcc...@gmail.com> wrote:
>
> shared micro-content databases - sort of like Freebase or Twine - but
> free and open to all - open source

On the more general data-oriented side I'd point to the numerous RDF
stores (many of which are built on DBs like MySQL), e.g.
http://sites.wiwiss.fu-berlin.de/suhl/bizer/toolkits/

...on the more specific (human-readable) content-oriented side, I'd
point to Atom stores, i.e. components that support AtomPub in both
directions (not sure what there is in the way of implementations yet -
try Google :-)

Both approaches offer commodity systems, both are mostly in the open
source world. In both cases I suspect the main obstacle to widespread
deployment right now is developer-unfamiliarity with treating such
systems as building blocks, compared to say ad hoc PHP+MySQL or even
Rails. The big advantage IMHO is that such systems speak richer web
standards out of the box, rather than interconnection being a
piecemeal affair put together after core development.

<plug>
At this point I'm obliged to point out that it shouldn't be necessary
for people to host (download, install, scale, maintain...) their own
storage systems, as long as they have full control of their data,
Software as a Service is an option. The /reason/ I'm obliged to point
this out is so I can plug the Talis Platform, which in short is
comparable to Amazon S3, but much more Web-oriented (and free for
community projects). Check Ian's slides from Friday:
http://n2.talis.com/resources/swig-bristol-2007/
</plug>

> exchange photo albums

That's exactly the kind of scenario where I reckon use of a (the)
resource description framework comes in handy, rather than little
bitty extensions to something like RSS.

> aggregate the aggregators - how do we do that?

Hmm, that should be doable already, but given that not everybody has
Google scale, relevance filtering seems worth attention (!!).

> get OpenSocial to go beyond "OpenWidgets"

Right. That might be your job Marc :-)

> a PeopleDNS would be nice - I believe Joel DeGan still has the domain

Oh yeah - I'd forgotten about that.

There have been some recent semweb developments that might come in handy - e.g.
http://sindice.com

is a fast lookup (try your name as keyword).

more p2p-ish data piping should be useful to, e.g.
http://pingthesemanticweb.com/

> ever heard of ThreadsML? Danny - tell them about it.

"It was the dawn of time..." ;-)

Basically when RSS was going mega it was obvious that discussion
threading (blog comments, newsgroup threads even) wasn't properly
covered. Stuff was worked out, but I reckon it probably happened too
early for mass adoption.

But now there are a couple of approaches that look promising (heh,
Atom and RDF again):

Atom Threading Extensions : http://www.ietf.org/rfc/rfc4685.txt
- is like the minimum necessary

The SIOC (Semantically-Interlinked Online Communities) folks have been
going much richer:
http://sioc-project.org/

(I'd strongly recommend taking a look at what they've got together -
blog tool plugins etc)

though core stuff is straightforward, check this diagram in the spec:
http://www.w3.org/Submission/2007/SUBM-sioc-spec-20070612/#sec-overview

> whatever happened to the Attribute Exchange - is it just too difficult
> to implement? What alternatives are there?

Dunno, but a lot of the attribute-oriented stuff I've seen seems to
overlook the kind of connectivity the web has to offer, reimplementing
a small subset of RDF in a way that's less interesting and much
harder... (grumble, grumble)

At a bit of a tangent, although a lot of work's been done around e.g.
Jabber+FOAF, there still seems to be a long way to go before the IM
protocol stuff gets hooked up with the web in a (end-user) useful
fashion...

Cheers,
Danny.

--

http://dannyayers.com

Chris Messina

unread,
Nov 27, 2007, 10:07:55 PM11/27/07
to datapor...@googlegroups.com
Speaking of Jabber, I'd add it to the stack listed on the homepage.

Chris


--
Chris Messina
Citizen-Participant &
Open Source Advocate-at-Large
Work: http://citizenagency.com
Blog: http://factoryjoe.com/blog
Cell: 412.225.1051
IM: factoryjoe
This email is: [ ] bloggable [X] ask first [ ] private

Terrell Russell

unread,
Nov 28, 2007, 7:08:18 PM11/28/07
to DataPortability
Definitely. I see XMPP being the single greatest vector for getting
this data moving around once we're ready to move it. It's open, it's
extensible, and it's already in front of millions of people.

Terrell


On Nov 27, 10:07 pm, "Chris Messina" <chris.mess...@gmail.com> wrote:
> Speaking of Jabber, I'd add it to the stack listed on the homepage.
>
> Chris
>
> On 11/27/07, Danny Ayers <danny.ay...@gmail.com> wrote:
>
>
>
>
>
> > Hi Marc,
>
> > Great to see you in these parts!
>

Chris Saad

unread,
Nov 28, 2007, 11:11:57 PM11/28/07
to DataPortability
Brian - Agreed on RSS Feed = Album.

Regarding the Push RSS thing - we have a solution for that - coming
soon

Chris

On Nov 27, 7:08 pm, "Brian Suda" <brian.s...@gmail.com> wrote:
> 2007/11/27, Chris Saad <chris.s...@gmail.com>:

Chris Saad

unread,
Nov 28, 2007, 11:14:09 PM11/28/07
to DataPortability
Agreed Chris - Jabber is going to be huge - it is also part of the
push solution I mentioned above - stay tuned.


On Nov 28, 1:07 pm, "Chris Messina" <chris.mess...@gmail.com> wrote:
> Speaking of Jabber, I'd add it to the stack listed on the homepage.
>
> Chris
>
> On 11/27/07, Danny Ayers <danny.ay...@gmail.com> wrote:
>
>
>
>
>
> > Hi Marc,
>
> > Great to see you in these parts!
>

Mike Reynolds

unread,
Nov 28, 2007, 11:21:15 PM11/28/07
to DataPortability
Not sure if this is a pipe dream, but it's sort of related to
distributed files and perhaps types of aggregated databases. If
Google is only giving us OpenWidget, then is there a way for people to
opt into an OpenConnectionsDB? While OpenSocial can tell things about
our friends, OpenConnectionsDB could be a meta-container that really
helps us open the social graph.

In terms of data portability, I'd want to be able to aggregate all of
my friends together (LinkedIn, Facebook, etc). This could make it
happen. We'd need strict rules for privacy/etc and I'm not sure it
would ever work, just thought I'd share.

Mike

Chris Messina

unread,
Nov 28, 2007, 11:33:33 PM11/28/07
to datapor...@googlegroups.com, DataPortability
Any reason why XFN + OAuth isn't sufficient for this?

A principle for this group should be to invent as little as possible
and reuse as much as is useful.

Chris

Sent from my iPhone

Danny Ayers

unread,
Nov 29, 2007, 6:39:15 AM11/29/07
to datapor...@googlegroups.com
On 29/11/2007, Chris Messina <chris....@gmail.com> wrote:
>
> Any reason why XFN + OAuth isn't sufficient for this?

That's distributed files covered, publishing connection data, but
doesn't go very far as an aggregated database. For that I'd personally
use (er, am using) an RDF store - it can source data from XFN (and
other things, [1,2]), transparently merge, and allows querying, with
the results presentable however you like (e.g. as hCards [3]).

> A principle for this group should be to invent as little as possible
> and reuse as much as is useful.

Yup.

Cheers,
Danny.

[1] http://esw.w3.org/topic/CustomRdfDialects
[2] http://esw.w3.org/topic/ConverterToRdf
[3] http://dannyayers.com/2007/11/04/foaf-sample-data-and

Sent from my vacuum cleaner.

--

http://dannyayers.com

Chris Saad

unread,
Nov 29, 2007, 8:33:42 PM11/29/07
to DataPortability
Ok I have added XMPP to the page - does anyone know key players in
that community to include in this DP group?

Also CTO of JanRain has expressed interest

On Nov 28, 1:07 pm, "Chris Messina" <chris.mess...@gmail.com> wrote:
> Speaking of Jabber, I'd add it to the stack listed on the homepage.
>
> Chris
>
> On 11/27/07, Danny Ayers <danny.ay...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi Marc,
>
> > Great to see you in these parts!
>
> This email is: [ ] bloggable [X] ask first [ ] private- Hide quoted text -
>
> - Show quoted text -

Chris Messina

unread,
Nov 29, 2007, 9:10:50 PM11/29/07
to datapor...@googlegroups.com, Peter Saint-Andre
I know St. Peter, the patron saint of Jabber. (CC'd).

Chris

Mike Reynolds

unread,
Dec 1, 2007, 1:18:24 AM12/1/07
to DataPortability
Is XMPP/Jabber a solution for pushing comments and other message
interactions? I see that some blogs have Comments Feeds. Would it
make more sense for comments to be stored in XMPP?

Chris Messina

unread,
Dec 1, 2007, 1:33:42 AM12/1/07
to datapor...@googlegroups.com
You could -- especially for real-time notification.

One way to think about it is to look at all those "subscribe to
comments by email" options on blogs... follow up comment notification
(and social network service messages) could actually be delivered via
Jabber, providing a great deal more control and semantic richness than
email.

Chris

Danny Ayers

unread,
Dec 3, 2007, 4:29:34 AM12/3/07
to datapor...@googlegroups.com
On 01/12/2007, Chris Messina <chris....@gmail.com> wrote:
>
> You could -- especially for real-time notification.
>
> One way to think about it is to look at all those "subscribe to
> comments by email" options on blogs... follow up comment notification
> (and social network service messages) could actually be delivered via
> Jabber, providing a great deal more control and semantic richness than
> email.

I like the sound of that - I bet there are quite a few other places
would be a nice fit too, Wiki RecentChanges springs to mind.

--

http://dannyayers.com

Reply all
Reply to author
Forward
0 new messages