Order MPD and Period elements per spec #76
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This orders the sub-elements of MPD and Period according to the DASH spec. Generally for most DASH consumers, this doesn't matter because even moderately modern XML parsers don't care about the ordering of independent elements in an XML hierarchy. However, there are systems using less evolved means to parse these messages and do care about the ordering of, in particular, MPD and Period, it turns out. And these systems, even when not using them, result in particular stringency in manual validation of an MPD by the spec. Technically, we'd probably want to do a scrub at some point for all elements; in the interim, this updates the order of MPD and Period elements based on latest spec. Understand that the changing of the order might require waiting to cut a 0.7.x, perhaps (though since the lib is still in a pre-1.0 state, perhaps not?). Appreciate you considering this. Thanks again for the lib - it's wonderful!
Fixes #75