Comments on 7.1 Periods

[haudiobe]

https://dashif-documents.azurewebsites.net/DASH-IF-IOP/master/DASH-IF-IOP.html#timing-period

An MPD SHALL define an ordered list of one or more consecutive periods. A period is both a time span on the MPD timeline and a definition of the data to be presented during this time span. period timing is relative to the zero point of the MPD timeline.

this is not a requirement, but a definition.

Periods are self-contained - a service SHALL NOT require a client to know the contents of another period in order to correctly present a period. Knowledge of the contents of different periods MAY be used by a client to achieve seamless period transitions, especially when working with [[#timing-connectivity|period-connected representations]].

Again this is not a requirement, but a statement of fact

In a static MPD, the first period SHALL start at the zero point of the MPD timeline. In a dynamic MPD, the first period SHALL start at or after the zero point of the MPD timeline.

unclear what this means. What is the "zero" point?

In a static MPD, the last period SHALL have a Period@duration.

this is not a requirement from MPEG-DASH. mediaPresentationDuration is also good enough

In a dynamic MPD, the last period MAY have a Period@duration, in which case it has a fixed duration. If without Period@duration, the last period in a dynamic MPD has an unlimited duration.

unlimited is not clear

[irajs]

Addressed all the comment along with Dash-Industry-Forum/Guidelines-TimingModel#10

[sandersaares]

As this has been addressed in August, I close the issue as it seems taken care of and was also discussed in some calls. If more comments arise, they can be processed separately.