We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mpd/dash-if/WSSReporting-OK-MultiRes.mpd contains the following
mpd/dash-if/WSSReporting-OK-MultiRes.mpd
<Metrics metrics="BufferLevel"> <Reporting schemeIdUri="urn:mpeg:dash:sand:channel:2016" value="channel-reporting"/> <Range duration="PT10S"/> </Metrics>
however the MPEG DASH schema says that the <Range> element is first...
<Range>
<xs:complexType name="MetricsType"> <xs:annotation> <xs:documentation xml:lang="en"> Metrics </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="Range" type="RangeType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Reporting" type="DescriptorType" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="metrics" type="xs:string" use="required"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType>
The text was updated successfully, but these errors were encountered:
Correct <Metrics> sub element order.
44df7c2
The [definition of `MetricsType`](https://github.com/MPEGGroup/DASHSchema/blob/993cb92435a68a2752ee036ae78d757633b271bf/DASH-MPD.xsd#L1082) used for the <Metrics> element can include 0 of more <Range> elements followed by <Reporting> elements. Proposal to fix issue Dash-Industry-Forum#2
No branches or pull requests
mpd/dash-if/WSSReporting-OK-MultiRes.mpd
contains the followinghowever the MPEG DASH schema says that the
<Range>
element is first...The text was updated successfully, but these errors were encountered: