From jferrai at us.ibm.com Tue Apr 1 09:38:27 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 1 Apr 2008 09:38:27 -0700 Subject: [OpenAjax] OpenAjax Call-to-Action to Ajax Developers for Browser Wishlist Message-ID: The OpenAjax Alliance is developing an Ajax industry wishlist for future browsers, using a dedicated wiki for this initiative ( http://www.openajax.org/runtime/wiki). The main purpose of the initiative is to inform the browser vendors about what future features are most important to the Ajax community and why. So far, the alliance has interviewed roughly a dozen industry leaders, including representatives from the ASP.NET AJAX, Dojo, Ext JS, Douglas Crockford of JSON fame, jQuery, Spry, and XAP, and recently held a townhall discussion on the feature request list among its members. The members have concluded that the wishlist (~25 items) is ready for public comments. The alliance is now issuing a call-to-action to Ajax developers to participate in this initiative, which is open to both OpenAjax Alliance members and to non-members. The alliance especially would like participation from Ajax toolkit developers and leading web developers with expertise in using open browser technologies to achieve rich user experiences. To join the effort, create a wiki login for yourself by following the instructions on the wiki home page (http://www.openajax.org/runtime/wiki). After you have a login, you can then add new feature requests or comment on existing feature requests as you see fit. The initiative operates on an honor-system basis. The moderators have attempted to make it possible that the community can add comments and vote on particular feature requests without large time commitments. For example, it is possible to simply vote for your favorite feature requests by adding a single row to a wiki table. The alliance?s wiki uses the same markup language as wikipedia. Here is the timeline: April - Phase I review, where participants not only add comments, but also are asked to identify their Top 5 features (i.e., those features that are most critical for inclusion in next-generation browsers). May - The moderators reorganize and possibly trim away feature requests for which little interest was shown. June - Phase II review, where participants will be asked to provide importance ratings for each of the feature requests on a scale of 0.0 to 5.0. July - The moderators will produce a summary report and notify the major browser vendors about the results. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080401/af38ffb6/attachment.html From jferrai at us.ibm.com Thu Apr 24 17:25:45 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Thu, 24 Apr 2008 17:25:45 -0700 Subject: [OpenAjax] Youtube video on OpenAjax Hub 1.1 Message-ID: IBM has created a short video on OpenAjax Hub 1.1 that was shown at a recent tradeshow. (BTW - I'm not sure which show.) The video doesn't go into much technical detail. Here is the link: Standard resolution: http://youtube.com/watch?v=v2aSfTwpZbM High resolution: http://youtube.com/watch?v=v2aSfTwpZbM&fmt=6 Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080424/146d0e3c/attachment.html From jferrai at us.ibm.com Fri May 30 06:37:55 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Fri, 30 May 2008 06:37:55 -0700 Subject: [OpenAjax] OpenAjax Alliance article in AJAXWorld: "Good News for AJAX" Message-ID: The online version of AJAXWorld magazine published our "Good News for AJAX" article on May 23: http://iphone.sys-con.com/read/547209.htm Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080530/07f5283b/attachment.html From jferrai at us.ibm.com Fri May 30 09:26:12 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Fri, 30 May 2008 09:26:12 -0700 Subject: [OpenAjax] Call for feedback on OpenAjax Conformance and OpenAjax Registry Message-ID: After more than a year of coordinated work across two committee (the Marketing WG and the Interoperability WG), we finally have completed formal review drafts of OpenAjax Conformance and OpenAjax Registry, and we are now soliciting public feedback on these two initiatives. The announcement appeared this morning in AJAZWorld online magazine: http://ajax.sys-con.com/read/579082.htm. Below is the text from the above announcement, which describes what we have announced and how to provide feedback. --------- Call for Feedback on OpenAjax Conformance and OpenAjax Registry The OpenAjax Alliance requests industry feedback on two companion initiatives, OpenAjax Conformance and the OpenAjax Registry By: Jon Ferraiolo May. 30, 2008 03:00 AM The OpenAjax Alliance is requesting industry feedback on two companion initiatives, OpenAjax Conformance and the OpenAjax Registry, which have been under development for the past year. The term OpenAjax Conformance is shorthand for the set of conformance requirements that OpenAjax Alliance places on Ajax technologies, products, and applications to promote interoperability. Version 1 of OpenAjax Conformance defines 10 specific conformance requirements on Ajax runtime libraries. An AJAX runtime library that meets these conformance requirements will allow Web developers to use that library conveniently within a given Web page with other OpenAjax Conformant libraries. OpenAjax Conformance provides the following benefits to IT managers and the AJAX developer community: * Seamless integration of multiple AJAX products and technologies within the same Web application, particularly with applications that use mashup techniques * Greater certainty about product choices, where OpenAjax Conformance plays a similar role in the AJAX community as the Good Housekeeping Seal does with consumer products * Lower training costs, lower development costs, and faster delivery of Web 2.0 innovations due to industry adoption of common approaches that build from OpenAjax standards * Interchangeability of OpenAjax Conformant products, such that customers can choose among multiple vendors (and change vendors in the future) OpenAjax Conformance defines three conformance levels. Full Conformance is for AJAX products that have sufficiently strong Ajax interoperability characteristics that there is high expectation that the given product can be used successfully and conveniently with other Ajax products as part of the same AJAX development task. Configurable Conformance is for AJAX products that support all of the same strong interoperability characteristics as for Full Conformance, except not in their default configuration. Limited Conformance is for products that meet a particular subset of the conformance criteria, and therefore have taken important steps towards AJAX industry interoperability, but on the question of whether the given AJAX product can interoperate successfully and conveniently with other Ajax products, the answer is "it depends". The OpenAjax Registry is a centralized, industry-wide AJAX registration authority managed by the Interoperability Working Group at OpenAjax Alliance. The Registry maintains an industry-wide list of AJAX runtime libraries and various characteristics of each library. For each library, the Registry lists: * JavaScript globals * runtime extensions (both JavaScript and DOM) * markup extensions (e.g., custom elements, attributes or CSS class names) These two technologies have now entered a public review phase that ends on June 30, 2008. Feedback can come in various forms, such as email to public at openajax.org, or comments posted on various industry blogs. After the public review phase ends, the members of OpenAjax Alliance will adjust the two specifications to take the feedback into account and then move the two specifications towards version 1.0 completion and approval. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080530/020e9ba3/attachment.html From Stian.Solberg at gaiaware.net Fri May 30 13:57:40 2008 From: Stian.Solberg at gaiaware.net (Stian Solberg) Date: Fri, 30 May 2008 22:57:40 +0200 Subject: [OpenAjax] Request for Open Ajax Registry Message-ID: <0B087783CCF6474FBB0943909A94F60C6CC958CCC7@apollo.gaiaware.net> Dear OpenAjax Alliance, we in Gaiaware would by this report the global namespace "Gaia". Gaia Ajax Widgets is a GPL licensed Ajax library for ASP.NET and Mono. Read more at: http://ajaxwidgets.com We are strongly interested in open standards, and want to support them with our product. Kind regards / Vennlig hilsen Stian Solberg Gaiaware as | http://ajaxwidgets.com stian.solberg at gaiaware.net | Tel +47 916 26 285 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080530/a631db02/attachment.html From petermichaux at gmail.com Sun Jun 1 10:10:55 2008 From: petermichaux at gmail.com (Peter Michaux) Date: Sun, 1 Jun 2008 10:10:55 -0700 Subject: [OpenAjax] OpenAjax feedback Message-ID: <3cbaf1c80806011010u7a45e62fq85a7c20115370828@mail.gmail.com> Hi, Is there a proper channel for feedback on the following page? Are the controlling parties willing to change the document or is it considered closed? http://www.openajax.org/whitepapers/Introducing%20Ajax%20and%20OpenAjax.php Peter From jferrai at us.ibm.com Sun Jun 1 11:14:47 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Sun, 1 Jun 2008 11:14:47 -0700 Subject: [OpenAjax] OpenAjax feedback In-Reply-To: <3cbaf1c80806011010u7a45e62fq85a7c20115370828@mail.gmail.com> Message-ID: Hi Peter, If there are problems with our white papers or they need to be updated becomes things have changed in the industry, the alliance would most likely do updates. What changes do you suggest? Thanks. Jon Ferraiolo "Peter Michaux" To Sent by: public at openajax.org public-bounces at op cc enajax.org Subject [OpenAjax] OpenAjax feedback 06/01/08 10:10 AM Hi, Is there a proper channel for feedback on the following page? Are the controlling parties willing to change the document or is it considered closed? http://www.openajax.org/whitepapers/Introducing%20Ajax%20and%20OpenAjax.php Peter _______________________________________________ public mailing list public at openajax.org http://openajax.org/mailman/listinfo/public -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080601/06362bcc/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080601/06362bcc/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: pic15245.gif Type: image/gif Size: 1255 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080601/06362bcc/attachment-0001.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080601/06362bcc/attachment-0002.gif From jferrai at us.ibm.com Mon Jun 2 07:13:05 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 2 Jun 2008 07:13:05 -0700 Subject: [OpenAjax] Request for Open Ajax Registry In-Reply-To: <0B087783CCF6474FBB0943909A94F60C6CC958CCC7@apollo.gaiaware.net> Message-ID: Hi Stian, I'm the chair of the Interoperability WG that manages the OpenAjax Registry. Thanks for the email. It seems almost certain that we will be able to reserve the "Gaia" global object for your toolkit. I can create the appropriate wiki page for the Gaia registry entries, but first I need some more information before we can start the approval process on the Gaia registry entry (per http://www.openajax.org/member/wiki/OpenAjax_Registry): * We need a URI that makes sense for XML namespaces (i.e., for the xmlns attribute in XML). Is "http://ajaxwidgets.com/" OK for that? Seems like a good choice to me. * What is the latest version number for your software? It looks like you are about to do a beta, so probably you are working on version "1.0". Is that right? * Do you have a URL that points to your root page for the specification for your library's APIs? * Does Gaia make use of any Gaia-specific attributes or elements within HTML or any Gaia-specific CSS class names? Have you considered joining OpenAjax Alliance? There are no fees. The only requirements are to sign and send the Members Agreement and send an email with a few bits of information. Instructions for joining are at: http://www.openajax.org/join.php. Thanks. Jon Ferraiolo Stian Solberg To Sent by: "public at openajax.org" public-bounces at op enajax.org cc Thomas Hansen 05/30/08 01:57 PM Subject [OpenAjax] Request for Open Ajax Registry Dear OpenAjax Alliance, we in Gaiaware would by this report the global namespace ?Gaia?.. Gaia Ajax Widgets is a GPL licensed Ajax library for ASP.NET and Mono. Read more at: http://ajaxwidgets.com. We are strongly interested in open standards, and want to support them with our product. Kind regards / Vennlig hilsen Stian Solberg Gaiaware as | http://ajaxwidgets.com. stian.solberg at gaiaware.net | Tel +47 916 26 285 _______________________________________________ public mailing list public at openajax.org http://openajax.org/mailman/listinfo/public -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080602/c81cba92/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080602/c81cba92/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: pic17096.gif Type: image/gif Size: 1255 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080602/c81cba92/attachment-0001.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080602/c81cba92/attachment-0002.gif From petermichaux at gmail.com Mon Jun 2 08:24:43 2008 From: petermichaux at gmail.com (Peter Michaux) Date: Mon, 2 Jun 2008 08:24:43 -0700 Subject: [OpenAjax] OpenAjax feedback In-Reply-To: References: <3cbaf1c80806011010u7a45e62fq85a7c20115370828@mail.gmail.com> Message-ID: <3cbaf1c80806020824t4653602bn46e064b268b1cf01@mail.gmail.com> Hi Jon, On Sun, Jun 1, 2008 at 11:14 AM, Jon Ferraiolo wrote: > If there are problems with our white papers or they need to be updated > becomes things have changed in the industry, the alliance would most likely > do updates. > > What changes do you suggest? My primary concern is the section defining "Ajax" http://www.openajax.org/whitepapers/Introducing%20Ajax%20and%20OpenAjax.php#What_is_Ajax In the community, there is a very casual use of the term Ajax currently that unfortunately means "browser scripting". In a whitepaper section that is defining the term, I believe it should correctly focus on the definition that Ajax is about communication and not DHTML. For example the whitepaper says > Ajax techniques therefore represent the continued evolution of > DHTML to deliver Rich Internet Applications (RIAs) and the > Web 2.0 experience. Ajax is not the evolution of DHTML. Ajax is a separate technology which when used in combination with DHTML delivers RIAs and the Web 2.0 experience. This general confusion is in other places in the white paper also. Ajax and DHTML are a powerful combination but they do not need to be used together and frequently are not. Peter From jferrai at us.ibm.com Mon Jun 2 09:18:04 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 2 Jun 2008 09:18:04 -0700 Subject: [OpenAjax] OpenAjax feedback In-Reply-To: <3cbaf1c80806020824t4653602bn46e064b268b1cf01@mail.gmail.com> Message-ID: Hi Peter, There has been lots of discussion about terminology since OpenAjax Alliance was formed last year, and one of the first things we discussed was whether "Ajax" had a narrow meaning which described the "AJAX" technique of asynchronous communication in the background between client and server using XMLHttpRequest or the broader meaning where "Ajax" means rich user experiences in the browser. The members of OpenAjax Alliance concluded that we would should define term Ajax to have the broader meaning, where "Ajax" means rich user interfaces in the browser. We made this terminology decision back in the summer of 2006 and published our first white paper with our current definition of Ajax in September 2006 when our Web site first went live. There was much discussion and formal voting among the member organizations on all of this prior to posting that white paper. After we published our white paper, we received key reinforcement from the editors of Ajaxian.com, Dion Almaer and Ben Galbraith. Their keynote at one of the Ajax Experience in the early 2007 timeframe was mostly about what the term "Ajax" meant. They had two key slides. One slide said something to the effect that "Ajax != AJAX", which means that "Ajax" (with lower case) is more than just what was defined by the original acronym (which focused on XMLHttpRequest). Their big conclusion slide then said "Ajax == DHTML", in clear acknowledgement that the term Ajax had transformed from its narrow definition into the broader definition that is more in line with the meaning of DHTML. Anyway, that's the background on why we define "Ajax" in a broad manner. Jon "Peter Michaux" To Jon Ferraiolo/Menlo Park/IBM at IBMUS 06/02/08 08:24 AM cc public at openajax.org Subject Re: [OpenAjax] OpenAjax feedback Hi Jon, On Sun, Jun 1, 2008 at 11:14 AM, Jon Ferraiolo wrote: > If there are problems with our white papers or they need to be updated > becomes things have changed in the industry, the alliance would most likely > do updates. > > What changes do you suggest? My primary concern is the section defining "Ajax" http://www.openajax.org/whitepapers/Introducing%20Ajax%20and%20OpenAjax.php#What_is_Ajax In the community, there is a very casual use of the term Ajax currently that unfortunately means "browser scripting". In a whitepaper section that is defining the term, I believe it should correctly focus on the definition that Ajax is about communication and not DHTML. For example the whitepaper says > Ajax techniques therefore represent the continued evolution of > DHTML to deliver Rich Internet Applications (RIAs) and the > Web 2.0 experience. Ajax is not the evolution of DHTML. Ajax is a separate technology which when used in combination with DHTML delivers RIAs and the Web 2.0 experience. This general confusion is in other places in the white paper also. Ajax and DHTML are a powerful combination but they do not need to be used together and frequently are not. Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080602/5b1becc6/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: graycol.gif Type: image/gif Size: 105 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080602/5b1becc6/attachment-0003.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: pic14943.gif Type: image/gif Size: 1255 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080602/5b1becc6/attachment-0004.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: ecblank.gif Type: image/gif Size: 45 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080602/5b1becc6/attachment-0005.gif From jferrai at us.ibm.com Mon Jun 9 10:06:49 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 9 Jun 2008 10:06:49 -0700 Subject: [OpenAjax] Ajaxian and AJAXWorld articles announcing new white papers Message-ID: FYI - Last week, Ajaxian and AJAXWorld published announcements about our two new white papers: * Ajaxian: http://ajaxian.com/archives/openajax-alliance-white-papers-on-mobile-ajax-and-recent-browser-advances * AJAXWorld: http://openwebdeveloper.sys-con.com/read/582662.htm The Mobile Ajax white paper was the result of several months of collaboration and hard work among several companies within the Mobile Task Force and represents an extensive assessment of the current state of the affairs regarding Mobile Ajax application development and contains a comprehensive set of developer tips for success with Mobile Ajax. The Good News for Ajax white paper is simply posting as a white paper the same article that was published in AJAXWorld in March. Here are links to the two white papers: * http://www.openajax.org/whitepapers/Introduction%20to%20Mobile%20Ajax%20for%20Developers.php * http://www.openajax.org/whitepapers/Good%20News%20for%20Ajax%20-%20Browser%20Wars%20Are%20Back.php Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080609/b450abca/attachment.html From jferrai at us.ibm.com Thu Jun 12 11:35:03 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Thu, 12 Jun 2008 11:35:03 -0700 Subject: [OpenAjax] Final voting phase on OpenAjax Browser Wishlist Message-ID: The OpenAjax Alliance is developing an Ajax industry wishlist for future browsers, using a dedicated wiki [1]. The feature list now lists 37 separate feature requests [2], covering a wide range of technology areas, such as security, Comet, multimedia, CSS, interactivity, and performance. The goal is to inform the browser vendors about what the Ajax developer community feels are most important for the next round of browsers (i.e., FF4, IE9, Safari4, and Opera10) and to provide supplemental details relative to the feature requests. The initiative is now in its final voting phase, and the alliance is issuing a call-to-action to Ajax developers to vote on which features should have the highest priority. To make the voting process as quick and painless as possible, the voting page lists all 37 feature requests, along with a popup menu for each feature with possible values of 0 (no importance) to 10 (highest importance). The voting period ends on July 10, 2008. To vote, you will need a wiki login (as explained on the wiki home page [1]) and then cast your votes on the Phase II Voting wiki page [3]. The alliance also strongly encourages people to comment on the wiki pages for each of the existing features and to add any important new features that are not yet on the list. The initiative is open to both OpenAjax Alliance members and to non-members. The alliance especially would like participation from Ajax toolkit developers and leading web developers with expertise in using open browser technologies to achieve rich user experiences. The initiative operates on an honor-system basis. [1] http://www.openajax.org/runtime/wiki [2] http://www.openajax.org/runtime/wiki/Feature_Requests_Summary_Page [3] http://www.openajax.org/runtime/wiki/Phase_II_Voting -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080612/0ede8a4e/attachment.html