API functions to capture media from local devices (camera and microphone) (currently in scope for the.camera, microphone, speakers (currently in scopeįor the Device APIs & Policy Working Group) API functions to explore device capabilities, e.g.Real-time communications between web browsers that will require specific client-side technologies: to take a pictureĪnd WebRTC's charter scope describes enabling Camera API an API to manage a device's camera e.g.The charter specifies a recommendation-track deliverable: The capture scenarios from DAP represent "local" capture scenarios that providing access to a user agent'sīoth groups include overlapping chartered deliverables in this space. The capture scenarios from WebRTC are primarily driven from real-time-communication-based scenarios, such asĬapturing live chats, teleconferences, and other media streamed from over the network from potentially One of the goals of the joint task force between the Device and Policy working group and the Web Real TimeĬommunications working groups is to bring media capture scenarios from both groups together into one unifiedĪPI that can address all relevant use cases. 5.12 Programmatic activation of camera app.5.8 Change user-selected device capabilities.5.6.1 Web platform post-processing toolbox.2.6 Incident on driver-download page (device fingerprinting with malicious intent).2.5.1.1 Showcase demo on local screen (screen as an local media input source).2.5 Conference call product debate (multiple conversations and capture review).2.4.1.2 Picture-in-picture (capture a composed video).2.4.1.1 Recording a sports event (simultaneous capture from multiple webcams).2.4 Video diary at the Coliseum (multiple webcams and error handling).
2.3 Find the ball assignment (video effects and upload requirements).2.2 Election podcast and commentary (video capture and chat).2.1 "Check out this new hat!" (photo upload with audio caption).An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. W3C maintains a public list of any patent disclosures ( Device APIs Working Group, Web Real-Time Communications Working Group) made in connection with the deliverables of the group that page also includes instructions for disclosing a patent. The group does not expect this document to become a W3C Recommendation. This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. It is inappropriate to cite this document as other than work in progress. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. Publication as a Working Draft does not imply endorsement by the W3C Membership. If you wish to make comments regarding this document, please send them to ( subscribe, archives). This document was published by the Device APIs Working Group and Web Real-Time Communications Working Group as a First Public Working Draft. It will eventually be released as a Note. Supported by the MediaStream Capture API. This document is intended to represent the consensus of the media capture task force on the set of scenarios A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at. Other documents may supersede this document. This section describes the status of this document at the time of its publication.
0 kommentar(er)
