rfc9559v3.txt   rfc9559.txt 
skipping to change at line 3155 skipping to change at line 3155
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterTimeStart path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterTimeStart
minOccurs / maxOccurs: 1 / 1 minOccurs / maxOccurs: 1 / 1
definition: Timestamp of the start of Chapter, expressed in Matroska definition: Timestamp of the start of Chapter, expressed in Matroska
Ticks -- i.e., in nanoseconds; see Section 11.1. Ticks -- i.e., in nanoseconds; see Section 11.1.
5.1.7.1.4.4. ChapterTimeEnd Element 5.1.7.1.4.4. ChapterTimeEnd Element
id / type: 0x92 / uinteger id / type: 0x92 / uinteger
path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterTimeEnd path: \Segment\Chapters\EditionEntry\+ChapterAtom\ChapterTimeEnd
minOccurs / maxOccurs: See Table 31 / 1 minOccurs / maxOccurs: See Table 31 / 1
definition: Timestamp of the end of Chapter timestamp excluded, definition: Timestamp of the end of Chapter (timestamp excluded),
expressed in Matroska Ticks -- i.e., in nanoseconds; see expressed in Matroska Ticks -- i.e., in nanoseconds; see
Section 11.1. The value MUST be greater than or equal to the Section 11.1. The value MUST be greater than or equal to the
ChapterTimeStart of the same ChapterAtom. ChapterTimeStart of the same ChapterAtom.
usage notes: With the ChapterTimeEnd timestamp value being excluded, usage notes: With the ChapterTimeEnd timestamp value being excluded,
it MUST take into account the duration of the last frame it it MUST take into account the duration of the last frame it
includes, especially for the ChapterAtom using the last frames of includes, especially for the ChapterAtom using the last frames of
the Segment. the Segment.
notes: See Table 31. notes: See Table 31.
+===========+====================================================+ +===========+====================================================+
skipping to change at line 3587 skipping to change at line 3587
file. To be playable, Matroska MUST also contain at least one Tracks file. To be playable, Matroska MUST also contain at least one Tracks
element and Cluster element. The first Info element and the first element and Cluster element. The first Info element and the first
Tracks element either MUST be stored before the first Cluster element Tracks element either MUST be stored before the first Cluster element
or SHALL both be referenced by a SeekHead element occurring before or SHALL both be referenced by a SeekHead element occurring before
the first Cluster element. the first Cluster element.
All Top-Level Elements MUST use a 4-octet EBML Element ID. All Top-Level Elements MUST use a 4-octet EBML Element ID.
When using Medium Linking, chapters are used to reference other When using Medium Linking, chapters are used to reference other
Segments to play in a given order (see Section 17.2). A Segment Segments to play in a given order (see Section 17.2). A Segment
containing these Linked Chapters does not require a Track element or containing these Linked Chapters does not require a Tracks element or
a Cluster element. a Cluster element.
It is possible to edit a Matroska file after it has been created. It is possible to edit a Matroska file after it has been created.
For example, chapters, tags, or attachments can be added. When new For example, chapters, tags, or attachments can be added. When new
Top-Level Elements are added to a Matroska file, the SeekHead Top-Level Elements are added to a Matroska file, the SeekHead
element(s) MUST be updated so that the SeekHead element(s) itemizes element(s) MUST be updated so that the SeekHead element(s) itemizes
the identity and position of all Top-Level Elements. the identity and position of all Top-Level Elements.
Editing, removing, or adding elements to a Matroska file often Editing, removing, or adding elements to a Matroska file often
requires that some existing elements be voided or extended. requires that some existing elements be voided or extended.
skipping to change at line 5229 skipping to change at line 5229
Chapters element. In that case, these elements are informational Chapters element. In that case, these elements are informational
only. only.
The following list shows the different Chapters elements only found The following list shows the different Chapters elements only found
in Ordered Chapters. in Ordered Chapters.
* ChapterAtom\ChapterSegmentUUID * ChapterAtom\ChapterSegmentUUID
* ChapterAtom\ChapterSegmentEditionUID * ChapterAtom\ChapterSegmentEditionUID
* ChapterAtom\ChapterTrack
* ChapterAtom\ChapProcess * ChapterAtom\ChapProcess
* Info\ChapterTranslate * Info\ChapterTranslate
* TrackEntry\TrackTranslate * TrackEntry\TrackTranslate
Furthermore, there are other EBML elements that could be used if the Furthermore, there are other EBML elements that could be used if the
EditionFlagOrdered evaluates to "1". EditionFlagOrdered evaluates to "1".
20.1.3.1. Ordered-Edition and Matroska Segment Linking 20.1.3.1. Ordered-Edition and Matroska Segment Linking
skipping to change at line 6043 skipping to change at line 6041
Element ID. Element ID.
Element IDs are encoded using the VINT mechanism described in Element IDs are encoded using the VINT mechanism described in
Section 4 of [RFC8794] and can be between one and five octets long. Section 4 of [RFC8794] and can be between one and five octets long.
Five-octet Element IDs are possible only if declared in the EBML Five-octet Element IDs are possible only if declared in the EBML
Header. Header.
Element IDs are described in Section 5 of [RFC8794], with the changes Element IDs are described in Section 5 of [RFC8794], with the changes
in [Err7189] and [Err7191]. in [Err7189] and [Err7191].
One-octet Matroska Element IDs (range 0x80-0xFF) are to be allocated One-octet Matroska Element IDs (range 0x80-0xFE) are to be allocated
according to the "RFC Required" policy [RFC8126]. according to the "RFC Required" policy [RFC8126].
Two-octet Matroska Element IDs (range 0x407F-0x7FFF) are to be Two-octet Matroska Element IDs (range 0x407F-0x7FFE) are to be
allocated according to the "Specification Required" policy [RFC8126]. allocated according to the "Specification Required" policy [RFC8126].
Three-octet (range 0x203FFF-0x3FFFFF) and four-octet Matroska Element Three-octet (range 0x203FFF-0x3FFFFE) and four-octet Matroska Element
IDs (range 0x101FFFFF-0x1FFFFFFE) are to be allocated according to IDs (range 0x101FFFFF-0x1FFFFFFE) are to be allocated according to
the "First Come First Served" policy [RFC8126]. the "First Come First Served" policy [RFC8126].
The allowed values in the "Matroska Element IDs" registry are similar The allowed values in the "Matroska Element IDs" registry are similar
to the ones found in the "EBML Element IDs" registry defined in to the ones found in the "EBML Element IDs" registry defined in
Section 17.1 of [RFC8794]. Section 17.1 of [RFC8794].
EBML Element IDs defined for the EBML Header -- as defined in EBML Element IDs defined for the EBML Header -- as defined in
Section 17.1 of [RFC8794] -- MUST NOT be used as Matroska Element Section 17.1 of [RFC8794] -- MUST NOT be used as Matroska Element
IDs. IDs.
 End of changes. 6 change blocks. 
7 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.48.