Should we strive for getting a badge on the open ajax initiative for conformance [1] ?
"The term OpenAjax Conformance is shorthand for the set of conformance requirements that OpenAjax Alliance places on Ajax technologies, products, and applications. These requirements focus on a small number of simple but important aspects of Ajax usage, thereby providing the critical bits of Ajax interoperability that customers need, but in a manner that allows Ajax suppliers to continue to innovate and move forward with new technologies and products." Full Conformance The term "Full Conformance" is reserved for Ajax products that have sufficiently strong Ajax interoperability characteristics that there is high expectation that the given product can be used successfully and conveniently with other Ajax products as part of the same Ajax development task. For example, it is expected that if you have two Ajax libraries that are Fully Conformant, it will be reasonably straightforward and convenient to use the two libraries within the same Web page. >From a detailed technical perspective, an Ajax product or toolkit can claim Full Conformance to a particular version of OpenAjax Conformance (see Versions of OpenAjax Conformance, above) if it supports all of the Full Conformance Requirements associated with that version and that apply to that type of product (e.g., Ajax library, server product or IDE) in its default configuration. Only Ajax products and toolkits that are Fully Conformant can make the simple claim that they are "OpenAjax Conformant". (See Conformance Claims below.) Configurable Conformance The term "Configurable Conformance" is reserved for Ajax products support all of the same strong interoperability characteristics as for Full Conformance, except not in their default configuration. >From a detailed technical perspective, an Ajax product or toolkit can claim Configurable Conformance to a particular version of OpenAjax Conformance (see Versions of OpenAjax Conformance, above) if it can be configured in a simple and straightforward manner to support all of the Configurable Conformance Requirements associated with that version and that apply to that type of product (e.g., Ajax library, server product or IDE). Ajax products and toolkits that only support Configurable Conformance cannot make the simple claim that they are "OpenAjax Conformant", and instead must claim Configurable Conformance. (See Conformance Claims below.) Limited Conformance The term "Limited Conformance" indicates an Ajax product that has taken important steps towards Ajax industry interoperability by supporting many of the Conformance Requirements defined in OpenAjax Alliance Specifications. However, on the question of whether the given Ajax product can interoperate successfully and conveniently with other Ajax products, the answer is "it depends". Products that only support Limited Conformance usually require some amount of research and study at the detailed technical level to determine whether that product can interoperate successfully with other Ajax products with your particular Ajax development task. >From a detailed technical perspective, an Ajax product or toolkit can claim Limited Conformance to a particular version of OpenAjax Conformance (see Versions of OpenAjax Conformance, above) if it supports all of the Limited Conformance Requirements associated with that version and that apply to that type of product (e.g., Ajax library, server product or IDE). Ajax products and toolkits that only support Limited Conformance cannot make the simple claim that they are "OpenAjax Conformant", and instead must claim Limited Conformance. (See Conformance Claims below.) Given these descriptions, I think we can seriously claim that we are in Full Conformance - we can work with most if not all Ajax libraries available in the same page without any problems. Martijn [1] http://www.openajax.org/member/wiki/OpenAjax_Conformance -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
