 |
 | This article contains content that is written like an advertisement .(March 2019) |
The OpenAjax Alliance is an industry group dedicated to the set of technologies and web programming techniques known as Ajax.
|
| This article contains content that is written like an advertisement .(March 2019) |
The OpenAjax Alliance is an industry group dedicated to the set of technologies and web programming techniques known as Ajax.
In late 2005, under the leadership of IBM, a number of 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 had 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]
The OpenAjax Alliance experienced 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:
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.
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.
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:
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.
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:
For an Ajax product to achieve OpenAjax Conformance, it must fulfill the following criteria:
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:
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.
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.
Sharable Content Object Reference Model (SCORM) is a collection of standards and specifications for web-based electronic educational technology. It defines communications between client side content and a host system, which is commonly supported by a learning management system. SCORM also defines how content may be packaged into a transferable ZIP file called "Package Interchange Format."
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 common prerequisite that open standards use an open license that provides for extensibility. Typically, anybody can participate in their development due to their inherently open nature. There is no single definition, and interpretations vary with usage. Examples of open standards include the GSM, 4G, and 5G standards that allow most modern mobile phones to work world-wide.
The Web Services Interoperability Organization (WS-I) was an industry consortium created in 2002 and chartered to promote interoperability amongst the stack of web services specifications. WS-I did not define standards for web services; rather, it created guidelines and tests for interoperability. In July 2010, WS-I joined the OASIS, standardization consortium as a member section. It operated until December 2017. The WS-I standards were then maintained by relevant technical committees within OASIS.
The Khronos Group, Inc. is an open, non-profit, member-driven consortium of 170 organizations developing, publishing and maintaining royalty-free interoperability standards for 3D graphics, virtual reality, augmented reality, parallel computation, vision acceleration and machine learning. The open standards and associated conformance tests enable software applications and middleware to effectively harness authoring and accelerated playback of dynamic media across a wide variety of platforms and devices. The group is based in Beaverton, Oregon.
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 Aviation Industry Computer-Based Training Committee (AICC) was an international association of technology-based training professionals that existed from 1988 to 2014. The AICC developed guidelines for aviation industry in the development, delivery, and evaluation of CBT, WBT, and related training technologies.
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.
OpenSocial is a public specification that outlines a set of common application programming interfaces (APIs) for web applications. Initially designed for social network applications, it was developed collaboratively by Google, MySpace and other social networks. It has since evolved into a runtime environment that allows third-party components, regardless of their trust level, to operate within an existing web application.
A distributed social network or federated social network is an Internet social networking service that is decentralized and distributed across distinct service providers, such as the Fediverse or the IndieWeb. It consists of multiple social websites, where users of each site communicate with users of any of the involved sites. From a societal perspective, one may compare this concept to that of social media being a public utility.
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.
The OPEN Alliance is a non-profit, special interest group (SIG) of mainly automotive industry and technology providers collaborating to encourage wide scale adoption of Ethernet-based communication as the standard in automotive networking applications.
Avnu Alliance is a consortium of member companies working together to create an interoperable ecosystem of low-latency, time-synchronized, highly reliable networking devices using the IEEE open standard, Time-Sensitive Networking (TSN) and its Pro AV networking protocol, Milan. Avnu Alliance creates comprehensive certification programs to ensure interoperability of network devices. In the Professional Audio Video (AV) industry, Alliance member companies worked together to develop Milan: a standards-based, user-driven deterministic network protocol for professional media, that through certification, assures devices will work together at new levels of convenience, reliability, and functionality. Milan™ is a standards-based deterministic network protocol for real time media. Avnu Members may use the Avnu-certified or Milan-certified logo on devices that pass the conformance tests from Avnu. Not every device based on AVB or TSN is submitted for certification to the Avnu Alliance. The lack of the Avnu logo does not necessarily imply a device is incompatible with other Avnu-certified devices. The Alliance, in conjunction with other complimentary standards bodies and alliances, provides a united network foundation for use in professional AV, automotive, industrial control and consumer segments.
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.