VFtF 2009 06 11

W3C Forms WG Virtual Face to Face Meeting

Agenda for June 11, 2009

Hour 1: Disposition of Comments on XForms 1.1 CR

In order to make the request to advance XForms 1.1 to PR, we need to fill out the table at the following location: http://www.w3.org/MarkUp/Forms/2009/xforms11-PR-DoC.html

Hour 2: Create Team Plan for FPWD of XForms 1.2

Two implementers have already given indications of "future features" that they have already implemented as well as features for which they are seeing most urgent need:

PicoForms: http://lists.w3.org/Archives/Public/public-forms/2009Jun/0029.html

Orbeon: http://lists.w3.org/Archives/Public/public-forms/2009Jun/0031.html

While other implementers should feel free to add to the list, it can already be seen that there are targets for standardization in that just these two lists contain common items. In particular, there are common elements among the items listed as already implemented, so getting two interoperable implementations seems more quickly achievable.

The goal of this hour should be to scan through the features listed in the Future Goals and have various working group members select a single feature and take the action item to post some spec-like text during the week so that we can put that person's work on the agenda for the following week.

With an iterative development style like this, we should be able to pull together a delta spec as we did for 1.1 to server as a FPWD for XForms 1.2 within the current charter.

To help focus our discussion, the proposed shortlist was produced by combining urgency with perceived ease of implementation:

  • Context everywhere, context on bind elements
  • Custom XPath functions, e.g sumover(), also from host language e.g. javascript
  • Model improvements (optional, nested, external/src, exceptions)
  • Better support for submission and model patterns for multipage web apps
  • Setting submission method default to "get"
  • Ability to suppress RRRR on submission completion and/or initialization
  • JSON submissions
  • submission to a "new" window
  • Data driven switch
  • case() function
  • Dialogs
  • mediatype="text/html" on textarea for rich text content
  • Better upload control (better control of metadata, instant upload submission to server)
  • Enable use of XPath 2.0
  • XML Events 2
  • Node 'create' functions (origin variation on insert?)
  • Setting event contextinfo as part of dispatch

Hour 3: Focus on External Model and Submodel Problem

To some extent, this hour will be a continuation of the previous hour, except that we need to get to some technical decisions about how we are going to proceed with the specific problem of elaborating how models are injected into the document so that the person who takes the action item to write this up will have some clearer direction.

These two issues are put together because it seems that each is necessary but not sufficient for solving authoring requirements related to having multiple web pages that operate over a common model.

Hour 4: Focus on Submission Improvements

There is a cluster of "low-hanging fruit" in the area of more submission improvements. The goal of this hour is to get as far through the discussion of these topics as the hour permits, and then we can pick up the discussion in the following week's vFtF day.

  • Setting submission method default to "get"
  • Ability to suppress RRRR on submission completion and/or initialization
  • JSON submissions
  • submission to a "new" window

Hour 5: Focus on User Interface Improvements

There is a cluster of "low-hanging fruit" in the area of user interface improvements. We've had some good discussions about some of these topics recently, and some are already implemented in various ways by multiple implementers. The goal of this hour is to get as far through the discussion of these topics as the hour permits, and then we can pick up the discussion in the following week's vFtF day.

Overall, the largest and most urgently needed feature is "Dialogs". We need a team member who can pick this up and really own it down to the deepest technical details that we know are lurking below the surface of this feature. Here's a chance to make a big difference!

  • Data driven switch
  • case() function
  • Dialogs
  • mediatype="text/html" on textarea for rich text content
  • Better upload control (better control of metadata, instant upload submission to server)
Last modified on 25 February 2010, at 15:18