jiebi/CodeConvo huggingface dataset:
Code change:
The current version of WARP only references CMAF packaging and does not make it clear that WARP is also intended to support LOC (Low Overhaded Container) packaging. LOC is defined by URL Currently the LOC spec defines both a streaming format and a packaging format. Reference for packaging will therefore need to be made to specific subsections of that draft. In the future if LOC packaging is separated from LOC streaming format, then the WARP references can be updated.

Related discussion:
text: catalog object SHOULD only be published only when the availability of tracks changes. <del> Each catalog update MUST be mapped to a discreet moq-transport object. </del> <ins> Each catalog update MUST be mapped to a discreet MOQT Object. </ins> 5. <del> The MOQT Groups and MOQT Objects need to be mapped to moq-transport Streams.  Irrespective of the packagingmode in place, each MOQT Object MUST be mapped to a new moq-transport Stream. </del> <ins> The MOQT Groups and MOQT Objects need to be mapped to MOQT Streams. Irrespective of the mediapackaging in place, each MOQT Object MUST be mapped to a new MOQT Stream. </ins> 6.
Code change:
Fixing table references and reformatting certain sections to 80 chars line width.
Table 2 is declared twice, as is Table 3.

Related discussion:
text: a separate MOQT Object.  Samples that belong to the same Group of Pictures (GOP) MUST be placed within the same MOQT Group. <del> Table 2 provides values for the catalog "packaging" field with LOC packaging. </del> <ins> When LOC packaging is used for a track, the catalog packaging attribute (packaging) MUST be present and it MUST be populated with a value of "loc". </ins> 3.2.
Code change:
Fixing table references and reformatting certain sections to 80 chars line width.
Table 2 is declared twice, as is Table 3.

Related discussion:
text: publishers for advertising their output and for subscribers in consuming that output.  The payload of the Catalog object is opaque to Relays and can be end-to-end encrypted.  The Catalog provides the <del> names and namespaces of the tracks being produced, along with the relationship between tracks, properties of the tracks that consumers may use for selection and any relevant initialization data. </del> <ins> names and namespaces of the tracks being produced, along with therelationship between tracks, properties of the tracks that consumers may use for selection and any relevant initialization data. </ins> The catalog track MUST have a case-sensitive Track Name of "catalog".
Code change:
Fixing table references and reformatting certain sections to 80 chars line width.
Table 2 is declared twice, as is Table 3.

Related discussion:
text: Location: R Required: Optional JSON Type: Boolean <del> A boolean that if true indicates that the publisher MAY issue </del> <ins> A Boolean that if true indicates that the publisher MAY issue </ins> incremental (delta) updates - see patch.  If false or absent, then <del> the publisher gaurantees that they will NOT issue any incremental </del> <ins> the publisher guarantees that they will NOT issue any incremental </ins> updates and that any future updates to the catalog will be independent.  The default value is false.  This field MUST be present if its value is true, but may be omitted if the value is false.
Code change:
Fixing table references and reformatting certain sections to 80 chars line width.
Table 2 is declared twice, as is Table 3.

Related discussion:
text: the catalog. Each timeline track begins with a header row of <del> MEDIA_PTS,GROUP_ID,OBJECT_ID,WALLCLOCK,METADATA.  This row defines </del> <ins> MEDIA_PTS,GROUP_ID,OBJECT_ID, WALLCLOCK,METADATA.  This row defines </ins> the 5 columns of data within each record. MEDIA_PTS: a media timestamp rounded to the nearest millisecond.