Skip to content
New issue

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

WSSReporting-OK-MultiRes.mpd has incorrect order of elements in <Metrics> #2

Open
paulhiggs opened this issue May 2, 2021 · 0 comments

Comments

@paulhiggs
Copy link

mpd/dash-if/WSSReporting-OK-MultiRes.mpd contains the following

  <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...

	<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>
paulhiggs added a commit to paulhiggs/SAND-Test-Vectors that referenced this issue Jan 2, 2023
The  [definition of `MetricsType`](https://github.com/MPEGGroup/DASHSchema/blob/993cb92435a68a2752ee036ae78d757633b271bf/DASH-MPD.xsd#L1082) used for the &lt;Metrics&gt; element can include 0 of more &lt;Range&gt; elements followed by &lt;Reporting&gt; elements.

Proposal to fix issue Dash-Industry-Forum#2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant