InsideRIA has just launched! My good friend Andre Charland (Nitobi) is the lead blogger.
It’s a gathering place for thought leaders in the RIA field. (See http://www.insideria.com/experts.html ). The site will be an ongoing conversation about RIA technologies including Flex, AIR, and AJAX – the experts will be continually posting their opinions, cool findings, and technical information to the site. The other leader of the site, another good friend Rich Tretola (Everything Flex and Community Manager/Editor), is an expert in his field.
These guys are off to a good start! Please take a visit.
Showing posts with label oreilly. Show all posts
Showing posts with label oreilly. Show all posts
Monday, January 21, 2008
Monday, November 05, 2007
Web 2.0 Berlin: Day One!
Heute ist eine andere gutes TAG! Hier habe ich Tim Oreilly im Hauptkonferenzplatz getroffen! Tim bereitet seinen Hauptgededanken vor (auf einem Mac) wie ich diesen blog Pfosten schreibe.
Duane Nickull and Tim O'Reilly in Berlin today.
While I have been here for a week or so, today is the first day of real excitement. I had the luxury of sitting down with a very brilliant television crew (HdM Stuttgart | www.web2null-derfilm.de) crew to discuss some of the finer points of Web 2.0 from a European perspective. One of the questions was about how the Web 2.0 market in Germany might differ from the Web 2.0 market in the USA. I really have to respond that the very question itself is not correct. There is now a global marketplace and things that can affect people in one place are really affecting us all. The illusion that we are different is a relic of the non-digital age and the new electronic democracy can affect an entire generation, country, or multiple countries and generations with the same speed. Honestly, I think this may be one of the finest inteviews I have ever had the pleasure of doing. The questions were right on target and it really made me aware of some key questions from a European perspective. It seems, like in many other places, there is a real pragmatic struggle to understand *exactly* WHAT Web 2.0 is. Once again, I think the book Web 2.0 Design Patterns (co-authored with Dion Hinchcliffe and James Governor) is a good starting point, yet this book will leave readers with just as many questions as answers. I found myself digging up several of the core Web 2.0 patterns several times during the interview and keep realizing that it is hard to describe something when you abstract the implementation away from the facts. Nevertheless, the book really does this.
And speaking of Dion, he is downstairs at his finest delivering his Web 2.0 University talk to an eager and packed audience. This is a great conference! Looking forward to some good German beer next!
Duane Nickull and Tim O'Reilly in Berlin today.While I have been here for a week or so, today is the first day of real excitement. I had the luxury of sitting down with a very brilliant television crew (HdM Stuttgart | www.web2null-derfilm.de) crew to discuss some of the finer points of Web 2.0 from a European perspective. One of the questions was about how the Web 2.0 market in Germany might differ from the Web 2.0 market in the USA. I really have to respond that the very question itself is not correct. There is now a global marketplace and things that can affect people in one place are really affecting us all. The illusion that we are different is a relic of the non-digital age and the new electronic democracy can affect an entire generation, country, or multiple countries and generations with the same speed. Honestly, I think this may be one of the finest inteviews I have ever had the pleasure of doing. The questions were right on target and it really made me aware of some key questions from a European perspective. It seems, like in many other places, there is a real pragmatic struggle to understand *exactly* WHAT Web 2.0 is. Once again, I think the book Web 2.0 Design Patterns (co-authored with Dion Hinchcliffe and James Governor) is a good starting point, yet this book will leave readers with just as many questions as answers. I found myself digging up several of the core Web 2.0 patterns several times during the interview and keep realizing that it is hard to describe something when you abstract the implementation away from the facts. Nevertheless, the book really does this.
And speaking of Dion, he is downstairs at his finest delivering his Web 2.0 University talk to an eager and packed audience. This is a great conference! Looking forward to some good German beer next!
Thursday, November 01, 2007
C'mon Web 2.0 - get it together now!!!
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.
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.
Thursday, October 25, 2007
Anne Thomas Manes on Web 2.0
I am usually not a big fan of a lot of Web 2.0 statements however today I am sitting in the Burton Catalyst conference in Barcelona and am listening to Anne Thomas Manes describe the core tenets of Web 2.0. Anne is one of the strongest analysts in terms of technical skills and has the unique distinction of actually having written many of the standards and technologies for SOA and web services as opposed to merely studying them. Here is Anne on stage:
Anne has noted, as we wrote in the O'Reilly Web 2.0 Design Patterns book, that a pragmatic analysis of Web 2.0 will help people really understand what is going on. She also noted that things many people think ARE Web 2.0 (such as Rich Internet Applications, SOA, Mashups, and SaaS) are in fact only technologies or specific design patterns. Web 2.0 is an attitude and also a social movement towards the new model whereby users are a core part of the interaction (and architecture to some degree). The client-server model has truly evolved into a new model for Web 2.0 as shown here.
Anne noted that the process of engagement is also core. The old web was a web of searching and browsing whereas Web 2.0 is about participating. Tim O'Reilly's quote is perhaps the best here and by a strange coincidence, both Anne and I used it. Tim stated:
“Don't treat software as an artifact, but as a process of engagement with your users."
Both Anne and fellow Burtonite Chris Haddad also noted that Enterprise 2.0 is really an adoption of the core patterns of Web 2.0 by enterprises. In my opinion, this has accelerated greatly in the last eight weeks as large companies are struggling to adopt the whole Web 2.0 phenomenon.
I am looking forward to more on Web 2.0 from Burton.
Anne has noted, as we wrote in the O'Reilly Web 2.0 Design Patterns book, that a pragmatic analysis of Web 2.0 will help people really understand what is going on. She also noted that things many people think ARE Web 2.0 (such as Rich Internet Applications, SOA, Mashups, and SaaS) are in fact only technologies or specific design patterns. Web 2.0 is an attitude and also a social movement towards the new model whereby users are a core part of the interaction (and architecture to some degree). The client-server model has truly evolved into a new model for Web 2.0 as shown here.
Anne noted that the process of engagement is also core. The old web was a web of searching and browsing whereas Web 2.0 is about participating. Tim O'Reilly's quote is perhaps the best here and by a strange coincidence, both Anne and I used it. Tim stated:
“Don't treat software as an artifact, but as a process of engagement with your users."
Both Anne and fellow Burtonite Chris Haddad also noted that Enterprise 2.0 is really an adoption of the core patterns of Web 2.0 by enterprises. In my opinion, this has accelerated greatly in the last eight weeks as large companies are struggling to adopt the whole Web 2.0 phenomenon.
I am looking forward to more on Web 2.0 from Burton.
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)