Interoperability Charter v3

From MemberWiki

Jump to: navigation, search

Contents

Introduction, including status of this document

This document contains the approved text for the updated version 3 charter for the Interoperability Working Group. This updated charter replaces the version 2 charter that expired on Dec. 31, 2009. For more information, please refer to the following other important wiki pages:

This version 3 charter was developed in accordance with the OpenAjax Alliance Development Process and has been approved by the OpenAjax Alliance Steering Committee.

This wiki page should not be changed except via coordination with the Chair(s) (see below). The preferred approaches for feedback on this document are the Interoperability committee mailing list (interop@openajax.org), the public mailing list (public@openajax.org), or the discussion tab on this wiki page.

Rechartering phone call

The rechartering phone call for the Interoperability Working Group (formally known as the "Creation Review" phone call) occurred on:

  • Monday, Jan. 18, 2010, 10:30am PT, 1:30pm ET, 7:30pm Paris
  • US toll-free: 1-866-423-8350, Int'l: 1-719-387-8273, Passcode 283044
  • For international phone numbers, refer to this wiki page.

Minutes from that phone call:

Members will vote on the rechartering during the following time period:

  • Jan. 19, 2010 to Jan. 25, 2010

The rechartering voting page is at:

Assuming members approve, then Steering Committee voting on the rechartering will occur just after Member voting.

Projected schedule

  • Creation Review phone call (see previous section)
  • 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: IBM
  • Proposal Lead: Jon Ferraiolo (jferrai(at)us.ibm.com)

Mission and scope

The Interoperability Working Group has responsibility for technical activities in the general area of Ajax interoperability covering the following areas:

  • Interoperability within the same Web application - ability to combine JavaScript components from multiple Ajax toolkits within the same Web application and have those components interact with each other.
  • Interoperability within a mashup application - ability to combine Ajax-powered mashup "widgets" (i.e., self-contained components) and have those components interact with each other, including the ability for untrusted 3rd party widgets to co-exist safely and securely in the same mashup with other components.
  • OpenAjax Registry - development and management of an industry-wide registry of Ajax libraries that contains a list of the JavaScript globals ("namespaces") and HTML markup (elements and attributes) that are allocated to and/or used by particular Ajax libraries.
  • OpenAjax Conformance - development and management of the rules around the OpenAjax Conformance trust brand, a set of conformance requirements that OpenAjax Alliance places on Ajax technologies, products, and applications. These requirements focus on a small number of simple but important aspects of Ajax usage, thereby providing the critical bits of Ajax interoperability that customers need, but in a manner that allows Ajax suppliers to continue to innovate and move forward with new technologies and products.
  • Best practices initiatives - Depending on industry interest, the Interoperability WG might work on various technical documents, testbeds and sample applications (e.g., acid tests) that support efforts around "OpenAjax Conformance" and any of the following:
    • Browsers
    • Ajax toolkits
    • Ajax applications
    • IDEs
    • Ajax server frameworks

The WG will produce Materials that are consistent with its mission and scope, including Specifications, other relevant technical documents, tests, and sample applications.

The WG will manage the Alliance's open source project at SourceForge that develops reference implementations of the Specifications produced by this WG, test suites and related utility software (such as automated build and test scripts).

The WG will manage the Alliance's technology coordination efforts with the external community around the various specifications and technologies developed by the WG.

The WG will be responsible for addressing interoperability issues associated with all Ajax-enabled devices. As such, its responsibilities goes beyond desktop computers into mobile devices and other computing platforms.

Work plan

Deliverables

Coordination with OpenSocial Foundation to integrate OpenAjax pubsub technologies into OpenSocial Gadgets

In 2009, there was considerable coordination effort, concrete proposals, and proof-of-concept open source integration work towards making OpenAjax pubsub technologies, such as OpenAjax Hub 2.0 Specification and selected features from the OpenAjax Metadata 1.0 Specification, into OpenSocial Gadgets in order to provide strong inter-gadget pubsub features to the OpenSocial community. The WG will continue and complete those integration efforts. These efforts may require updates to the OpenAjax Hub 2.0 Specification and most likely will require updates to the open source reference implementation.

Errata, Updates and Revisions to the OpenAjax Hub Specification

This Working Group may choose to develop one or more subsequent releases of the OpenAjax Hub.

This charter allows for the Working Group to add new features to the Hub relating to a Communications Hub, a Security Hub, a Data Hub, or other similar mediation logic, without rechartering the Working Group, so long as those features are focused on interoperability and integration of multiple Ajax toolkits where the Hub performs a dispatching role. On the other hand, if new features are proposed that go beyond this interoperability scope, a new or revised charter will be necessary.

Standardization of common event names and payloads for those events

The WG might produce Material, possibly in the form of Specifications, that define the technical details around standardization of certain commonly used event topics (potentially both the event name and payload) and relevant best practices (e.g, recommended approaches for how to name events) to promote interoperability in mashup scenarios. This standardization effort might be done in conjunction with OpenAjax Registry work.

If standard events are defined by this WG, those events will be relevant to the technologies developed within this WG and appropriate to the mission and scope of this WG. One example of a standardized event that might be developed within this WG would be events relating to drag-and-drop within mashup scenarios.

It is expected that other OpenAjax Alliance working groups and other organizations, including other industry groups, will define event names and event payload standards building on the foundation work produced by this WG.

OpenAjax Registry

This WG will produce Specifications, other related Material, open source reference implementations, test suites, and related utility source code in order to deliver to the industry an OpenAjax Registry, which is an industry-wide registry of Ajax libraries that contains a list of the JavaScript globals ("namespaces") and HTML markup (elements and attributes) that are allocated to and/or used by particular Ajax libraries.

The initial release or subsequent releases of the Registry might be extended to address other industry interoperability requirements, such as including a list of mashup messaging topics and payloads.

If there is industry demand for updates to OpenAjax Registry, and these updates are consistent with the existing charter and can be accomplished within the charter period, then this Working Group may choose to develop one or more subsequent releases of the OpenAjax Registry.

OpenAjax Best Practices

This WG may choose to produce produce Material, possibly in the form of Specifications, that define the technical details around the official definition of OpenAjax Alliance's Best Practices.

Coordination with other OpenAjax Alliance committees

This WG will coordinate with other activities at OpenAjax Alliance as follows:

  • Gadgets TF (or future WG) - Mashup integration issues, particularly around the ability to reuse Ajax library widgets within mashup scenarios and standardized topic names
  • IDE WG - IDE issues that overlap with Ajax library runtime scenarios
  • Security Task Force (or future WG) - IDE integration issues that overlap with Ajax security issues
  • Mobile 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.

Relationship to other forums

This WG will coordinate with OpenSocial Foundation on integration of OpenAjax pubsub features into OpenSocial Gadgets.

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.

Schedule

Duration

This WG will be chartered to run until Dec. 31, 2010.

Revisions to this charter might shorten or extend the duration of this WG.

Milestones

It is expected that there will be significant progress towards OpenAjax/OpenSocial integration in the first half of 2010. It is difficult to project when such integration efforts will be complete and/or will become formally approved specifications, but the goal is for these efforts to be finished as early in 2010 as possible.

Communications mechanisms

Email

Email will occur on interop@openajax.org. This email list will be read-only to people who are not representatives of Members of OpenAjax Alliance. Public discussion will occur on public@openajax.org.

Phone

Phone calls will happen on an as-needed basis.

IRC

The IRC channel for this WG is: irc.freenode.net, #oaa-interop

Chair, expected membership, and operational rules

Jon Ferraiolo is the chair for this WG. It is expected that the people who are currently involved in the existing Interoperability Committee will participate in this WG. 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.

Retrieved from "http://www.openajax.org/member/wiki/Interoperability_Charter_v3"
Personal tools