dash-industry-forum/sand-test-vectors

Test vectors for ISO/IEC 23009-5 Server And Network assisted DASH

SAND Test Vectors

This repository collects test vectors for the ISO/IEC 23009-5 Server And Network assisted DASH standard.

It comprises:

• PED and status messages as plain text
• PER and metrics message as XML documents
• MPD example containing the sand:Channel element

sand-test-vectors's Issues

HTTPSReporting-Conf-OK-MultiRes.mpd has incorrect order of elements in <Metrics>

mpd/dash-if/HTTPSReporting-Conf-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>

Discrepancy DaneCapabilities documentation and XSD

Hi,
I've noticed some discrepancies between the documentation and the normative annex provided at the end of ISO/IEC 23009-5. The documentation suggests that the DaneCapabilities PER message contains either a list of supportedMessage elements with the attribute messageType which refers to the PER message type, or an messageSetUri attribute. Annex A, which provides the normative XML schema for SAND messages, says nothing about the messageType attribute and suggests that supportedMessage should contain an unsigned integer value and that the messageSetUri attribute should be an element instead.

This repository seems to follow the documentation instead of the normative XSD. Does this imply that the provided XSD contains a mistake? Or am I overlooking something?

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

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>