search

w3c / tvcontrol-api

TV Control API specification - https://w3c.github.io/tvcontrol-api/
10 stars 11 forks source link

Channel#nextEvent and onCurrentEventChanged missing #33

Open mprobst-irt opened 8 years ago

mprobst-irt commented 8 years ago

The TVChannel object should have either a nextProperty property or method or currentProgram should return a sequence. In addition an event should be defined which fires when currentProgram changes.

As background, DVB system have EIT p/f which is the current and the next event which can signal the current events on the channel very accurately. They are different to EIT schedule which is the EPG data.

mprobst-irt commented 7 years ago

any opinion?

chrisn commented 7 years ago

I assume you mean nextProgram, rather than nextEvent or nextProperty?

I agree about the need for an event on program change. If this event can only be generated for channels currently being streamed, it would be better for this event to be in an interface more closely related to the TVMediaStream - i.e., the revised TVTuner concept described in https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-259467862 and here - rather than TVChannel.

If we introduce properties to get the current and next programmes, how should these relate to the EPG information available through TVChannel::getPrograms()? Should they be exposed through the revised TVTuner, or from TVChannel?

mprobst-irt commented 7 years ago

Nextproperty was a typo

Event comes from EIT.

I am fine with nextprogram and onCurrentProgramChanged

They should be exposed through a tuned channel

edit: e.g. Promise<sequence> TVChannel#getCurrentPrograms()

chrisn asked:

how should these relate to the EPG information available through TVChannel::getPrograms()?

In a DVB deployment this is EIT schedule, getCurrentPrograms EIT p/f In other deployments they may be identical.