OpenAjax Metadata 1.0 Release Review

From MemberWiki

Jump to: navigation, search

The Release Review phone call for OpenAjax Metadata 1.0 occured on March 30, 2010 at 11am US-PT.

See Release Review Minutes below for a record of the minutes from that phone call.

Contents

Background

The IDE Working Group at OpenAjax Alliance is in the final approval phase for OpenAjax Metadata 1.0 after a few years of standards and open source work. Here is some of the things that OpenAjax Alliance and the industry have products around OAM:

The IDE Working Group devoted significant effort towards:

  • A complete and detailed formal Specification (the OpenAjax Metadata 1.0 Specification)
  • Open source implemenations at OpenAjax Alliance of major parts of the spec open source reference implementation
    • Open source implementation of an OpenAjax Widget loader (loader.js)
    • Open source converter from JSDoc inline comments into OAM's XML for describing JavaScript APIs
    • Open source converter from YUI's JSON format for describing their APIs into OAM's XML for describing JavaScript APIs
    • An [open source sample mashup application] that demonstrates how to build a mashup assembly application using OpenAjax Hub 2.0 and OpenAjax Widgets (defined in the OpenAjax Metadata 1.0 Specification)
  • Eclipse Foundation has an open source implementation of the OAM JavaScript API features within the JSDT component that is a standard piece of the Web Tools Project
  • Various commercial implementations. The widget features are supported by Adobe Dreamweaver CS4 and are the preferred format for 3rd party widget extensions and by multiple IBM commercial products and research projects. OAM's JavaScript API features are supported by Aptana Studio and IBM Rational Application Developer.
  • A multiple-vendor interoperability event in 2008 (the 2008 InteropFest where various companies integrated their products and technologies with OpenAjax Hub and OpenAjax Widgets (see [press announcement])

"Release Review" is a required part of the OpenAjax Alliance Development Process [3] and happens just before finalization and approval of all OpenAjax Specifications. The process requires a 3-week freeze period on the specification, followed by a Release Review phone call open to all OpenAjax members. One of the reasons for the Release Review milestone is to allow member companies an opportunity to review the given specifications for potential intellectual property issues. The phone call allows members to hear each others feedback on the Specification. If no major problems are raised during the Release Review phone call, then OpenAjax Metadata 1.0 will be submitted to the members and the Steering Committee shortly afterwards for approval.

Release Review Minutes

Date/time: March 30, 2010 at 11am US-PT.

Attendees

  • Jon Ferraiolo, IBM
  • Javier Pedemonte, IBM
  • Michael Squillace, IBM
  • Eduardo Abe, IBM
  • Kin Blas, Adobe
  • Lori Hylan-Cho

Minutes

Jon: I expect low attendance. The main reason for Release Review phone calls as part of our process was to alert member companies about potential IP issues within new specifications. The worry long ago was that our royalty free specs might impact patent portfolios. However, we have discovered over time that OpenAjax specs do not tend to have significant IP issues.

Jon: Also, the Release Review phone call gives people an opportunity to ask questions and listen to the discussion. A last chance to speak or forever hold your peace.

Jon: Any questions or comments?

Michael: I went through the spec and was surprised at how big it is.

Jon: Yes, two major parts, widgets and JavaScript APIs. For Michael, who wasn't on the WG, we've been working on this spec for maybe 3 years. There are multiple implementations, including Dreamweaver, Eclipse, and Aptana, and open source for both the widget and JavaScript APIs. Should have finished the spec long ago, but the end game got drawn out because of people getting new jobs and assignments.

Jon: Any questions or comments?

(nothing)

Jon: Kin, did you read the minor spec change I sent on email?

Kin: Been busy. I'll read it after this meeting.

...soon after...

Kin: Email looks fine.

Jon: OK, thanks.

Kin: Dreamweaver uses the widget format from OAM for 3rd party widgets, which can get posted on the Dreamweaver Exchange. The current DW requires that you wrap the OAM in our own packaging format, which makes interoperability difficult.

Jon: I have pulled down some widgets from the DW Exchange and unpacked them using a tool I found. Yes, I see the OAM files.

Jon: Do you have any jQuery widgets?

Kin: We are working with the jQuery UI team, YUI team, and some individual developers. Moving towards supporting ZIP. Paul Backup of YUI and Thomas Shaw of jQuery UI.

Jon: Can you send me private email with their emails? So we can try to see if we can have interoperability between what we are doing with the OA Widget loader in open source and DW?

Kin: Will be interesting to see how compatible the OAM files are across implementations. We only use a subset. We don't support the mashup features.

Jon: Our implementation falls back if no mashup features in the file. I expect there is a subset that will work fine in both cases, but the sooner the better in trying things out.

Kin: I'll send emails and a ZIP file with a sample jQuery widget.

Jon: Recently, I got SVG Web working with our OA Widget loader. Turned out to be easy. Just add a LIBRARY tag for SVG Web and then put SVG stuff in the CONTENT. Good for graphic widgets like arrows. Maybe I can submit these widgets to the DW Exchange.

(after 20 minutes, no outstanding issue and there was a mutual decision that OK for everyone to drop, except Jon, who hung around for the whole hour.)

Retrieved from "http://www.openajax.org/member/wiki/OpenAjax_Metadata_1.0_Release_Review"
Personal tools