This is YOUR Web

Outline

• W3C & the Web platform
• WebRTC media pipeline demo
• Making it yours
• Deep dives in technical topics?

W3C

• Standards setting body for the Web
• 400 Members, with most key players in ICT
• 70+ staff, mostly technical
• Founded by Web inventor, Tim Berners-Lee
• Key foundational principles:
  1. Interoperability
  2. Openness
  3. Royalty-free patent policy

w3.org/mob

Application Foundations

Why contribute?

The web's future still depends on us. All of us must use our creativity, skills and experience to make it better: more powerful, more safe, more fair and more open.

Tim Berners-Lee on the Web at 25

Proposing a use case

• Post it to SpeciFiction
• Follow up on questions / feedback

All W3C APIs are perfect

Unless you agree with that…

• Send feedback on W3C APIs as they get developed
• API usability
• API fitness to use cases
• bugs

How to send feedback?

• Make sure you’re reading the latest spec
• Post to the right mailing list (linked from spec)
• Post to the right bug tracker (linked from spec)
• Send pull request (for specs on github)

All W3C specs are perfectly implemented in all browsers

Unless you agree with that…

• File / vote for bug in browser bug trackers
• Help pinpoint interoperability issues with test cases

How to write test cases

• Web platform Test Suite on Github
• Test The Web Forward documentation
• Non trivial, but very rewarding

W3C APIs are finalized so fast!

Unless you agree with that…

• More work to be done than people to do it
• Getting contributions to spec development helps a lot
• W3C groups operate on public mailing list
• W3C specs increasingly developed on Github
• Work that doesn’t fit in any existing Working Group can be started in Community Groups

How to contribute to specs

• Subscribe to the mailing list
• Watch the github repo
• Participate to issue discussions
• Make pull requests
• Time consuming, difficult, but rewarding
• For Working Groups, Invited Expert or Membership required for substantive contributions

European SMEs?

• Interested in being interviewed on your needs from the Web platform?
• Get in touch!

Thanks!

• Slides: http://www.w3.org/2015/Talks/dhm-apis-w3ctrack/
• Twitter: @dontcallmedom
• Email: dom@w3.org

This project has received funding from the European Union’s Seventh Framework Programme for research, technological development and demonstration under grant agreement 611327

Device Interaction

Sensors already available:

• geolocation
• accelerometer
• compas
• gyroscope
• camera
• mic
• battery

In development

• Generic pattern for sensor APIs
• proximity
• ambient ligt
• NFC
• Bluetooth (incl. BLE)

What’s missing for you?

Application Lifecycle

Example: news app

Native	Web
Installable (engagement+)	No installation needed (shareability+)
Available offline, background sync	Primarily on-line experience
Deeper hardware integration	Privacy guarantees
Alerts (engagement+)
Rich	Reach

Install

• ⌛ Manifest for Web apps:
  • icon in app launcher
  • splash screen
  • UI mode (e.g. fullscreen)
  • Catch https://news.example.org URLs

Key: ✓ Existing solution; ⌛ in progress; ❓ early/exploratory work; ✗ no active work

Share

• ⌛ Packaging Web content

Offline

• ✓ Application Cache (but not without issues)
• ⌛ Service Worker
  • Offline
  • Increased on-line perfs
  • esp. in poor network conditions
  • HTTPs-only
• ❓ Background sync
• ❓ Storage quota management
• ❓ Upgraded storage (WHATWG)

Notifications

• ✓ Local Notifications
• ⌛ Push notifications (but open protocol missing)
• ❓ Geo-based notifications (geofencing)
• ❓ Scheduled tasks

Hands-free usage

e.g. cooking recipe

• ❓ Wake-lock API

Reduced resources usage

• ✓ Detect foreground activity
• ⌛ Detect battery level

More lifecyle events?

• ✗ App lifecycle and events (sysapps)
• ✗ Events vary from one device to another (e.g. cars)

Feedback needed

• Is this the right scope?
• Are there work items that need accelerated development?
• What are the next big things we need to be looking at?

Media & Real-Time Communications

Media & Real-Time Communications

A/V rendering

• ✓ <audio> & >video> with HTMLMediaElement API
• ⌛ Multi-screen rendering (2nd Screen WG)
• ⌛ Multi-audio output rendering (WebRTC/DAP)
• ❓ Local Network Multimedia integration (DAP)
• ❓ Cross-device sync (Web Timing CG)
• ✗ Color management

Key: ✓ Existing solution; ⌛ in progress; ❓ early/exploratory work; ✗ no active work

Open issues

• <audio> & >video> are magical black boxes
• Many groups “monkey-patch” HTMLMediaElement
• Multiple mechanisms with same objectives (2nd Screen vs Audio Output API)
• Security model for local network integration

A/V Processing

• ⌛ Protected Media (EME)
• ✗ JS-based codecs

Open issues

• Controversies around DRM
• RF Video codec?

A/V adjuncts

• ✓ SVG, CSS, canvas graphics
• ⌛ Common animation timeline (CSS/WebApps)
• ⌛ Captioning (WebVTT, TTML)
• ⌛ In-band metadata
• ❓ Sync with any timed content (Web Timing CG)

Open issues

• SVG / HTML media overlap
• Overlap / incompatibilities between WebVTT and TTML

Media Control

• ✓ <audio> & >video> with HTMLMediaElement API
• ⌛ Media Keys (DOM 3 Keyboard events)
• ❓ Time-shift live broadcast with MediaStream recording
• ❓ Tuner control (TV control CG, Auto WG)
• ❓ Media Session (WhatWG)

Media Transmission

• ✓ Chunk-based transmission (HTTP)
• ✓ Streaming via Media Source Extensions
• ⌛ P2P CDN (WebRTC)
• ❓ Broadcast integration (TV control CG)
• ❓ Deeper network integration (WebMob)

Media Capture

• ⌛ From camera / mic (WebRTC/DAP)
• ⌛ From current Web page (WebRTC/DAP)
• ⌛ From screen (WebRTC/DAP)
• ✗ Timed textual alternative

Open issues

• Privacy for media capture
• “Fingerprinting” associated with local devices info
• Security for screen sharing

Media Transmission

• ⌛ P2P (WebRTC)

Open issues

• WebRTC / ORTC as alternatives approaches to P2P connection establishment
• Privacy challenges around private IP addresses

Media Capture

• ⌛ Delegated image capture (DAP)
• ⌛ Recording (WebRTC/DAP)
• ❓ Still Image capture (WebRTC/DAP)

Media Editing

• ✓ Audio processing (Web Audio API)
• ✓ Drawing capabilities (canvas, SVG)
• ✓ CPU-based Image/Video processing (canvas)
• ❓ End-to-end video lifecycle in “Glass-to-glass” Task Force of Web&TV IG
• ✗ GPU-based video processing (discussions in WebRTC)

Media Capture

• ❓ 3D camera capture

Media Processing

• ✓ 3D-graphics and effects (WebGL)
• ✗ GPU-based video analysis (e.g. face detection, object recognition)

Next steps

• HTML 2015 plan includes coordination of media work
• Seeking new sources of use cases
• Web & TV IG manages pipeline of new work
• Potential WebRTC-NG workshop?

Feedback needed

• Is this the right scope?
• Are there work items that need accelerated development?
• What are the next big things we need to be looking at?
• Who should we reach out to to collect new use cases?