Thursday, June 1st, 2006

Open Ajax Alliance Update

Category: Ajax, Editorial

I had the pleasure of being part of the first Open Ajax Alliance summit, brought together by IBM, hosted at Adobe in San Francisco.

The first day was all about getting on the same page, as the members went around and discusses their worlds, and where they see the Open Ajax alliance moving. It was interesting to see vendors (commercial and open source) from so many parts of the development world come together here. We had Java tools vendors, server framework vendors, browser vendors, mobile companies, and many more. One of the great features of “Ajax” is that it is so fluffy, that all platforms can join in :)

On the second day work began to work out which subcommitees should be formed, and we ended up with:

  • Interoperability subcommittee
  • Declarative Markup subcommittee
  • Marketing subcommittee

I am most interested in what comes out of the interoperability piece. If we could use various code and widgets from multiple toolkits, that would be a win (TIBCO has announced that they do this now).

One of the issues that I see is packaging. The nature of JavaScript on the web is that browsers need to download code to run. If we could have a versioned system that was built into browsers and grokked JSAN so I could say <script version=”1.3″ uuid=”dojo/kitchensink” /> that would be great. Not only would it mean that in general we wouldn’t have to keep downloading the same files a million times, but it would enable us to have more fine-grained libraries. For example, if we could agree on the $ function we could put it up on JSAN and the other frameworks could just declare dependencies (so dojo/kitchensink could have metadata that says “oh, I need you to download x, y, z too” and it just happens).

Anyway, end of my sporadic opinion… the open ajax alliance knows that there are many things to work on (from low level to tooling to platform independent issues [e.g. Java vs. .NET vs. …] to …) so the challenge will be finding the low hanging fruit and going after that first. If there is anything that you would like to see let us know!

Posted by Dion Almaer at 11:53 am
7 Comments

++++-
4 rating from 30 votes

7 Comments »

Comments feed TrackBack URI

Your article is broken (when viewed in IE) at text:
(…)If we could have a versioned system that was built into browsers and grokked JSAN so I could say <script version=”1.3″ uuid=”dojo/kitchensink” /> that would be great. (…)
Please escape where necessary!

Comment by Krzysztof — June 1, 2006

Broken in FFX and Opera too…

Comment by geoff2k — June 1, 2006

Missing text:

One of the issues that I see is packaging. The nature of JavaScript on the web is that browsers need to download code to run. If we could have a versioned system that was built into browsers and grokked JSAN so I could say <script version=”1.3″ uuid=”dojo/kitchensink” /> that would be great. Not only would it mean that in general we wouldn’t have to keep downloading the same files a million times, but it would enable us to have more fine-grained libraries. For example, if we could agree on the $ function we could put it up on JSAN and the other frameworks could just declare dependencies (so dojo/kitchensink could have metadata that says “oh, I need you to download x, y, z too” and it just happens).

Anyway, end of my sporadic opinion… the open ajax alliance knows that there are many things to work on (from low level to tooling to platform independent issues [e.g. Java vs. .NET vs. …] to …) so the challenge will be finding the low hanging fruit and going after that first. If there is anything that you would like to see let us know!

Comment by geoff2k — June 1, 2006

When will there be a centralized portal for information regading the aliance work? It seems that information about the project is scattered amungst the member sites.

Comment by Ryan Olsen — June 1, 2006

Oh boy, that committee work is too slow! Meanwhile, in Mountain View, a large company is reshaping the Ajax world on their own…

Mats

Comment by Mats Henricson — June 1, 2006

Great ideas, its about time, even when design by committee is slow. “if we could agree on the $ function we could put it up on…” in not as big an issues as the real $ that often supercede efforts by committees.

Comment by Les Papier — June 3, 2006

[…] Hopefully, organizations like the new OpenAjax Alliance will be able to reach consensus on what needs to be done and how in order to take us to the next level in Rich Internet Application evolution. […]

Pingback by brentashley » Blog Archive » Ajax transports still need to evolve — June 7, 2006

Leave a comment

You must be logged in to post a comment.