Share

From this page you can share Initial Draft Specification for "OpenAjax Metadata" to a social bookmarking site or email a link to the page.
Social WebE-mail
Enter multiple addresses on separate lines or separate them with commas.
Initial Draft Specification for "OpenAjax Metadata"
(Your Name) has forwarded a page to you from Ajaxonomy
(Your Name) thought you would like to see this page from the Ajaxonomy web site.

Initial Draft Specification for "OpenAjax Metadata"

Tagged:  

News from the OpenAjax Alliance! The IDE Working Group and Gadgets Task Force have completed an initial draft of the “OpenAjax Metadata Specification". The Metadata spec represents a standard for interoperability across the Ajax toolkits we know and love. Here are the metadata items defined in this first draft version:

  • Ajax widgets - the spec defines two definitions for "widget"
    • UI controls - Some Ajax libraries provide a set of user interface building block components such as combo boxes, menu bars, or charts
    • Mashup components (aka “widgets” and “gadgets”) - Mashup frameworks allow for pre-packaged mini-applications (sometimes called “widgets” or “gadgets”) to be combined together within a composite application (the “mashup”), where the mashup components react to each other intelligently, such as when the user selects an address in one component which causes a different component to display an updated map that shows the given address.
  • Ajax APIs - the spec provides a set of metadata that describes runtime JavaScript APIs (like classes and methods) available for an Ajax library.
  • Ajax libraries - includes metadata fields similar to entries in the OpenAjax Registry

The primary target consumers of OpenAjax Metadata 1.0 are software products. It is expected that these software products will consume and use the metadata to provide enhanced experience for users who building Ajax-powered solutions. In particular:

* Mashup frameworks will use OpenAjax Metadata to use OpenAjax Metadata for widgets, such as the message types that the widget produces and consumes and the customization parameters that the widget supports

* Ajax IDEs will use OpenAjax Metadata to provide the developer with (presumably automatically-generated) API documentation, intelligent code-assist, widget palettes, and widget property editors

The draft specification can be found here.

Click here to read the announcement from the OpenAjax Alliance