W3C home > Mailing lists > Public > public-device-apis@w3.org > December 2012

[html media capture] proposed (new) resolution of your HTML Media Capture Last Call Comments (Please respond)

From: <Frederick.Hirsch@nokia.com>
Date: Fri, 7 Dec 2012 15:42:19 +0000
To: <schepers@w3.org>
CC: <Frederick.Hirsch@nokia.com>, <public-device-apis@w3.org>
Message-ID: <1CB2E0B458B211478C85E11A404A2B2701852DB7@008-AM1MPN1-033.mgdnok.nokia.com>

I think the DAP Working Group has a change to the HTML Media Capture specification that should satisfactorily address the Last Call issues you raised.  Thanks very much for raising the issues and following through.

The change is to make the capture attribute a boolean with the meaning that if it is present (true) then the user agent will invoke the appropriate device capture mechanism based on the MIME type, it it is able (and if not act as if the capture attribute were not present).

This has the following implications:

LC-2637 : camcorder keyword may conflate audio and video, suggest capture is list of strings

No longer conflates items or is confusing, no longer need for strings - what is captured is specified only by MIME type.

LC-2638 : add examples

Examples have been added and extended to clarify how HTML Media Capture may function in different ways

LC-2639 : Why 'camcorder' instead of 'videocamera'? 

moot - we got rid of the keywords entirely

See the latest editors draft for details: http://dev.w3.org/2009/dap/camera/

(there is also a diff, http://dev.w3.org/cvsweb/2009/dap/camera/Attic/unofficial.html.diff?r1=1.3;r2=1.4;f=h )

Does this latest change address your Last Call comments? 


regards, Frederick

Frederick Hirsch, Nokia
Chair, W3C DAP Working Group

Received on Friday, 7 December 2012 15:42:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:56 UTC