Google Wave, the role of the W3C, and maybe some neat tech work

We've had a wave of invited guests, and we have a few more planned for
November. But maybe it would be useful to step back and look at some
interesting tech work we could propose in our technical overview
deliverable.

Based on our previous two meetings with Evan and Peter, it's
interesting that Google Wave keeps coming up again and again. Its
combination of combining e-mail with collaborative work, particularly
on documents, using the updating of XML documents, seems like it
might, to quote a friend of mine, have the power to disrupt even
e-mail.

I'd to hear what people think about Google Wave, and the role of the
W3C in particular in this area.  Google has, like Peter did with
Jabber, committed to making Google Wave an open system, and this is
shown by its federation of using XMPP. The protocol is currently
written as a spec [1].  Interestingly enough, like FOAF, security is
provided via TLS, using a combination of URIs and ID strings. However,
user-data is not federated, that is, not shared with other wave
providers. This seems like an interesting place for FOAF/Linked Data
to step, as well as non-Semantic Web mechanisms like XRD-S and
Portable Contacts

What do people think, or have any ideas here? Does anyone know of any
work in this area? Or would be interested in working on this area?

We need to present a broad overview of the technical work in the
Social Web to the W3C, including existing work, but also with our
thinking headed to the future.

[1] http://www.waveprotocol.org/draft-protocol-specs/draft-protocol-spec

Received on Friday, 9 October 2009 17:57:59 UTC