Dash-Industry-Forum / Guidelines-TimingModel

DASH-IF implementation guidelines: the DASH timing model
9 stars 1 forks source link

Periods (5.3.) #37

Closed RufaelDev closed 4 years ago

RufaelDev commented 4 years ago
sandersaares commented 4 years ago

please elaborate on the use of zero duration periods

Changed this to SHALL NOT have a duration of zero. This was some legacy leftover because old IOP versions allowed it but there were already comments questioning this and there's really no justification besides "for legacy reasons", so we might as well say don't do this.

timing examples may help and more exact definition of the timing behavior in differnt cases (unknown duration period, updated period, fixed duration period etc.)

Chapters "Presentation timing characteristics" and "First and last period timing in dynamic/static presentations" created to try better clarify this. I think it could be further improved but currently lack the inspiration as to how.

In some sense, perfect definitions are not practical as many of the components are defined in referenced specifications like DASH and there is also a stylistic choice to make the document as one intended to be consumed as a whole - there's a concept introduced in e.g. "Period timing" and then futher chapters explain how other elements relate to it. That is, it is explicitly not a goal that anyone can go to "Period" chapter and know all about period timing. That chapter just introduces the period timing aspect, further elaborated throughout the text.

consider merging with section 5.8

Structure adjusted somewhat, though not merged these. What do you think of the latest draft?

sandersaares commented 4 years ago

Proposed resolution: close issue; appropriate clarifications were made to text.

haudiobe commented 4 years ago

(IOPv5 20/02/05): No other comments. If no further comments are received, the issue will be closed during the next (IOPv5 20/02/12)

haudiobe commented 4 years ago

(IOPv5 20/02/12): No comments received. Issue is closed