[html-media-capture] DAP Proposed resolution of LC-2640 issue to clarify capture attribute can be added in markup

Chaals

At our DAP F2F in Lyon we discussed the Last Call comments related to the HTML Media Capture specification [1]. One action we took was to clarify the abstract and introduction - the changes in this revision should address your Last Call comment , LC-2640 [2],  where you suggested that we clarify that the capture attribute can be added in markup rather than programmatically.

The revised Abstract and Introduction now state:

[[
Abstract

The HTML Media Capture specification defines HTML form extensions that facilitate user access to media capture capabilities of the hosting device. These form extensions enable the upload of still images, video, and audio directly from a device capture mechanism but capture the default offered by the device, providing limited control over what is captured. More detailed control, including management of related streams, is provided by the Media Capture and Streams specification [GETUSERMEDIA<http://dev.w3.org/2009/dap/camera/#bib-GETUSERMEDIA>].

1. Introduction

This section is non-normative.

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. This enables unified capture and upload from the device capture device without requiring a user to save a file and then upload it in separate steps.

Such an approach does not provide detailed user control over capture, so use cases requiring correlating specific individual audio and video streams may be met by using another specification, Media Capture and Streams [GETUSERMEDIA<http://dev.w3.org/2009/dap/camera/#bib-GETUSERMEDIA>]. Access to media streams from the hosting device is out of scope for this specification.

This specification extends the HTMLInputElement<http://dev.w3.org/2009/dap/camera/#dfn-htmlinputelement> interface with a new capture<http://dev.w3.org/2009/dap/camera/#dfn-capture-1> attribute. The capture<http://dev.w3.org/2009/dap/camera/#dfn-capture-1> attribute enables content authors to indicate the media to be captured and uploaded, specifically still images, video, and audio. Conformant user agents provide their users a more seamless access to the above-mentioned media capture capabilities of the hosting device.

]]

The sentence "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. " should address the concern you noted.

We also added a clarification to the beginning of the Note in section 5.1 [3]:

 NOTE
Use of the capture attribute as defined in this specification enables integrated capture and upload of audio, video and still images, and complements the following behavior defined in the File Upload<http://dev.w3.org/2009/dap/camera/#dfn-file-upload> state<http://dev.w3.org/2009/dap/camera/#dfn-state> [HTML5<http://dev.w3.org/2009/dap/camera/#bib-HTML5>]: User agents may use the value of [the accept] attribute to display a more appropriate user interface than a generic file picker. For instance, given the value image/*, a user agent could offer the user the option of using a local camera or selecting a photograph from their photo collection; given the value audio/*, a user agent could offer the user the option of recording a clip using a headset microphone.

Do these changes adequately address your concern? If so we shall close the issue, LC-2640. If not, do you have any suggestions on how to make it clearer?

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Chair, W3C DAP Working Group

[1] http://dev.w3.org/2009/dap/camera/

[2] https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-html-media-capture-20120712/2640

[3] http://dev.w3.org/2009/dap/camera/#attributes