Interoperability Minutes 2009-05-26
From MemberWiki
URL: http://www.openajax.org/member/wiki/Interoperability_Minutes_2009-05-26
Contents |
Attendees
- Jon Ferraiolo, IBM
- Javier Pedemonte, IBM
- Eduardo Abe, ILOG/IBM
- Howard Weingram, TIBCO
Minutes
(Reviewing the red-colored comments in each chapter)
Introduction chapter
Jon: Howard fixed the text to say "mashup" instead of sometimes spelling it "mash-up"
RESOLUTION: Remove red-colored comment about mashups
Howard: The comment about not extending OpenAjax objects is wrong. We do it in our implementation.
Jon: I agree with the new text about putting extensions on a subobject
RESOLUTION: Jon to fix by removing "MUST NOT" sentence, and add text to say that extensions should be put onto a subobject or follow extensibility instructions in various parts of the spec
Jon: Regarding JSDoc, I added version 2.1 to the spec. I checked to make sure that the subset of JSDoc that we use is still compatible with version 2.1.
Howard: OK, good.
Howard: OK with the new paragraph about subobjects for parameters?
Jon: Yes, good addition
Libraries chapter
Jon: Howard added a comment about mixing OpenAjax implementations
Howard: In Hub 1.0, this mattered, but in Hub 2.0 we have to mix clients that might use a different implementation of the Hub. We need to allow you to take a container from one vendor and mix with Managed Hub from another vendor.
Javier: Yes. To do this, the Container just has to implement publishForClient, etc.
Howard/Javier: Container/HubClient need to come from same implementation
Howard/Javier: We have a version number on the protocol between Container and HubClient.
Howard: Might want to add a version# to the container
Jon: I'd prefer not adding it now
Howard: OK, but that means that version# is accurate for Managed Hub but not necessarily correct for containers
RESOLUTION: Remove section on no mixing
Howard: Regarding conformance requirements, my quibble is that this is the only section that has conformance requirements. We don't use it in the Managed Hub.
Jon: Yes, it's ridiculous.
RESOLUTION: Remove green-colored Conformance highlights
Pubsub Overview chapter
Jon: Howard made several editorial changes. I reviewed them all carefully and agree with all of them.
Unmanaged Hub chapter
RESOLUTION: Convert to JSDoc style conventions for documenting these APIs to be consistent with Managed Hub chapter.
ACTION JON: Make the above changes
Managed Hub Overview chapter
Jon: Howard made some editorial changes. I reviewed them all carefully and agree with all of them.
Jon: Howard, have you looked at the sample app?
Howard: No, but I'll make sure I look at it.
Managed Hub APIs chapter
Howard/Jon: We've beaten this chapter to death over the past several months.
Howard: I'm OK with removing the new enableDebug feature. It's implementation-specific.
RESOLUTION: Remove enableDebug section
Jon: New sentence about data owned by publisher. Any objections?
(none)
Topic Names chapter
Jon: Howard, have you reviewed this yet?
Howard: No, still need to do so.
What's left to do before Release Candidate?
Javier: As far as I know, code and test suite is done. Before we declare RC, I will rerun the test suite across all supported browsers just to be sure.
Javier: Another issue was for FIM we are now putting the URL on a URL param instead of fragment to address need to allow redirection. Unfortunate, but only way to get it to work.
Jon: How are things going with updating the sample mashup application on the OpenAjax site.
Javier: Working somewhat. Working with Adam to try to make it clean. Should be ready soon.
Jon/Howard: Not a requirement for Release Candidate. Very valuable to have when we announce completion.
Howard: I hope to complete my editorial pass by the end of this week. By next meeting, we should be able to go to Release Candidate.
