From MemberWiki

Contents 1 Minutes from Declarative Markup committee teleconference June 14, 2006 1.1 Attendees 1.1.1 Absent 1.2 Agenda 1.3 Topic: Use Cases and Requirements 1.3.1 Standardize on one markup language or allow multiple markup languages 1.3.2 Support for top-level markup approaches 1.3.3 Content types

Minutes from Declarative Markup committee teleconference June 14, 2006

Attendees

• "Adam Peller" <apeller@us.ibm.com>
• "Alex Russell" <alex@dojotoolkit.org>
• "Anil Sharma" <anil@vertexlogic.com>
• "David Frankel" <david.frankel@sap.com>
• "Eddie O'Neil" <ekoneil@bea.com>
• "Jim Grandy" <jgrandy@openlaszlo.org>
• "Jon Ferraiolo" <jferrai@us.ibm.com>
• "Lindsey Simon" <lsimon@finetooth.com>
• "Ted Thibodeau" <tthibodeau@openlinksw.com>
• "Javier Gallego" <Javier.Gallego@softwareag.com>
• "Phil Berkland" <berkland@us.ibm.com>
• Alex Escalante from Jackbe

Absent

• "Coach Wei" <coach@nexaweb.com>
• "Dave Johnson" <djohnson@ebusiness-apps.com>
• "David Temkin" <temkin@laszlosystems.com>
• "Eric Nguyen" <ericn@mercedsystems.com>
• "Gustavo Munoz" <gustavom@jackbe.com>
• "Jeremy Chone" <jchone@adobe.com>
• "John Crupi" <john.crupi@jackbe.com>
• "Ken Fyten'" <ken.fyten@icesoft.com>
• "Kingsley Idehen" <kidehen@openlinksw.com>
• "Mark Schiefelbein" <mark@backbase.com>
• "Michael Peachey" <mpeachey@tibco.com>
• "William Shulman" <will@mercedsystems.com>

Agenda

• Review Declarative Markup Use Cases and Requirements
  • http://www.openajaxalliance.org/member/wiki/index.php/Markup_Use_Cases_And_Requirements

Topic: Use Cases and Requirements

Most of the meeting was spent reviewing the use cases and requirements document and updating the wiki page in real time as the discussion occurred. Check the change history on the wiki page for further details.

The meeting ended while discussing what requirements we need in the area of Side Effects. The remaining notes are some comments that were not captured on the wiki page.

Standardize on one markup language or allow multiple markup languages

DavidF quoted David Boloker about how we might converge on a single markup language within a year. Jon said that this might not be exactly what David meant and that previous discussions within the Open AJAX Alliance talked about the need to allow toolkit innovation, which leads to allowing for different markups. Others re-inforced Jon. Result was reaffirmation that we will target solutions which allow integration of different markup languages.

Support for top-level markup approaches

There was considerable discussion on various things relating to markup languages that exist at the top level and want to be "on top" and at the root level of the application. Part of the discussion was whether we needed special requirements for this case or whether this was already covered by the general use case for allowing toolkit integration. For now, we are leaving a SHOULD requirement for integration with top-level markup languages, but it isn't clear whether we have a good grasp on whether there are any special issues with top-level markup languages or even how to describe a top-level markup language.

Content types

There was some discussion, spurred by the question of requiring support of XML, about the content type within HTTP headers and the initial markup included at the top of Ajax applications. The Ajax community has adopted certain approaches that work for now. Jon suggested that we document these approaches and evangelize to the browser vendors that they should not changes their browsers to break applications that use these approaches. Alex agreed. Jon will find a place on the wiki to capture this. (See http://www.openajaxalliance.org/member/wiki/index.php/Best_Practices)