I have watched in dismay in the last months as I have been forced to accept the same connections via LinkedIn.com, Plaxo, Facebook, MySpace, Mix2r.com and a number of other social networking sites.
Why can't someone build a portal using the XFN (XHTML Friend Network) microformat to allow these connections to be only declared once. Then an API can federate it to all sites wanting to declare this sort of information. James Governor wrote a piece for the O'Reilly Web 2.0 Design Patterns book on the Synchronized Web being a core pattern of Web 2.0. It looks like these sites are really failing in that they are not getting it together fast enough.
Maybe I will start one now. How should it work?
When you accept a friend request from any site, it also allows you the option to "federate" the declaration. This means that any other site can pick it up. Of course, this will require the sort of Sxip-ish OpenID infrastructure in place to make sure the identities match.
Entrepreneurs - please take this idea and run with it. If you feel really nice, give me some shares but please save us all time and effort by making this automated! Hey - if you really like it I'll be your friend on the system.
Showing posts with label design. Show all posts
Showing posts with label design. Show all posts
Thursday, November 01, 2007
Monday, April 02, 2007
Web 2.0 Architectural Patterns and Model Presentation
The slides from O'Reilly eTech are now available here. Feel free to poach and use at your leisure.
Synopsis:
There is no definition of Web 2.0 nor will there ever be a formal architecture. From Tim O'Reilly's example however, we can distill out patterns. If we take the list and compare Ofoto to Flickr, Akamai to BitTorrent, etc., the abstract patterns tell us what is going on for each example. These patterns can then be studied to build an abstract model for the Web 2.0. The abstract model in the presentations extends the basic client server model of the first internet generation to be able to facilitate the patterns of interaction people are building now. The new model extends the client to include "users" to enable patterns such as Participation-Collaboration and Collaborative Tagging. The lower part of the server sees SOA replacing the concept of a server given it encompasses an entire paradigm for software architecture and extends the concept into the enterprise (Capabilities) to fulfill other patterns like delivering a Rich User Experience or Software as a Service. The middle also encompasses some concepts that are important for developers and architects alike to consider such as consistent event and object models (necessary to build Mashups and the synchronized web patterns.
The first set of draft architectural and design patterns distilled from Tim's examples are listed below. Some of these are explained in the slide deck. The rest will be refined in a book I am working on with other authors.
Service Oriented Architecture
Software as a Service pattern (SaaS)
Participation-Collaboration Pattern
Asynchronous particle update (AJAX)
The Mashup Pattern
Rich User Experience
The Synchronized Web
Collaborative Tagging Systems (Folksonomy)
Declarative Living and Tag Gardening
Semantic Web Grounding Pattern
Persistent Rights Management
Adaptive Software
Fine grained content accessibility
Synopsis:
There is no definition of Web 2.0 nor will there ever be a formal architecture. From Tim O'Reilly's example however, we can distill out patterns. If we take the list and compare Ofoto to Flickr, Akamai to BitTorrent, etc., the abstract patterns tell us what is going on for each example. These patterns can then be studied to build an abstract model for the Web 2.0. The abstract model in the presentations extends the basic client server model of the first internet generation to be able to facilitate the patterns of interaction people are building now. The new model extends the client to include "users" to enable patterns such as Participation-Collaboration and Collaborative Tagging. The lower part of the server sees SOA replacing the concept of a server given it encompasses an entire paradigm for software architecture and extends the concept into the enterprise (Capabilities) to fulfill other patterns like delivering a Rich User Experience or Software as a Service. The middle also encompasses some concepts that are important for developers and architects alike to consider such as consistent event and object models (necessary to build Mashups and the synchronized web patterns.
The first set of draft architectural and design patterns distilled from Tim's examples are listed below. Some of these are explained in the slide deck. The rest will be refined in a book I am working on with other authors.
Service Oriented Architecture
Software as a Service pattern (SaaS)
Participation-Collaboration Pattern
Asynchronous particle update (AJAX)
The Mashup Pattern
Rich User Experience
The Synchronized Web
Collaborative Tagging Systems (Folksonomy)
Declarative Living and Tag Gardening
Semantic Web Grounding Pattern
Persistent Rights Management
Adaptive Software
Fine grained content accessibility
Subscribe to:
Posts (Atom)