OpenAjax Metadata Specification v07 ChangeLog

From MemberWiki

Jump to: navigation, search

This wiki page holds a saved snapshot (for future historical reference) of a portion of the v0.7 draft of the OpenAjax Metadata 1.0 Specification. This wiki page is meant to be a read-only capture of the OpenAjax Metadata spec at a moment of time.

The base wiki page that provides an index for all working drafts of the OpenAjax Metadata specification is at http://www.openajax.org/member/wiki/OpenAjax_Metadata_Specification. The base wiki page for this 0.7 version of the draft specification is at http://www.openajax.org/member/wiki/OpenAjax_Metadata_Specification_v07.

The text below holds the v07 version of the OpenAjax Metadata spec.



Here is the proposed way for the IDE WG to edit this specification:

  • All textual content that has normal text properties (i.e., black) and has no colored status text (e.g., does not say Tentatively approved or Approved) represents preliminary proposed text that requires further review and discussion.
  • Members of OpenAjax Alliance are encourage to place inline comments into this document, preferably by identifying your name or initials before your comment, such as "Mary: This bullet should be moved above previous bullet".
  • When an item has been deemed complete by the WG chair due to committee consensus, then the annotation Approved will be placed at the end of an approved block of text (e.g., paragraph or bullet). Note that during the development phase of this specification, the group can change its mind and "un-approve" text that was previously approved.
  • When an item has been deemed near complete by the WG chair due to committee consensus, but further review is necessary (e.g., review final wording), then the annotation Tentatively approved will be placed at the end of given block of text (e.g., paragraph or bullet).
<--previous       contents--^       next-->


Contents

Appendix B: Change Log

Changes around 2008-11-18

Resolutions from 20081118 phone call

  • Add 'static' to <class>
  • Add 'fromProperty' and 'toProperty' to <mix>
  • Add 'unregisterCallbackPattern' to <handerFunction>

Changes around 2008-11-13

  • Move <config> and <configs> elements to Properties chapter. Expand the description of those properties and include examples.
  • Add <handerFunction> sub-element to <event>, with attribute 'registerCallbackPattern'.
  • Add 'registerCallbackPattern' description to Properties chapter, including the new Template:Event pattern variables.
  • Per decision at 2008-11-04 telecon, support lowercase versions of ECMA built-in datatypes and HTMLElement, Node, Window, Document. Reorganize and cleanup. Add precedence order for checking different datatypes.

Changes around 2008-11-04

  • Remove <field>/<fields>; instead, add 'managed' attribute to <properties>.
  • Add <config> and <configs> elements to allow declaration of object literals that can be used to pass configuration options as a parameter to a constructor or method
  • Allow <property> children for objects that can have 'datatype' of "Object"
  • Allow <parameter> children for objects that can have 'datatype' of "Function"
  • For 'datatype', allow lowercase versions of built-in ECMA types (e.g., sllow both String and string) and allow 4 new HTML types: HTMLElement, Document, Window and Node. Allow tools to attempt to figure out what to do with datatype values that don't match one of the built-in types.
  • Change <event> element to remove child elements <parameter> and <returnType>
  • Remove 'auto' option on 'includeRef' on <require>.

Changes around 2008-11-01

  • Major editing changes to the <require> element to take into account discussion over the past couple of months. Some of these editing changes were highly overdue. Among the specific changes:
    • 'src' attribute is now required
    • New text about how IDEs or mashup editors can relocate Ajax libraries and can share libraries across multiple widgets, with a recommendation to use the highest version number for a given library
    • New text that how to define metadata when your widget uses an Ajax library
    • Recommend the use of CDNs for popular Ajax libraries
    • Updated text about the 'target' attribute
  • Change schema to allow inline message bundles.
    • Also did some editorial work on the Localization chapter.
  • Changed 'datatype' to allow HTMLElement and permit IDEs and mashup tools to apply heuristics if they encounter a datatype value that doesn't align with any of the built-in rules
  • For <constructor>, add text that says that a <returnType> must be specified.
  • 'usage' attribute is now an optional attribute whose default value is 'required'

Changes on 2008-10-16

  • Updated the examples at the top of the widget and API chapters to align with latest changes to the schema.

Changes from 2008-09-23 IDE WG phone call

  • We changed <useragent> and <useragents> to <userAgent> and <userAgent> to go for greater consistency in our use of camel-casing.
  • Added a red-colored note to widgets chapter about how we are looking into declarative ways of describing widget constructor and an Object that holds the list of properties that is passed into the constructor to see if there is a way to support widgets without requiring widget authors to create a wrapper class
  • Added a red-colored note to properties chapter about how we are working on detailed rules for expressing default attributes using JSON notation

Previous changes

Previous spec changes have not been logged here in the change log. To research the changes that happened earlier:

  • You can examine the Recent Changes log for the full OpenAjax Alliance wiki () and look for changes to pages whose names begin with "OpenAjax Metadata Specification".
  • You can go through the individual pages that make up OpenAjax Metadata Specification and click on the history tab.
Retrieved from "http://www.openajax.org/member/wiki/OpenAjax_Metadata_Specification_v07_ChangeLog"
Personal tools