Re: Next steps for Coremob-2012 and the group.

I did not make your Tuesday deadline, Jo, but here is some input.

We will be stepping up our focus on CoreMob in 2013, and doing what we can to drive the alignment/synergy with the Web Testing IG. The importance of CoreMob and its role in helping to shape expectations for HTML5 was mentioned prominently in our CTO's keynote at the recent AT&T 2013 Developer Summit, attended by ~2700 developers over 3 days.

There is a Web Testing meeting in Mountain View on Jan 29 to which we will contribute an analysis of current test coverage per CoreMob 2012. This is intended to help in planning tactical efforts to close the gaps. I've put a draft of the analysis on the CoreMob wiki [1]. The linked spreadsheet includes:

*         How CoreMob-referenced specs/requirements are covered by:

o   Ringmark

o   tests available under the W3C Test Framework [2]

o   other tests hosted by W3C and elsewhere

*         Looking the other direction, how the current (as of two days ago) set of tests in Ringmark map to CoreMob 2012.

These are initial/rough assessments intended to assist in:

1)      Assessing how well current "production-ready" test suites cover CoreMob 2012.

2)      Where there are gaps, explaining them and developing priorities to close them.

3)      For the Web Testing IG, helping to create an overall map to where the current test assets are, and identify which are migrating toward the W3C Test Framework (and how this is occurring).

Doing this analysis raised a number of other questions that I hope to document and resolve as part of the Web Testing IG; clearly W3C has a ways to go to flesh out the coverage and adopt more consistent processes for test management.

For CoreMob 2013, our focus will be to start the dialog early on:

*         What CoreMob 2012 features in hindsight really weren't ready, e.g. based upon current implementation status and test experience

*         What new features might be key to reference in CoreMob 2013. Some initial proposals for consideration will include:

o   WebRTC

o   getUserMedia (GUM)

o   HTML Encrypted Media Extensions and Media Source Extensions

Of these, WebRTC and GUM seems to be the most likely candidates. Of course what's feasible for CoreMob 2013 may look completely different as we get closer to Q3.

[1] http://www.w3.org/community/coremob/wiki/CoreMob2012_Test_Coverage
[2] http://w3c-test.org/framework/app/suite

Thanks,
Bryan Sullivan