Position Statements

Topics you are interested in discussing at FOMS:

  • A case study on web subtitle formats
  • Getting (web) media onto TVs? and other devices using Presentation API and or Open Screen Protocol
  • Delivery of media to browsers using a QUIC API
  • Delivery of live media to browsers using Media Source Extensions (MSE) or MSE with low-latency controls or low-level video decoder objects
  • Uses of Web APIs? for video encoders and decoders separate from WebRTC and MediaRecorder?
  • Picture in picture - captions&Ads support.
  • Autoplay - one api to get the capabilities for a session
  • Optimizing video sharing & transcoding on mobile
  • Managing audio focus on the web using the Audio Focus API
  • A standard for Quality of Experience (QoE) Metrics (we have a published version! Check it out and come with comments) https://github.com/cta-wave/R4WG20-QoE-Metrics
  • Audio focus audio play apis
  • MSE spec, MSE with workers.
  • bitstream analysis and tools.
  • updates on media capabilities and low latency playback.
  • browser API feature requests.
  • casting features; open screen protocol; brining casting streaming capabilities cross devices.
  • "open screen", low latency video streaming. Quick transport p2p
  • capture and webRTC, captions (tomorrow)
  • web facing APIs? (captions)
  • autoplay spec; high performance cross platform code.
  • low latency streaming.
  • video analytics, cross browser compatibility.
  • LHLS
  • Android media stack; transcoding
  • autoplay api
  • realtime monitoring
  • text tracks
  • community conversation.
  • game consoles & streaming devices.
  • VTT spec - impending date?
  • vectorly .. svg video codec. white paper; javascript library
  • video element extensibility.
  • APIs? to switch. dash and advertising - multi-period