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

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

From: <Frederick.Hirsch@nokia.com>
Date: Fri, 7 Dec 2012 16:36:44 +0000
To: <w3b@chaals.com>
CC: <Frederick.Hirsch@nokia.com>, <public-device-apis@w3.org>
Message-ID: <1CB2E0B458B211478C85E11A404A2B2701853238@008-AM1MPN1-033.mgdnok.nokia.com>

Thanks for raising Last Call issues on HTML Media Capture - thinking about them has helped us improve the specification.

We have an update to HTML Media Capture with the primary change being to make capture a boolean attribute. In conjunction with this change additional examples have been added.

You had two Last Call comments on HTML Media Capture [1] before these changes:

(1) LC-2641 allow hint as to which camera to use

We changed the meaning of the capture attribute - it is now a boolean ( thus there are no keywords defined with it). The accept attribute defines the requested MIME type and if present the capture attribute indicates to use the device built-in capture mechanism to obtain content of that MIME type. Thus that mechanism could have a user interaction to determine which device, but that would be implementation dependent.  I could also envision different MIME types for different camera choices (though maybe that would probably require standardization elsewhere).

Given the wide range of possible accept content types, it probably does not make sense for the HTML Media Capture specification to define capture choices at the device (and the current specification does not provide a means to do so).

Do you agree that with the latest set of changes this issue is moot?    (Keywords previously implied finer granularity  but are no longer specified)
.(2) LC-2640 clarify that the capture attribute can be in markup, not only in examples

We addressed this in a number of places (for formatted version of quoted text see draft link below):

Introduction: "The HTML Media Capture specification enables web page authors to declaratively specify the upload of audio, video and still images by adding a new attribute to the HTML input element."

Terminology:  "The input element, HTMLInputElement interface, accept attribute, and File Upload state are defined in [HTML5]."

This indicates that input is an HTML element.

Examples: Examples 1,2,3 show declarative form without requiring Javascript;  example 4 shows use of markup without form and examples 5-7 show how this can be processed.

Does these changes adequately address this issue?

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 )

Please respond (including the list) indicating if these two Last Call issues can be closed with these changes.


regards, Frederick

Frederick Hirsch, Nokia
Chair, W3C DAP Working Group

[1] https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-html-media-capture-20120712/doc/
Received on Friday, 7 December 2012 16:37:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:47 UTC