You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of the byte stream format specs (such as this one) have ReSpec warnings because they refer to informative definitions in the MSE spec, e.g., "media segment", "initialization segment".
Should we make these definitions normative - e.g., by moving the current section 1.1 Definitions to a new section 2, so it's outside the informative section 1 Introduction? Some of the definitions include normative requirements on implementations.
The text was updated successfully, but these errors were encountered:
+1 to make the definitions normative. On top to the byte stream format specs, the MSE spec itself references these informative definitions from within normative sections and algorithms, which isn't ideal either.
Introduction is non-normative, but the definitions
include normative requirements for implementations,
and are referenced normatively from the MSE Byte
Stream Format Registry entries, and so need to be
normative.
Resolves#347
All of the byte stream format specs (such as this one) have ReSpec warnings because they refer to informative definitions in the MSE spec, e.g., "media segment", "initialization segment".
Should we make these definitions normative - e.g., by moving the current section 1.1 Definitions to a new section 2, so it's outside the informative section 1 Introduction? Some of the definitions include normative requirements on implementations.
The text was updated successfully, but these errors were encountered: