- From: Ingar Mæhlum Arntzen <ingar.arntzen@gmail.com>
- Date: Wed, 6 Nov 2024 14:26:32 +0100
- To: Chris Needham <chris.needham@bbc.co.uk>
- Cc: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>, public-webtiming@w3.org
- Message-ID: <CAOFBLLp5A6nzzs0hBiJ73n0AG7aBYNrfAq6gznmhJ4TbMVbEqA@mail.gmail.com>
Dear Chris and all. Thanks again for inviting to this meeting! To reiterate some key points from my side. - I regard "timing model for the Web" as a topic of general interest for the Web community at large. Though the activity level in the CG group has been low, timing is a recurring theme across many groups and application domains. The meeting disussion also included additional examples of related discussions and/or intitiatives in other groups. - I regard the "MEIG" as the IG where this topic most naturally belongs. - I'm ok with closing the CG group, but I'm of course hopeful that some of the key ideas can live on with the IG. Some takeaways from the CG work - Timing is the most imporant part. The timing object is a suggestion for a minimal, common representation of logical/virtual timeline playback (support for acceleration can be dropped), to be used for coordination across components and frameworks within a Web page, or across Web-pages hosted by different devices. - Opening up for distributed sync of timing objects is a key purpose of the timing object, but there is no suggestion for a particular protocol or approach for this. This is intentially left open, so that organisations and developers can explore different options. Agreement on a common timing object would still remains highly valuable, as it provides separation between application code and the particular approach to distributed sync. - For maximized utiltity, we recommend that time representation is not bundled with other concepts, e.g. session management. - Syncing media elements precisely in reference to a logical clock is a hugely important case, and the current complexity of doing this is seen as a showstopper for a wide variation of applications, both in the entertainment/media domain, and in other industries (e.g. playback of IoT sensor data visualizations along with captured video). Things to do from here - A testing suite for the "syncability" of media elements would be useful, as suggested by Louay. I've attached two technical reports which Njål and I made back in 2014/15. Best regards, Ingar Arntzen ons. 6. nov. 2024 kl. 13:10 skrev Chris Needham <chris.needham@bbc.co.uk>: > Dear all, > > The minutes from this week's MEIG meeting are available [1]. > > Thank you to all who joined, and in particular Ingar, for joining us as > Chair of the Multi-Device Timing CG. > > Our next meeting is scheduled for Tuesday 3 December at 15:00 UTC. Agenda > details TBC. > > Many thanks, > > Chris (for the MEIG co-chairs) > > [1] https://www.w3.org/2024/11/05-me-minutes.html > >
Attachments
- application/zip attachment: norut_tromso_rapport_.zip
Received on Wednesday, 6 November 2024 13:26:55 UTC