IDE Charter v1
Introduction, including status of this document
This document contains the approved version 1 charter for the IDE Working Group. The version 1 charter expires on Dec. 31, 2008. An updated version 2 charter is being developed to extend the Working Group. For more information, please refer to the following other important wiki pages:
- IDE Working Group charter (main page): http://www.openajax.org/member/wiki/IDE_Charter
- IDE Working Group version 2 charter: http://www.openajax.org/member/wiki/IDE_Charter_v2
- IDE Working Group main page: http://www.openajaxalliance.org/member/wiki/IDE
This vesion 1 charter for the IDE Working Group was approved by the OpenAjax Alliance Steering Committee on July 10, 2007, with the result that the IDE Working Group was formally launched. This charter was developed collaboratively by the Members of OpenAjax Alliance and then submitted for review/commenting by the Members and review/approval to the Steering Committee, in accordance with the OpenAjax Alliance Development Process.
This wiki page should not be changed except via coordination with the Chair (see below).
Minutes from Creation Review Phone Call
The Creation Review phone call for the proposed IDE Working Group occurred on June 21. Minutes for the phone call can be found at:
- IDE Working Group Declaration -
- Proposal Phase - Jan. 29, 2007 - April 18, 2007
- IDE Working Group Charter Temporarily Frozen and Declaration Email Sent - May 14, 2007
- IDE Working Group Creation Review phone call
- June 21, 2007. 9:00 AM Pacific, 12 PM Eastern, 6 PM Paris.
- US toll-free: 1-888-227-9220, Int'l: 719-785-4480, Passcode 871757
- Member voting - If no objections during creation review period, member voting would commence the day after Creation Review phone call and continue for 1 week.
- Steering Committee voting - During the 1 week period following tabulation and reporting on Member voting.
Initiating Member and Proposal Lead
The OpenAjax Alliance Development Process requires that the initiating Member identify its Proposal Lead:
- Initiating Member: TIBCO
- Proposal Lead: Kevin Hakman <khakman(at)tibco.com>
"Visual and non-visual Controls and their APIs" is used below to mean visual controls like data grids, sliders, form elements, GUI containers Non-visual controls like data objects, communication objects, events; and the application programming interfaces (APIs) developers would use to instance, query, modify, and execute aspects of those.
Mission and Scope
The IDE Working Group has responsibility for industry standards for describing Visual and non-visual Controls and Ajax library APIs for use in design-time and potentially run-time scenarios so as to:
- provide a predictable way for makers of libraries and controls to publish metadata about their libraries and controls useful in authoring and potentially run-time processes
- provide a predictable way for makers of IDEs and authoring tools supporting Ajax development to consume metadata about Ajax libraries and controls useful in authoring and potentially run-time processes
- provide a list of IDE features that would be "nice to have" for Ajax authoring cycles in IDEs, (e.g. auto-completion, type-ahead, code completion, type checking), and provide a standard way to comment and annotate Ajax controls, libraries, and potentially custom Ajax application code (user defined classes and application logic) to dove tail with these features
- provide a standard approach to commenting Ajax source code such that a common set of utilities could be created to generate the metadata (either statically in advance as a separate file or by the IDEs dynamically upon loading or registering a new Ajax class object)
- define standards and/or best practices in the area of Ajax application debugging, such as recommendations about the availability of debug versions of Ajax libraries that can be integrated into IDEs
The specifications produced by the WG will target design-time integration with IDEs as the primary use case, but the WG will develop appropriately generalized technologies on an opportunistic basis to design features in a manner that promotes maximize reuse in other usage scenarios, such as runtime-integration in mashup environments.
The WG may pursue industry-wide activities on behalf of the Ajax IDE industry, such as collecting and publishing market research.
The WG will leverage work to date from the IDE Integration Task Force (http://www.openajax.org/member/wiki/IDE_TF).
The WG will be responsible for addressing development issues associated with IDEs for creating Ajax solutions on all Ajax-enabled devices. As such, its responsibilities would go beyond desktop computers into mobile devices and other computing platforms where Ajax can be used.
This charter allows for the WG to define specifications and features as necessary without rechartering so long as those specifications and features are consistent with the mission of the WG and are thus focused on cross-product interoperability arising from the integration of Ajax libraries and Ajax controls into Ajax IDEs. On the other hand, if new features are proposed that go beyond this interoperability scope, a new or revised charter will be necessary.
Ajax IDE Integration Use Cases and Requirements Specification
The WG will finish and publish an Ajax IDE Integration Use Cases and Requirements Specification, building from the wiki pages that have been developed in the IDE Integration Task Force (http://www.openajax.org/member/wiki/IDE_TF). This document will identify the topics that MUST, SHOULD or MAY be addressed in the Ajax IDE Integration Specification.
Ajax IDE Integration Specification
The WG will produce an Ajax IDE integration specification that specifies metadata and other integration technology requirements consistent with the Mission and Scope (see above) that will enable Ajax libraries and Ajax controls to be integrated into IDEs. The Use Cases and Requirements document will guide the process of developing the Specification.
The WG may produce other Materials, including Specifications, other relevant technical documents, tests, and sample applications, so long as they are consistent with the Working Group's mission and scope.
Coordination with other Working Groups and Task Forces
This WG will coordinate with other activities at OpenAjax Alliance as follows:
- Marketing WG - promotional activities associated with this WG's activities, progress, and industry adoption
- Interoperability Committee (or future WG) - IDE integration issues that overlap with runtime scenarios
- Communications Hub Task Force (or future WG) - IDE integration issues that overlap with client-server communications
- Security Task Force (or future WG) - IDE integration issues that overlap with Ajax security issues
- Mobile Hub Task Force (or future WG) - IDE integration issues that overlap with Mobile Ajax issues
If new OpenAjax activities are started during the duration of this WG, the WG will determine what coordination activities are required with the new activities.
This WG will be chartered to run until Dec. 31, 2008.
Revisions to this charter might shorten or extend the duration of this WG.
The following milestones represent expected delivery dates, but the WG can use judgment to update delivery dates using its own discretion.
- It is expected that a stable draft of uses cases and requirements will be available by the June of 2007.
- It is expected that an incomplete, but reviewable specification will be available for public review by July of 2007.
- It is expected that a feature-complete draft specification will be available by September 1, 2007 around which time we'll hold an AjaxIDEInteropFest.
- It is expected that a revised and final feature-complete draft specification will be available by December 1, 2007
- It is expected that an approved version 1.0 specification will be available by January 31 of 2008.
Success and completion criteria
This WG can consider its efforts around the Specification to be successful if:
- Some popular and specialized IDEs ship with abilities to load and unload individual or collections of Visual and Non-Visual Ajax Controls and library APIs conformant with the specification
- Some popular and specialized Ajax toolkits provide mechanisms to have their libraries be used by IDEs that support the Specification
- Some independent Ajax control providers to have their Ajax controls and APIs support the Specification
Further success is measured by the degree to which the IDEs support the additional Ajax authoring features this WG's reasearch shows developers would like to have in their IDEs.
Relationship to other forums
- Whenever possible, Specifications should reference industry-accepted relevant Ajax industry standards (de jure and de facto) rather than develop conflicting new features or authoring redundant feature definitions.
Email will occur on email@example.com. This email list will be read-only to people who are not representatives of Members of OpenAjax Alliance. Public discussion will occur on firstname.lastname@example.org.
Normally, there will be bi-weekly phone calls, but phone calls may be added or cancelled at the discretion of the chair.
The IRC channel for this WG is: irc.freenode.net, #oaa-ide
Chair, expected membership, and operational rules
Kevin Hakman of TIBCO is the proposed chair for this WG.
It is expected that the people who are currently involved in the existing IDE Task Force will participate in this WG. The proposal lead will work towards recruiting component vendors and more IDE vendors and experts to the group.
There will be a consensus decision process managed by the chair that aligns with common practice in Web standards (e.g., W3C consensus process) and open source activities (e.g., Apache voting process), where a particular decision process used to resolve a particular issue is chosen by the chair based on appropriateness to the given circumstance. This WG produces recommendations to the Membership and Steering Committee about activities and material to be published, in accordance with process defined by the OpenAjax Alliance Members Agreement and OpenAjax Alliance Development Process.