View source

== (20070625) David Frankel's fixes and questions ==

* David suggests that we add the word "the" before "ability" in the last sentence of the 3rd paragraph in section 1.
** JF RESPONSE -I have updated the wiki page.
* In Section 4, we say "Some of the vendors who have passed the conformance test case are listed on the OpenAjax Alliance's InteropFest wiki page", so David asks - "Why are only some of the vendors who have passed the conformance test listed?"
** JF RESPONSE - Given that the old InteropFest is no longer current and we do not have a replacement conformance test under development, I changed section 4 such that it first talks about the spec, the open source, and the test suite, and then refers to the InteropFest as something that occurred in the past that was helpful in allowing us streamlining and refining the feature set for OpenAjax Hub 1.0.
* In Section 5, we talk about futures and mention "Coordination of communications requests", to which David says: "Does this include invocation of server-side application services?  If so, try to mention the connection to SOA here."
** JF RESPONSE - Yes, of course, as a matter of policy, we always want to look for ways to hammer on SOA, but I don't see a good way to mention SOA without appearing artificial. If you have suggestions, please pass them on. But now that you have pointed out our list of Futures, I think we need fixes to list. We have made some good recent progress in some of the other OpenAjax committees, so there is more clarity about the future, which warrant updates to the list of bullets. Here is the new list:
*** Coordination of communications requests, including server-push using Comet techniques
*** Ability to achieve "secure mashups" (i.e., allowing for the convenience of mashups, but without sacrificing security)
*** Enabling data binding across Ajax libraries
*** Expanded list of standardized events and payloads