- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Mon, 9 Jun 2014 18:28:07 +0000
- To: "mark a. foltz" <mfoltz@google.com>
- CC: Mark Watson <watsonm@netflix.com>, "Bassbouss, Louay" <louay.bassbouss@fokus.fraunhofer.de>, "public-webscreens@w3.org" <public-webscreens@w3.org>, Mark Scott <markdavidscott@google.com>, "Rottsches, Dominik" <dominik.rottsches@intel.com>, Bob Lund <B.Lund@cablelabs.com>, Philipp Hoschka <ph@w3.org>, Daniel Davis <ddavis@w3.org>
On 09 Jun 2014, at 19:08, mark a. foltz <mfoltz@google.com> wrote: > MarkW, I am happy to help with this, as our project has implemented this ability for Cast and DIAL. MarkFo - thanks for volunteering to help! > Anssi, it would be helpful to be specific as to what you expect to be delivered to the group: > > (1) Use cases demonstrating the feature > (2) API proposal or proposals > (3) Interoperability test suites or requirements per earlier thread > (4) Prototype implementations? Anything that helps the group make progress and be productive with this issue is good. I’d start with use cases and requirements, scrutinize them, ensure they are well understood and address real problems end users face. Then I’d move on to evaluate existing solutions, and experiment with new solutions if the existing ones do not address the requirements. There’s no strict format how to do this. You can use e.g. the W3C wiki or anything else that works for you to document your findings as long as you keep the group in the loop (e.g. ping the mailing list for feedback). Thanks, -Anssi
Received on Monday, 9 June 2014 18:28:40 UTC