From jferrai at us.ibm.com Tue Jul 8 11:45:34 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 8 Jul 2008 11:45:34 -0700 Subject: [OpenAjax] FINAL REMINDER on browser wishlist Message-ID: This is the last week for voting on the OpenAjax browser wishlist initiative. To vote: 1) You need to create a wiki login for yourself. Instructions are at: * http://www.openajax.org/runtime/wiki 2) After logging in to the runtime wiki, go to the following page to cast your votes:: * http://www.openajax.org/runtime/wiki/Phase_II_Voting Vote casting is simple: just pick a number from 0-10 for each feature using a popup menu. The voting page uses Ajax behind the scenes to talk to a server which logs the votes. This initiative was an experiment to see if we could help get the Ajax community to come together to identify their feelings about highest priority features in future browsers. From my perspective, the initiative has exceeded even the wildest expectations, both in terms of the quantity and quality of the feature requests and the level of community participation. Here are some statistics: * 54 separate features have been described on the wiki * 181 people have created wiki logins for themselves * 101 people have cast votes on their favorite features The list of features and a listing of all votes that have been cast to date can be found at the following two pages: * http://www.openajax.org/runtime/wiki/Feature_Requests_Summary_Page * http://www.openajax.org/runtime/wiki/Phase_II_Voting_Details Here is one of the press articles on the wishlist initiative: * http://arstechnica.com/news.ars/post/20080701-four-things-that-need-fixing-to-secure-the-future-of-the-web.html At this point, although we shouldn't take the voting too seriously nor too literally, the features receiving the most votes are (in order): * 2D Drawing/Vector Graphics * Better Security for Cross-site Scripts * HTML DOM Operation Performance in General * Better APIs about positioning and styling * The Two HTTP Connection Limit Issue * Video and Audio * Better UI Layout Support Next week, Coach Wei will start to work on a summary report which we will deliver to the browser teams. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080708/d0b3576a/attachment.html From jferrai at us.ibm.com Mon Jul 14 10:34:06 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Mon, 14 Jul 2008 10:34:06 -0700 Subject: [OpenAjax] Browser wishlist Phase II Voting is now closed Message-ID: Hi everyone, The Phase II Voting phase for our browser wishlist initiative is now completed and the Phase II voting page has been deactivated. Coach Wei and I will start work soon on the summary report. In my mind, this initiative has turned out to be a bigger success than I had ever hoped. This was all just an experiment to see if he could get amount of community participation without too much effort (e.g., post a new wiki, add a couple of simple wiki extensions). I was hoping that we would get around 50 people voting, which I though would be sufficient in order to establish a rough idea of what's most important to the community, but we went well beyond that level. Here are some quick statistics: #Participants: 222 (i.e., the number of people who created wiki logins for themselves) #Voters: 143 (i.e., the number of people who cast Phase II votes) #Features: 55 (i.e., the number of features written up on their own wiki pages) If you want to look at the raw results, go to these pages: * http://www.openajax.org/runtime/wiki/Feature_Requests_Summary_Page * http://www.openajax.org/runtime/wiki/Phase_II_Voting_Details Sometime soon I'll post a new wiki page (or two) that provides various views into the voting results, such as a table that shows the feature in sorted order, with the highest vote-getting feature at the top. Once the summary report is completed, Coach and I will present the information to the browser teams. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080714/7ba9d740/attachment.html From jferrai at us.ibm.com Wed Jul 16 11:34:05 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Wed, 16 Jul 2008 11:34:05 -0700 Subject: [OpenAjax] Browser wishlist initiative summary report is now available Message-ID: We have produced a summary report from our browser wishlist initiative that you can find at: * http://www.openajax.org/runtime/wiki/Summary_Report By July 13, when the voting closed, this initiative has turned out to be a bigger success than expected. Given the amount of effort required to read and understand the vast web technology landscape, and the relatively limited time and resources available to the OpenAjax Alliance Runtime participants, we were hoping for 50 or so people to vote, which would be meaningful to establish a rough idea of what's most important to the community. Voting results are available at: * http://www.openajax.org/runtime/wiki/Feature_Requests_Summary_Page * http://www.openajax.org/runtime/wiki/Phase_II_Voting_Summary * http://www.openajax.org/runtime/wiki/Phase_II_Voting_Details Here are some quick statistics: * 222 people participants; * 143 people voted; * 55 feature request being written up; * Various industry leaders contributed; * A discussion thread spawns on Slashdot with 628 comments ( http://tech.slashdot.org/article.pl? sid=08/06/30/1845201). Among all the feature requests, 2D Drawing/Vector Graphics is clearly the most desired feature by the community. It received most votes (110 people voted for it), and highest total score (842, over 10% higher than the second feature request). The second top feature request is enhanced security for cross-site scripts. The third and fourth were better APIs for scripting and styling and HTML DOM performance. Here are the top 10 features (followed by #votes*avgvote, #votes, avgvote): * 2D Drawing/Vector Graphics 842 110 7.65 * Better Security for Cross-site Scripts 759 102 7.44 * Better APIs about positioning and styling 748 99 7.56 * HTML DOM Operation Performance In General 742 92 8.07 * Better Support for Rich Text Editing 693 102 6.79 * The Two HTTP Connection Limit Issue 690 98 7.04 * Better UI Layout Support 689 96 7.18 * Native JSON Parsing 688 107 6.43 * Persistent Connections Issue 649 95 6.83 * Video and Audio 639 99 6.46 Coach and I summarized as follows the top requests as follows: * Graphics - The top vote getter was 2D Drawing/Vector Graphics. Ajax developers today are achieving astoundingly rich graphics effects through clever techniques leveraging JavaScript, CSS, images, and whatever vector graphics features they can find (usually, SVG, VML and Canvas), but browser differences are a major pain point among Ajax developers. Mozilla, WebKit and Opera support both Canvas and SVG with good interoperability (although Mozilla does not yet support SVG animations). IE is the holdout. The call-to-action is for all browsers, particularly IE, to support both of the industry standards for 2D vector graphics, SVG (the DOM-based standard) and Canvas (the procedural-based standard). * Security - Web security is an important topic for leading Ajax developers. The second top vote getter was Better Security for Cross-Site Scripts (XSS), but other security requests also receiving high votes, such as Strong Cross-Site Request Forgery Protection (which it turns out was the 11th top voter-getter). The perception of the moderators is that it?s not just XSS, but that the community cares about all aspects of ensuring that the Web is secure, and in fact more secure than it is today. Recently, Mozilla has authored a proposal that might help make the Web more secure: http://people.mozilla.com/~bsterne/site-security-policy/. Note that Native JSON Parsing can be considered a security feature because without it Web developers are more inclined to use JavaScript eval() to process JSON data, which might allow for XSS attacks. * Better low-level CSS and DOM support for layout - Two of the top vote-getters were Better APIs for positioning and styling and Better UI Layout Support. These requests come from the widget developers within Ajax toolkit projects who design Ajax-based UI controls by taking advantage of what the browser gives them, such as DOM, CSS, images, and table layout. They often run into walls, and their jobs could be much easier (and performance much faster) if the browser included a small number of additional (relatively small) features, such as stretchable layout (e.g., flexbox in XUL) and the ability to determine the location and size of objects (and containers) within the page. * Performance - The top vote-getter in the performance area was HTML DOM Performance in General. In discussions over the past year with leading Ajax developers, the moderators believe that the Ajax community wants performance improvements in all aspects of the browser runtime, including DOM, JavaScript, and rendering, but DOM performance was singled out by the community because Ajax toolkit developers have found that DOM access is the top performance barrier today. The key high-level message is keep making the browsers faster, but even blazingly fast JavaScript isn?t going to help if making DOM calls is too slow. * Rich text editing - Various people in the Ajax community want to move desktop-like document editing into the browser. However, the contributors to this feature request did not outline a detailed strategy for how to accomplish this in future browser. The takeaway is that the Ajax community wants Better Support for Rich Text Editing , and hopefully one of the browser teams will push the envelope in this direction and send standards proposals so that the other browsers can also provide this functionality. * Comet (server push) - Two of the top vote-getters were The Two HTTP Connection Limit Issue and Persistent Connections Issue. The underlying requirement is that many Ajax applications, such as dashboards, require an efficient and robust mechanism for having the server send data to the client on an event-driven basis. Today, server push in Ajax is often accomplished using ?Comet? techniques such as long-lived HTTP connections, but the Ajax community would prefer if server push was a native browser feature. * Video and Audio - Video and Audio also receiving strong support, coming in as the 10th-most requested feature. The next step is to communicate with browser vendors. We have had calls with some of the browser vendors such as Microsoft IE team during Phase I. OpenAjax Alliance will try to get in touch (or continue) the dialog with browser vendors to convey what the community is looking for. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080716/a023b8ed/attachment.html From ricjohnsoniii at gmail.com Mon Jul 21 13:24:16 2008 From: ricjohnsoniii at gmail.com (Ric Johnson) Date: Mon, 21 Jul 2008 16:24:16 -0400 Subject: [OpenAjax] Cross browser testing Message-ID: I am having a problem testing one of my web applications. Would please be able to recommend any automated tools you may know to verify cross-browser scripts, styles, and security? We can not change our back end, so simply choosing a backend script library will not work. Thank you, Ric Johnson From jferrai at us.ibm.com Fri Aug 22 16:53:31 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Fri, 22 Aug 2008 16:53:31 -0700 Subject: [OpenAjax] Announcing the 2008 InteropFest for IDEs and Mashups Message-ID: This announcement can also be found on the Web with nice formatting at: http://www.openajax.org/blog/?page_id=62 ----------------------------------------- OpenAjax Alliance is pleased to announce the start of this year?s interoperability event, the 2008 InteropFest for IDEs and Mashups. The 2008 InteropFest continues until just before AJAXWorld West 2008 (i.e., until just before October 20, 2008). The 2008 InteropFest focuses on two main areas: Ajax IDEs and secure mashups. InteropFest Focus #1: Ajax IDEs Today, Ajax tooling falls short of potential, in large part due to interoperability problems. There are a number of Ajax IDEs today and hundreds of Ajax libraries, but only a small fraction of IDEs work well with only a small fraction of Ajax libraries, usually due to one-off coordination between particular Ajax libraries and particular IDEs. To promote strong plug-and-play between Ajax IDEs and Ajax libraries, OpenAjax Alliance has developed an industry standard called ?OpenAjax Metadata? ( http://www.openajax.org/member/wiki/OpenAjax_Metadata_Specification), which defines an industry standard XML grammar for the following:, JavaScript APIs - Descriptive information about the namespaces, classes, methods, parameters, properties, etc. found in JavaScript libraries. This API metadata can be used by Ajax IDEs to deliver content-assist features and interactive help. Widgets - XML metadata, along with wrapper HTML and JavaScript, for the UI controls found in many Ajax libraries. This widget metadata can be used by Ajax IDEs to populate widget palettes and to allow visual layout of Ajax applications. InteropFest Focus #2: Secure Mashups OpenAjax Alliance is working on multiple related technology efforts in order to help realize the potential of mashup technologies to enable user-generated situational applications, where applications are assembled by end users by dragging various widgets onto a canvas and connecting widgets together. The two main inhibitors to widespread deployment of mashups are security issues and interoperability challenges: Mashup security: OpenAjax Alliance is addressing security primarily through the secure mashup runtime environment found within OpenAjax Hub 1.1. Widget interoperability: The alliance is addressing widget interoperability primarily through its widget metadata standards found within OpenAjax Metadata (see the related discussion of widgets in the discussion about IDEs) The OpenAjax Hub 1.1 is the key technology piece for addessing mashup security issues. OpenAjax Metadata for Widgets is the key technology piece for addressing the widget interoperability challenges. What We Have Built At OpenAjax Alliance So Far We have built a significant amount of technology in advance of the 2008 InteropFest: For OpenAjax Hub 1.1, we have: Draft specification for OpenAjax Hub 1.1 Open source reference implementation for Hub 1.1 that matches the draft specification. (Source code for Hub 1.1 is available at the OpenAjax Alliance open source site) Open source Sample Mashup Application that uses OpenAjax Hub 1.1 for loading and initializing widgets into isolated sandboxes (using IFRAMEs usually) and that provides a secure pub/sub engine for passing messages between the widgets through a secure and mediated message bug. (Source code for Sample Mashup Application is available at the OpenAjax Alliance open source site) For OpenAjax Metadata, we have: Draft specification for OpenAjax Metadata, which was developed in the IDE Working Group, where the leading contributors have included the following companies/products: Adobe Dreamweaver & Spry Toolkit, Aptana Studio (Eclipse-based), Eclipse ATF, Eclipse JSDT, Microsoft Visual Studio and ASP.NET AJAX, OpenLink Software, and TIBCO General Interface Open source Sample Mashup Application that serves as a reference implementation for OpenAjax Metadata and implements most of the mashup-related features in OpenAjax Metadata An XML validator for OpenAjax Metadata in the form of a ?Validator? widget within the Sample Mashup Application Open source extension to JSDoc Toolkit that can generate OpenAjax Metadata for JavaScript APIs out of any JavaScript file that uses JSDoc inline comments. (Source code for the JSDoc to OpenAjax Metadata converter is available at the OpenAjax Alliance open source site) As preparation for the 2008 InteropFest, we have set up the following: The main wiki page for the 2008 InteropFest, which describes how to participate and includes sections where participants can list their contributions. The Sample Mashup Application, which will be the centerpiece for many of the activities associated with the 2008 InteropFest How to Participate in the 2008 InteropFest The following sections explain how different classes of developers can participate in the 2008 InteropFest and how they can work with the Sample Mashup Application. Subsequent sections provide some additional information about the 2008 InteropFest. JavaScript library developers JavaScript library developers (or other developers with access to the JavaScript library source code) are strongly encouraged to generate OpenAjax Metadata files that define the JavaScript APIs and widgets that are included in their library and then use the Validator widget within the Sample Mashup Application to validate their OpenAjax Metadata files. To explain in more depth: OpenAjax Metadata for JavaScript APIs - By providing OpenAjax Metadata for your library?s JavaScript APIs, you will enable developers you use your library to take advantage of Ajax IDEs that offer intelligent code assist and context-sensitive help. OpenAjax Metadata for Widgets - By providing OpenAjax Metadata for your library?s widgets, you will enable your developers to take advantage of visual Web application design (e.g., drag and drop onto a canvas) in selected Ajax IDEs and you will have made your widgets ?mashable? in that they will be ready for use within mashup editors such as the Sample Mashup Application. The Sample Mashup Application includes a ?Validator? widget that allows you to upload your OpenAjax Metadatata files (either in the form of a single XML file or a ZIP package) and validate your XML file(s) against the OpenAjax Metadata language schema. Library widgets that have corresponding OpenAjax Metadata files can also be uploaded to the Sample Mashup Application?s repository, which will cause the widget to appear in the Sample Mashup Application?s list of widgets, and therefore can be included within a mashup. A JavaScript library can claim to be a successful participant in the 2008 InteropFest by producing OpenAjax Metadata files for a subset of their features where those file validate successfully against the language schema. Web Widget developers (For the purposes of this discussion, a ?Web Widget?, aka Gadget, is a standalone Web component that can be embedded into other applications. One of the leading formats in the industry for Web Widgets today is Google Gadgets.) Web Widget developers are strongly encouraged to create an OpenAjax Metadata file for their Web Widget, then use the Validator widgets within the Sample Mashup Application to validate their XML, and if possible upload the file to the repository so that it can be included within user-created mashups. A Web Widget developer can claim to be a successful participant in the 2008 InteropFest by producing an OpenAjax Metadata file for their widget where the file validates successfully against the language schema. IDE developers IDE developers should add support for both aspects of OpenAjax Metadata to their products: OpenAjax Metadata for JavaScript APIs - This will allow your IDE to provide intelligent code assist and context-sensitive help for arbitrary JavaScript libraries. OpenAjax Metadata for Widgets - This will allow your IDE to support rich visual editing with widgets from arbitrary Ajax libraries. An IDE can claim to be a successful participant in the 2008 InteropFest by consuming OpenAjax Metadata files and demonstrating user interface features that reflect the information from the OpenAjax Metadata files. Mashup editor developers Mashup editor developers should add support for OpenAjax Metadata for Widgets and OpenAjax Hub 1.1 to their products. This will enable your mashup editor to support the industry standard for Web Widgets and support the secure mashup runtime framework provided by OpenAjax Hub 1.1. A mashup editor can claim to be a successful participant in the 2008 InteropFest by consuming OpenAjax Metadata files for widgets and/or including support for OpenAjax Hub 1.1. Users Users who are interested in learning more about user-designed mashups (i.e., where applications are assembled without programming), or are interested in learning more about ?secure mashups?, can play with the mashup editor to add widgets to the canvas and link the widgets so that data can be passed from one widget to another, all within the context of the security management features that are included in the Sample Mashup Application (due to OpenAjax Hub 1.1 being used under the hood). (Note: Need to build widgets and demos that showcase the security features.) For more information For more information about the 2008 InteropFest: If you are a member, you can send questions and comments as follows: Discussion on Hub 1.1 occurs on the Interoperability WG mailing list at interop at openajax.org Discussion about OpenAjax Metadata occurs on the IDE WG mailing list at ide at openajax.org (for things related to IDE workflows) and the Gadgets TF mailing list at gadgets at openajax.org (for things related to mashups and Web Widgets) If you are not a member of OpenAjax Alliance, please send questions and comments to public at openajax.org. Also, feel free to send questions and comments individually to Jon Ferraiolo (jferrai at us.ibm.com), who manages operations at OpenAjax Alliance. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080822/67ac384a/attachment-0001.html From a.badger at gmail.com Tue Sep 2 09:07:53 2008 From: a.badger at gmail.com (Toshio Kuratomi) Date: Tue, 02 Sep 2008 09:07:53 -0700 Subject: [OpenAjax] Licensing of reference implementation In-Reply-To: References: Message-ID: <48BD64D9.3000503@gmail.com> Jon Ferraiolo wrote: > Hi Toshio, > Thanks for the question. Before I can respond, please let me ask a > question. What in particular makes Apache V2 incompatible with GPLv2? I > can understand why it would be difficult to take GPL code into an > ApacheV2 project, but what aspect makes it difficult to take ApacheV2 > code into a GPL project? > This has been written up on the Free Software Foundation[1]_ and Apache Software FoundationWebsites[2]_. It boils down to the fact that the GPLv2 specifies that no further restrictions can be placed on code licensed under GPLv2 while the ApacheV2 places the additional restriction of patent indemnification. .. _[1]: http://www.apache.org/licenses/GPL-compatibility.html .. _[2]: http://www.fsf.org/licensing/licenses/#apache2 > Even if we felt dual licensing was a good idea, switching to dual > licensing would be a logistic challenge. The Apache V2 stipulation is in > our Members Agreement. To offer dual licensing, I am pretty sure we > would have to get our member companies (~110 of them) to agree to a > revision to the agreement they have already signed. > Understood. But if the aim of OpenAjax is to be adopted as widely as possible, having a license which does not allow the reference implementation to be used with GPLv2 code is a major setback. An alternative would be for OpenAJAX to sponsor someone to write a clean room implementation that follows the specification and is compatible with the GPLv2. However, this means you will always have double the work as you write more specifications. -Toshio > Jon > > > Inactive hide details for Toshio Kuratomi Toshio > Kuratomi > > > *Toshio Kuratomi * > > 09/01/2008 05:20 PM > > > > To > > Jon Ferraiolo/Menlo Park/IBM at IBMUS > > cc > > > Subject > > Licensing of reference implementation > > > > > I've subscribed to the mailing list but the subscription is awaiting > moderator approval so I'm sending you a message. > > Can the license of the reference implementation be changed? The Apache > License is unfortunately incompatible with the GPLv2. This means that > toolkits which use the reference implementation of OpenAJAX cannot be > used with GPLv2 licensed programs. > > Using a BSD license or dual licensing Apache and GPLv2 (or GPLv2+) would > be a way around this. > > Thanks, > -Toshio > > /(See attached file: signature.asc)/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature Url : http://openajax.org/pipermail/public/attachments/20080902/31024e3c/attachment.bin From jferrai at us.ibm.com Tue Sep 2 09:32:29 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Tue, 2 Sep 2008 09:32:29 -0700 Subject: [OpenAjax] Licensing of reference implementation In-Reply-To: <48BD64D9.3000503@gmail.com> Message-ID: Hi Toshio, Thanks for the info. OK, I see the problem. I'll see what I can do, but I can't make any promises. It is certainly possible for people to do clean-room reimplementations of our technologies. We usually deliver both open specifications and then (usually) an open source reference implementation (of course, with an Apache license). Therefore, people are not only able to create a new implementation from scratch by reading the spec, but in fact we encourage multiple implementations. I know of at least one proprietary vendors at OpenAjax Alliance who has done their own private implementations of OpenAjax Hub 1.0 due to their company's paranoia about using open source. Jon Toshio Kuratomi To Jon Ferraiolo/Menlo Park/IBM at IBMUS, 09/02/2008 09:07 public at openajax.org AM cc Subject Re: Licensing of reference implementation Jon Ferraiolo wrote: > Hi Toshio, > Thanks for the question. Before I can respond, please let me ask a > question. What in particular makes Apache V2 incompatible with GPLv2? I > can understand why it would be difficult to take GPL code into an > ApacheV2 project, but what aspect makes it difficult to take ApacheV2 > code into a GPL project? > This has been written up on the Free Software Foundation[1]_ and Apache Software FoundationWebsites[2]_. It boils down to the fact that the GPLv2 specifies that no further restrictions can be placed on code licensed under GPLv2 while the ApacheV2 places the additional restriction of patent indemnification. .. _[1]: http://www.apache.org/licenses/GPL-compatibility.html .. _[2]: http://www.fsf.org/licensing/licenses/#apache2 > Even if we felt dual licensing was a good idea, switching to dual > licensing would be a logistic challenge. The Apache V2 stipulation is in > our Members Agreement. To offer dual licensing, I am pretty sure we > would have to get our member companies (~110 of them) to agree to a > revision to the agreement they have already signed. > Understood. But if the aim of OpenAjax is to be adopted as widely as possible, having a license which does not allow the reference implementation to be used with GPLv2 code is a major setback. An alternative would be for OpenAJAX to sponsor someone to write a clean room implementation that follows the specification and is compatible with the GPLv2. However, this means you will always have double the work as you write more specifications. -Toshio > Jon > > > Inactive hide details for Toshio Kuratomi Toshio > Kuratomi > > > *Toshio Kuratomi * > > 09/01/2008 05:20 PM > > > > To > > Jon Ferraiolo/Menlo Park/IBM at IBMUS > > cc > > > Subject > > Licensing of reference implementation > > > > > I've subscribed to the mailing list but the subscription is awaiting > moderator approval so I'm sending you a message. > > Can the license of the reference implementation be changed? The Apache > License is unfortunately incompatible with the GPLv2. This means that > toolkits which use the reference implementation of OpenAJAX cannot be > used with GPLv2 licensed programs. > > Using a BSD license or dual licensing Apache and GPLv2 (or GPLv2+) would > be a way around this. > > Thanks, > -Toshio > > /(See attached file: signature.asc)/ > (See attached file: signature.asc) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080902/ebedc98b/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/20080902/ebedc98b/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: pic09650.gif Type: image/gif Size: 1255 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080902/ebedc98b/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/20080902/ebedc98b/attachment-0002.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/octet-stream Size: 204 bytes Desc: not available Url : http://openajax.org/pipermail/public/attachments/20080902/ebedc98b/attachment.obj From jferrai at us.ibm.com Fri Sep 5 03:46:34 2008 From: jferrai at us.ibm.com (Jon Ferraiolo) Date: Fri, 5 Sep 2008 03:46:34 -0700 Subject: [OpenAjax] OpenAjax Alliance news Message-ID: This email contains some short announcements for OpenAjax Alliance. Face-to-face meeting on October 23 in Silicon Valley ----------------------------- (This information also appears on the OpenAjax blog: http://www.openajax.org/blog/?p=64) The members of the OpenAjax Alliance will hold a one-day face-to-face meeting on Thursday, Oct. 23, 2008, the day after AJAXWorld RIA Conference and Expo 2008 West. The face-to-face will be hosted by Microsoft and located at a TBD location in the San Francisco Bay Area (somewhere in Silicon Valley). The various wiki pages for the face-to-face meeting is: * Main page: http://www.openajax.org/member/wiki/2008_October_Members_Meeting * Agenda: http://www.openajax.org/member/wiki/2008_October_Members_Meeting_Agenda * Registration: http://www.openajax.org/member/wiki/2008_October_Members_Meeting_Registration The full agenda is not yet available, but one key agenda item will be to review the results from the 2008 InteropFest ( http://www.openajax.org/blog/?p=63) and discuss what changes are needed to OpenAjax Hub 1.1 and OpenAjax Metadata based on those results. Steering Committee Election ----------------------------- In this year's Steering Committee election, four of the seven slots in the Steering Committee are up for election this year. The dates are as follows: * Nomination period: Sept 17-30, 2008 * Voting period: Oct 1-8, 2008 * Announcement of results: within a couple of days after the end of voting Any member can nominate themselves for the election by filling out a nomination web form. Encumbent SC members (i.e., Dojo Foundation, Eclipse Foundation, IBM and Zend) may run again. The nomination web form will be active only during the nomination period, and the voting web form will be active only during the voting period. Here are the relevant wiki pages: * Steering Commitee main page: http://www.openajax.org/member/wiki/Steering_Committee * Election main page: http://www.openajax.org/member/wiki/2008_Steering_Committee_Election * Nominations page: http://www.openajax.org/member/wiki/2008_Steering_Committee_Nominations * Voting page: http://www.openajax.org/member/wiki/2008_Steering_Committee_Voting_Page There will be subsequent emails with reminders about nominations and voting. Recent OpenAjax slide deck focusing on IDEs, Mashups and 2008 InteropFest ----------------------------- I gave a talk yesterday that provides an overview of current activities at OpenAjax Alliance and goes into detail about our initiatives around IDE workflows (OpenAjax Metadata for JavaScript APIs and Widgets) and mashup workflows (OpenAjax Hub 1.1 and OpenAjax Metadata for Widgets). The slide deck can be found at: * http://www.openajax.org/slidedecks/Interoperable%20Ajax%20Tools%20and%20Mashups.pdf OpenAjax Alliance as media sponsor for Ajax Experience ----------------------------- (This information also appears on the OpenAjax blog: http://www.openajax.org/blog/?p=65) OpenAjax Alliance is pleased to announce it will be a media sponsor of The Ajax Experience in Boston * http://ajaxexperience.techtarget.com/east/index.html Ajaxian.com is offering the OpenAjax community members a special rate for attending The Ajax Experience, September 29 - October 1. Register with the code ?openajax? to save $100 off the registration fee, making the price only $1395 after (regular rate: $1495). If you are interested in coming with a team, contact Tracey West at twest at techtarget.com. Groups of 3 or more are being offered an extra $300 off per person. Register for TAE here: * http://www.regonline.com/ajaxexperience. Thanks. Jon Jon Ferraiolo Web Architect, Emerging Technologies IBM, San Jose, CA Mobile: +1-408-956-2413 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://openajax.org/pipermail/public/attachments/20080905/b6564ddc/attachment.html