API group status and reminder

If the protocol call tomorrow has extra time at the end we can use that to review any of the API group's work we haven't got to yet (we didn't get to Debbie's work in the last API call and only got part way through Bjorn's proposal on events).  As a reminder, the work items that were due 2 weeks ago which we still haven't seen on the list (those people with open assigned late tasks are on the to list above) are the following:

Raj, by 12 noon ET Tuesday the 28th of June, please distribute to the list the API relevant requirements and design decisions (the equivalent to what Marc did for the protocols group).

Charles, by 12 noon ET Wednesday the 29th of June, please to the list a first draft of API and IDL for items 10, 11, and 12 [The API hooks related to actually doing a synthesis transaction; The synthesis events that are raised and the associated handlers and data (same caveat about timing as with 6); The API hooks for controlling synthesis, if any (pause, resume, play, etc.)].

Dan Burnett, by 12 noon ET Wednesday the 29th of June, please to the list a first draft of API and IDL for item 13 [The API to do text based recognition].

Olli, by 12 noon ET Wednesday the 29th of June, please to the list a first draft of API and IDL for item 8 [The API hooks related to hooking up with the capture system].

The ones we have seen already are:

Dan Druita, by 12 noon ET Wednesday the 29th of June, please to the list a first draft of API and IDL for item 3 [The API hooks relating to "setting up" or "preparing" or "checking the capabilities" of a request (both recognition and TTS)].

Debbie, by 12 noon ET Wednesday the 29th of June, please to the list a first draft of API and IDL for items 4 and 5 [The API hooks for specifying grammars and also other recognition properties (both what these properties are, and how to specify them); The API hooks for getting speech results back (both the EMMA XML and text representation that was in a couple of proposals and Bjorn outlined, but also the continuous results that we talked about at the F2F - this also possibly covers feedback functionality)].

Bjorn, by 12 noon ET Wednesday the 29th of June, please to the list a first draft of API and IDL for item 6 [The recognition events that are raised and the associated handlers and data (including any semantics about time stamps and other related information we covered at the F2F)].

Michael, by 12 noon ET Wednesday the 29th of June, please to the list a first draft of API and IDL for item 2 [The markup associated with the recognition element and any associated properties and api (I.e., the element, for label, implied behavior)].

In addition we still have unassigned items of:

Item 7:  The API hooks related to the protocol for both speech and synthesis (both what speech service to use, and also anything else the protocol team identifies as a need).  This might have to wait until the protocol is further along (and might also be something someone on the protocol team wants to take).

Item 9: The API hooks associated with actually doing the recognition.  (This may, or may not, be different than a combination of 3 and 4 above).

Item 14: The API to do a combination of bargeable synthesis and recognition.  This was a little controversial, but we discussed it at the F2F.

Item 15: The API hooks to do continuous recognition (both open microphone as well as dictation).  This was covered some at the F2F and may just be part of 3, 4, and 9 above.

I don't like to nag, and I know it is summer/vacations/etc. for lots of people, but if we want to have a successful API proposal as a group before the end of our current charter we'll need to get through all of these very quickly.  If you have one of the above items open, please send it in to the list ASAP.