OpenAjax Alliance

Last updated

The OpenAjax Alliance is an industry group dedicated to the set of technologies and web programming techniques known as Ajax.

Contents

Membership in the OpenAjax Alliance consists of vendors, open source projects, and companies that utilize Ajax in their web technologies. The organization was established by Ajax companies and open source projects to address issues that require collaboration among the various organizations involved in creating and using Ajax products and technologies. The alliance does not collect dues or maintain a staff, so all of its activities are the result of voluntary contributions from its 100+ member organizations.

The organization's target audience is web developers and IT professionals who want to utilize Ajax technologies to create web applications with interactive user interfaces.

The alliance's technical focus is on achieving interoperability across different Ajax products and technologies. Interoperability allows customers to integrate Ajax technologies from various providers.

The OpenAjax Alliance engages in educational and communication initiatives, such as posting web pages and white papers on its website, maintaining a wiki, email lists, and issuing press releases.

History and Termination of Formal Operations

In late 2005, under the leadership of IBM, companies came together to discuss how to ensure that Ajax reaches its full potential as the industry standard application platform based on open technologies. These initial discussions led to the announcement of the "OpenAjax Initiative" on Feb. 1, 2006, with participation from 15 original companies including BEA, Borland, the Dojo Foundation, Eclipse Foundation, Google, IBM, Laszlo Systems, Mozilla Corporation, Novell, Openwave Systems, Oracle, Red Hat, Yahoo, Zend, and Zimbra. [1]

Between February 1 and May 15, 2006, an additional 15 organizations joined "OpenAjax", and the group of 30 companies held a two-day kickoff meeting in San Francisco to establish their plans. During the meeting, the decision was made to form the OpenAjax Alliance, define its mission, agree on an interim organizational process, and establish its activities. [2]

The participating companies then developed a governance model through a Members Agreement and began executing their marketing/educational and technical initiatives. The alliance's website and white paper were launched in September 2006. [3] In October 2006, the alliance elected its first Steering Committee. [4] By December 2006, the alliance released its first technical product, the OpenAjax Hub, with a draft specification and reference open-source implementation. The OpenAjax Hub integrated a dozen Ajax toolkits on a trial basis as part of the alliance's initial OpenAjax InteropFest. [5]

As of May 2008, the organization had over 100 member organizations, including major companies such as IBM, Microsoft, Google, Adobe, and Sun, as well as Ajax suppliers like the Dojo Foundation, Laszlo Systems, Nexaweb, Tibco, Zimbra, and a few individual members.

In October 2012, the OpenAjax Alliance formally concluded its operations. [6]

Members

The OpenAjax Alliance has been experiencing a steady growth in its membership. To view the complete list of members, please visit the OpenAjax Alliance homepage or the members wiki page.

The alliance's members include organizations from various categories:

  1. Ajax toolkit developers (both open source and commercial)
  2. Web browsers (both desktop and mobile)
  3. Enterprise product companies
  4. Organizations that utilize Ajax to provide solutions to their users
  5. Other community-oriented organizations, including open source projects or standards organizations, with a significant interest in Ajax

How OpenAjax Alliance is organized

Steering Committee

The OpenAjax Alliance members elect representatives from seven companies to serve on the OpenAjax Alliance Steering Committee. The Steering Committee is responsible for overseeing the operations of the OpenAjax Alliance on behalf of its member organizations. One of its key responsibilities is providing final approval for the establishment of working groups and the development of specifications, among other matters.

Working Groups

The OpenAjax Alliance develops formal materials through its Working Groups. Currently, there are two formally chartered working groups that operate according to the alliance's established process documents.

The Interoperability Working Group focuses on technical activities related to Ajax interoperability, particularly on client-side runtime issues. The group's primary deliverables include specifications that define OpenAjax Conformance in detail, such as the OpenAjax Hub specifications (versions 1.0 and 1.1), as well as the management of the OpenAjax Registry.

The Marketing Working Group is responsible for the OpenAjax Alliance's communication, education, and promotion efforts. Its main objective is to promote the adoption of open and interoperable Ajax-based Web technologies. The group produces white papers, oversees website development, and drives the strategy, high-level definition, and industry adoption of the OpenAjax Conformance term.

The IDE Working Group focuses on developing metadata standards that enable integration of various Ajax runtime libraries into different Ajax developer tools, specifically integrated development environments (IDEs). The group's metadata standard, known as the OpenAjax Metadata Specification, also serves as an industry standard for mashup widgets. The standard aims to be an intermediary format that closely aligns with popular proprietary formats, allowing for transcoding to and from the OpenAjax format. This approach ensures that support for the metadata formats is not necessary for every industry participant.

Task Forces

The OpenAjax Alliance establishes task forces to explore new areas of activity. These task forces consist of informal groups of members who conduct research and provide recommendations for future alliance initiatives. Currently, there are four task forces in place:

  1. The Security Task Force focuses on identifying Ajax security issues and determining the appropriate actions for the alliance to undertake.
  2. The Mobile Ajax Task Force investigates ways in which the OpenAjax Alliance can promote the adoption of Ajax applications on mobile devices and support developers in achieving success in this domain.
  3. The Gadgets Task Force collaborates with the IDE Working Group to ensure that the OpenAjax Metadata Specification meets the needs of the mashup community and serves as an industry standard for mashup widgets.
  4. The Runtime Advocacy Task Force utilizes an open wiki platform to gather input from the Ajax community. Their goal is to compile a prioritized feature request list that reflects the most significant needs of the Ajax industry with regard to future web browsers.

Specifications and open source

While the OpenAjax Alliance does not aim to become a formal standards body, it does actively engage in activities related to standards when necessary to achieve goals of enhanced interoperability, increased vendor choice, and the promotion of innovation. Consequently, the alliance may develop its own formal specifications or contribute to open-source projects to address significant gaps in the industry. The ultimate objective in such cases is to transition the work to a formal standards organization or an open-source project when the time is deemed appropriate.

Members of the OpenAjax Alliance are encouraged to participate in standards-related activities within other standards bodies and open-source projects. This collaboration helps to expedite the coordinated progress of OpenAjax technologies and products.

OpenAjax Conformance

A fundamental aspect of OpenAjax Alliance's work revolves around defining OpenAjax Conformance. OpenAjax Conformance refers to the set of requirements that the alliance imposes on Ajax technologies, products, and applications. By utilizing Ajax products that adhere to OpenAjax Conformance, IT managers and web developers can benefit from the following:

  1. Seamless integration of multiple Ajax products and technologies within the same web application, particularly in applications employing mashup techniques.
  2. Increased confidence in product choices, as OpenAjax Conformance plays a comparable role in the Ajax community to that of the Good Housekeeping Seal in the consumer products realm.
  3. Reduced training and development costs, as well as expedited delivery of Web 2.0 innovations, due to the adoption of common approaches built upon OpenAjax standards within the industry.
  4. Interchangeability of OpenAjax Conformant products, enabling customers to select from various vendors.

For an Ajax product to achieve OpenAjax Conformance, it must fulfill the following criteria:

  1. Support the OpenAjax Hub.
  2. Register its library and JavaScript global objects with the OpenAjax Registry.
  3. Comply with all relevant Conformance Requirements outlined in the collection of specifications provided by the OpenAjax Alliance.

OpenAjax hub

The OpenAjax Hub is a compact collection of JavaScript technologies designed to fulfill essential requirements for Ajax runtime interoperability. The initial release, OpenAjax Hub 1.0, incorporates the following capabilities:

  1. Ajax library loading
  2. An event hub based on the publish/subscribe model (topic bus)

The upcoming version, OpenAjax Hub 2.0, aims to expand the publish/subscribe functionalities to facilitate secure mashup workflows and client-server communications. In the context of mashups, Hub 2.0 enables the confinement of mashup widgets within secure sandboxes while offering a facilitated message bus.

The OpenAjax Alliance is responsible for developing the OpenAjax Hub Specification and provides an open-source reference implementation.

See also

Related Research Articles

The Common Language Infrastructure (CLI) is an open specification and technical standard originally developed by Microsoft and standardized by ISO/IEC and Ecma International that describes executable code and a runtime environment that allows multiple high-level languages to be used on different computer platforms without being rewritten for specific architectures. This implies it is platform agnostic. The .NET Framework, .NET and Mono are implementations of the CLI. The metadata format is also used to specify the API definitions exposed by the Windows Runtime.

<span class="mw-page-title-main">Object Management Group</span> Computer industry standards consortium

The Object Management Group (OMG) is a computer industry standards consortium. OMG Task Forces develop enterprise integration standards for a range of technologies.

The Portable Operating System Interface is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines both the system and user-level application programming interfaces (APIs), along with command line shells and utility interfaces, for software compatibility (portability) with variants of Unix and other operating systems. POSIX is also a trademark of the IEEE. POSIX is intended to be used by both application and system developers.

Interoperability is a characteristic of a product or system to work with other products or systems. While the term was initially defined for information technology or systems engineering services to allow for information exchange, a broader definition takes into account social, political, and organizational factors that impact system-to-system performance.

An open standard is a standard that is openly accessible and usable by anyone. It is also a prerequisite to use open license, non-discrimination and extensibility. Typically, anybody can participate in the development. There is no single definition, and interpretations vary with usage.

Web Services for Remote Portlets (WSRP) is an OASIS-approved network protocol standard designed for communications with remote portlets.

The common warehouse metamodel (CWM) defines a specification for modeling metadata for relational, non-relational, multi-dimensional, and most other objects found in a data warehousing environment. The specification is released and owned by the Object Management Group, which also claims a trademark in the use of "CWM".

OMA SpecWorks, previously the Open Mobile Alliance (OMA) is a standards organization which develops open, international technical standards for the mobile phone industry. It is a nonprofit Non-governmental organization (NGO), not a formal government-sponsored standards organization as is the International Telecommunication Union (ITU): a forum for industry stakeholders to agree on common specifications for products and services.

The Storage Management Initiative Specification, commonly called SMI-S, is a computer data storage management standard developed and maintained by the Storage Networking Industry Association (SNIA). It has also been ratified as an ISO standard. SMI-S is based upon the Common Information Model and the Web-Based Enterprise Management standards defined by the Distributed Management Task Force, which define management functionality via HTTP. The most recent approved version of SMI-S is available on the SNIA website.

A mashup, in web development, is a web page or web application that uses content from more than one source to create a single new service displayed in a single graphical interface. For example, a user could combine the addresses and photographs of their library branches with a Google map to create a map mashup. The term implies easy, fast integration, frequently using open application programming interfaces and data sources to produce enriched results that were not necessarily the original reason for producing the raw source data. The term mashup originally comes from creating something by combining elements from two or more sources.

<span class="mw-page-title-main">Linux Foundation</span> Non-profit technology consortium to develop the Linux operating system

The Linux Foundation (LF) is a non-profit technology consortium founded in 2000 as a merger between Open Source Development Labs and the Free Standards Group. Its primary objectives are to standardize Linux, support its growth, and promote its commercial adoption. Additionally, it hosts and promotes the collaborative development of open source software projects.

<span class="mw-page-title-main">OpenSocial</span> Public specification aimed at social networking applications

OpenSocial is a public specification that defines a component hosting environment (container) and a set of common application programming interfaces (APIs) for web applications. Initially, it was designed for social network applications and developed by Google along with MySpace and several other social networks. Recently, it has been adopted as a general use runtime environment for allowing untrusted and partially trusted components from third parties to run in an existing web application. The OpenSocial Foundation moved to integrate or support numerous other Open Web technologies. This includes OAuth and OAuth 2.0, Activity Streams, and Portable Contacts, among others.

Service Component Architecture (SCA) is a software technology designed to provide a model for applications that follow service-oriented architecture principles. The technology, created by major software vendors, including IBM, Oracle Corporation and TIBCO Software, encompasses a wide range of technologies and as such is specified in independent specifications to maintain programming language and application environment neutrality. Many times it uses an enterprise service bus (ESB).

Energistics is a global, non-profit, industry consortium that facilitates an inclusive user community for the development, adoption and maintenance of collaborative, open standards for the energy industry in general and specifically for oil and gas exploration and production.

The Publishing Requirements for Industry Standard Metadata (PRISM) for the Internet, computing, and computer science, is a specification that defines a set of XML metadata vocabularies for syndicating, aggregating, post-processing and multi-purposing content.

The Linear Tape File System (LTFS) is a file system that allows files stored on magnetic tape to be accessed in a similar fashion to those on disk or removable flash drives. It requires both a specific format of data on the tape media and software to provide a file system interface to the data.

CIPURSE is an open security standard for transit fare collection systems. It makes use of smart card technologies and additional security measures.

<span class="mw-page-title-main">Open Geospatial Consortium</span> Standards organization

The Open Geospatial Consortium (OGC), an international voluntary consensus standards organization for geospatial content and location-based services, sensor web and Internet of Things, GIS data processing and data sharing. It originated in 1994 and involves more than 500 commercial, governmental, nonprofit and research organizations in a consensus process encouraging development and implementation of open standards.

The Physical Security Interoperability Alliance (PSIA) is a global consortium of more than 65 physical security manufacturers and systems integrators focused on promoting interoperability of IP-enabled security devices and systems across the physical security ecosystem as well as enterprise and building automation systems.

glTF 3D scene and model file format

glTF is a standard file format for three-dimensional scenes and models. A glTF file uses one of two possible file extensions: .gltf (JSON/ASCII) or .glb (binary). Both .gltf and .glb files may reference external binary and texture resources. Alternatively, both formats may be self-contained by directly embedding binary data buffers. An open standard developed and maintained by the Khronos Group, it supports 3D model geometry, appearance, scene graph hierarchy, and animation. It is intended to be a streamlined, interoperable format for the delivery of 3D assets, while minimizing file size and runtime processing by apps. As such, its creators have described it as the "JPEG of 3D."

References

  1. "IBM Newsroom".
  2. http://www.infoworld.com/article/06/05/22/78577_HNajaxforge_1.html
  3. http://www.marketwire.com/mw/release_html_b1?release_id=164720 [ bare URL plain text file ]
  4. "OpenAjax Alliance".
  5. "InteropFest 2007 March - MemberWiki".
  6. "[OpenAjaxSteeringCommittee] URGENT: PLEASE VOTE to approve termination of formal operations at OpenAjax Alliance". openajax.org. Archived from the original on 2014-08-14.

Notes

[1]

  1. Open Aax Steering Committee email archive link to message asking for formal operations to terminate. http://openajax.org/pipermail/steeringcommittee/2012q4/001015.html