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
Test vectors for ISO/IEC 23009-5 Server And Network assisted DASH
License: BSD 3-Clause "New" or "Revised" License
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>
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>
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?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.