search

MPEGGroup / DASHSchema

The XML schema and example XML files for DASH (ISO/IEC 23009-1)
Other
11 stars 16 forks source link

Update and rename example_patch_base.mpd to example_G21_patch_base.mpd #117

Closed haudiobe closed 3 years ago

haudiobe commented 3 years ago

This is renamed to refer to example G21 and also to address that patch docs have mpp suffix

mikedo commented 3 years ago

Where does .mpp come from? The only registration I can find for that is Microsoft Project. RFC 5261 registers .xer for patch-ops.

paulhiggs commented 3 years ago

According to clause 10.2 of RFC 5261 xer is used for an xml document that contains errors identified when performing a path.

The patch document is an XML document so using an interesting extension (where I presume MPP means MPD Patch) can be confusing. If needed, we can adjust our CI/CD procedures to look at the root element and validate against the relevant schema (at present the validation procedure just checks al XML documents again the DASH-MPD.xsd schema)

paulhiggs commented 3 years ago

5th edition FDIS has already been sent to ISO and stating "File extension(s): mpp" so we should do this anyway. I can look into updating the validation procedure to check *.mpp against DASH-MPD-PATCH.xsd

mikedo commented 3 years ago

I'll merge these PRs into dev and master, then move the "FDIS 5th Ed" release to match.

paulhiggs commented 3 years ago

I'll merge these PRs into dev and master, then move the "FDIS 5th Ed" release to match.

OK, Once issue #119 is closed, we can retire the 5th Ed branch

mikedo commented 3 years ago

I typically leave the branch active until publication as there can still be editorial changes up to when the files are posted at ISO.