I am trying to add a boilerplate, but I am really not able to so. This is all very cryptic for me.
<pre class="metadata">
Revision: 1.0
Title: DASH Player's Application Events and Timed Metadata Processing Models and APIs
Status: LD
Shortname: application events
URL: https://dashif.org/guidelines/name-of-doc
Issue Tracking: GitHub https://github.com/Dash-Industry-Forum/Events/issues
Repository: https://github.com/Dash-Industry-Forum/Event GitHub
Editor: DASH Industry Forum
Default Highlight: text
<!-- Enabling line numbers breaks code blocks in PDF! (2018-10-02) -->
Line Numbers: off
Markup Shorthands: markdown yes
Markup Shorthands: css yes
Boilerplate: copyright off, abstract off
Abstract: None
</pre>
The boilerplate for community review should contain all of the following:
DASH-IF IOP
CR
rev
-
Current version:
V4.3
Status: | | Draft | X | Internal Review | | Community Review | | Agreed
Title: | Low-latency Modes for DASH
|
Source: | Live TF
|
Supporting Companies: | Akamai, castLabs, Comcast, Elemental Technologies, Ericsson, Harmonics, Qualcomm Incorporated, Sony, TNO, Unified Streaming
|
Category: | A | | Date: | 2019-06-03
| Use one of the following categories: C (correction) A (addition of feature) B (editorial modification) |
|
Reason for change: | DASH‐IF collected information related to Low‐Latency Streaming in a Report, together with DVB. The report (available here: https://dash-industry-forum.github.io/docs/Report%20on%20Low%20Latency%20DASH.pdf) provides use cases, service scenarios, deployment experience and existing potential technologies. Also, DASH‐IF already generated the DASH profile for ATSC that includes a mode supporting low latency. Based on this information in the report, it is recommended to add low latency to DASH‐IF IOP Guidelines.
|
Summary of change: | This change provides a new clause for live services that addresses specification updates as well as implementation guidelines to support Low-Latency DASH services addressing the requirements above.
|
Consequences if not approved: | Low-Latency DASH not available
|
Sections affected: | References in clause 2 New section 4.X
|
Other comments: | This document contains several notes highlighted in yellow. Feedback during community review is welcome specifically on these topics.
| | | | | | | | | | | | | | | | | | | |
All,
I am trying to add a boilerplate, but I am really not able to so. This is all very cryptic for me.
The boilerplate for community review should contain all of the following:
Status: | | Draft | X | Internal Review | | Community Review | | Agreed Title: | Low-latency Modes for DASH | Source: | Live TF | Supporting Companies: | Akamai, castLabs, Comcast, Elemental Technologies, Ericsson, Harmonics, Qualcomm Incorporated, Sony, TNO, Unified Streaming | Category: | A | | Date: | 2019-06-03 | Use one of the following categories: C (correction) A (addition of feature) B (editorial modification) | | Reason for change: | DASH‐IF collected information related to Low‐Latency Streaming in a Report, together with DVB. The report (available here: https://dash-industry-forum.github.io/docs/Report%20on%20Low%20Latency%20DASH.pdf) provides use cases, service scenarios, deployment experience and existing potential technologies. Also, DASH‐IF already generated the DASH profile for ATSC that includes a mode supporting low latency. Based on this information in the report, it is recommended to add low latency to DASH‐IF IOP Guidelines. | Summary of change: | This change provides a new clause for live services that addresses specification updates as well as implementation guidelines to support Low-Latency DASH services addressing the requirements above. | Consequences if not approved: | Low-Latency DASH not available | Sections affected: | References in clause 2 New section 4.X | Other comments: | This document contains several notes highlighted in yellow. Feedback during community review is welcome specifically on these topics. | | | | | | | | | | | | | | | | | | | |