<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Guidelines on DASH Industry Forum</title>
    <link>https://dash-industry-forum.github.io/guidelines/</link>
    <description>Recent content in Guidelines on DASH Industry Forum</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <atom:link href="https://dash-industry-forum.github.io/guidelines/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IOP version 5</title>
      <link>https://dash-industry-forum.github.io/guidelines/iop-v5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dash-industry-forum.github.io/guidelines/iop-v5/</guid>
      <description>Introduction With version 5 of DASH-IF Interoperability Guidelines, DASH-IF decided to introduce different parts that each address specific aspects of DASH-based service delivery. Each part is developed and updated within its own timescale. The multipart set of documents is collectively called “DASH-IF Interoperability Points, V5.0” (IOP V5). Version 5 of the DASH-IF IOP is defined for usage with the MPEG DASH specification (ISO/IEC 23009-1) and further constrained to deliver media formatted according to the MPEG CMAF Specification (ISO/IEC 23000-19).</description>
    </item>
    <item>
      <title>Earlier Versions</title>
      <link>https://dash-industry-forum.github.io/guidelines/earlier-versions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dash-industry-forum.github.io/guidelines/earlier-versions/</guid>
      <description>Introduction DASH-IF publishes primarily three types of documents:&#xA;Completed Specifications and Guidelines: The documents below are stable and have undergone a community review. Documents for community review: These documents are technically solid, but public is asked for comments in order to improve details. Position and White Papers: These documents provide background and initial studies Completed DASH-IF Interoperability Documents Disclaimer The documents below are stable and have undergone a community review. However, the DASH-IF welcomes feedback on these published documents, e.</description>
    </item>
    <item>
      <title>Specifications</title>
      <link>https://dash-industry-forum.github.io/guidelines/specifications/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dash-industry-forum.github.io/guidelines/specifications/</guid>
      <description>Introduction DASH-IF has a Publicly Available Specifications (PAS) agreement with the European Telecommunications Standards Institute (ETSI) to publish DASH-IF documents as ETSI specifications. In the process of publishing through ETSI, DASH-IF still provides early drafts of the candidate specifications and runs community reviews and draft publications of candidate specifications. Also, DASH-IF collects errata or smaller updates to ETSI specifications that are then rolled into a new version of an ETSI specification at appropriate time.</description>
    </item>
    <item>
      <title>Other Publications and Position Papers</title>
      <link>https://dash-industry-forum.github.io/guidelines/others/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dash-industry-forum.github.io/guidelines/others/</guid>
      <description>Introduction On top of DASH-IF Interop Guidelines as well as ETSI specifications, DASH also has published a set of other publications guidelines.&#xA;Guidelines for Implementation: DASH-IF Interoperability Point for ATSC 3.0 Scope The scope of this document is to provide a DASH interoperability point that is based on DASH-IF-IOPs and provides extensions to address use cases and requirements of ATSC 3.0.&#xA;Comments and bugs may be submitted through the public github repository.</description>
    </item>
  </channel>
</rss>
