Agenda for the 2015 European face to face meeting May 20th Berlin

Agenda Wednesday May 20th.

8:30 - 10:00: Coffee and breakfast

10:00 - 12:30 Morning session

1. Welcome and intros from all attendees
2. Live start up logic and finding the edge - new features demo from Dan. Review of adaption logic - what is there today, how can it be improved.
3. EBU/IRT presentation and discussion around EBU-TT-D support for captioning.
4. StreamRoot will demo WebRTC/p2p media delivery integration with dash.js and also discuss changes/enhancements to dash.js to better facilitate p2p integration.
5. Current Xlink implementation, possible improvements and changes.
6. EME support by Greg
7. MP4box parsing by Cyril
8. Complexity - where does it lie - how to reduce?

12:30 - 13:30 - Lunch, demos, exhibition

13:30 - 18:00 Afternoon session

3. CDN hosting of minified files
4. Documentation - what is needed, who will create it, who will maintain it.
5. Multiperiod playback of test vectors with PTO in the first period.
6. Simplifying segment scheduling, pending queues to a just-in-time decision model.
7. Competition - Shaka player, reference player versus practical real-world player. Removing abstraction layer between DASH and others.
8. Error reporting / handling
9. 16:00 (Webex join from San Francisco by Brightcove/video.js) Proposal to rewrite dash.js in ES6 for clarity and extensibility (compiling out using babel to ES5 compliant code until all browsers support ES6 robustly). Brightcove to present on benefits.
10. Should we remove Dijon as a framework and use another? What would you suggest to make dash.js a first class, future proof, JS implementation?
11. Open sessions from attendees and overflow from prior agenda items.
12. Features for current releases, compliance against test vectors - Thomas slides.

18:00 - 19:30 - Get together, NETWORKING, DEMOS & EXHIBITION

19:30 - 22:00 Social Event

---

For archival purposes, these were the items previously submitted for inclusion:

1. Review of adaption logic - what is there today, how can it be improved
2. Documentation - what is needed, who will create it, who will maintain it.
3. CDN hosting of minified files
4. Current Xlink implementation, possible improvements and changes.
5. Multiperiod playback of test vectors with PTO in the first period.
6. Simplifying segment scheduling, pending queues to a just-in-time decision model.
7. Error reporting / handling
8. EBU presentation and discussion around EBU-TT-D support for captioning.
9. Live start up logic and finding the edge
10. Proposal to rewrite dash.js in ES6 for clarity and extensibility (compiling out using babel to ES5 compliant code until all browsers support ES6 robustly). Brightcove to present on benefits.
11. Should we remove Dijon as a framework and use another? What would you suggest to make dash.js a first class, future proof, JS implementation?
12. StreamRoot will demo WebRTC/p2p media delivery integration with dash.js and also discuss changes/enhancements to dash.js to better facilitate p2p integration.
13. Testing - what do we have? Do we need more?

Cheers

Will