- From: Ingar Arntzen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Mar 2019 15:34:31 +0000
- To: public-web-and-tv@w3.org
Chiming in with @cconcolato. In my view *event* is not the correct term here. It seems like *cue* is a better name for an object that is tied to a point or a region on the timeline. In my view, the term *event* should be reserved for named js callbacks, e.g. *enter* or *exit* which occur when the cue becomes *active* or *inactive* during playback or timeshifting. For reference, in the implementation of the the [sequencer](https://webtiming.github.io/timingsrc/doc/api_sequencer.html) for the [timingobject](https://webtiming.github.io/timingsrc/doc/api_timingobject.html) I define cue as an object with properties (key, interval, data). The *interval* defines a region on the timeline `(low, high)`. A point on the timeline is simply a special case of region, where both interval endpoints happens to be the same `low == high. I've noticed this kind of terminology confusion also other contexts, e.g. *dash events*, which are basically objects with a timestamp as far as I've understood. I'd recommend trying to maintain a distinctions between *data/objects* and *events* (essentially referring to state transitions in *data/objects*) -- GitHub Notification of comment by ingararntzen Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/issues/41#issuecomment-477212572 using your GitHub account
Received on Wednesday, 27 March 2019 15:34:34 UTC