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:

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.

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)