Skip to content

Commit 4ea46c9

Browse files
committed
Add former content of 'extra' pages, and flag them as outdated
1 parent 67c0db7 commit 4ea46c9

File tree

8 files changed

+201
-16
lines changed

8 files changed

+201
-16
lines changed
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
<x-layout>
2+
<div class="alert alert-warning">
3+
<h4>Outdated</h4>
4+
<p>
5+
This content has not yet been updated to reflect the current version
6+
</p>
7+
</div>
8+
<div class="container">
9+
<h4>About</h4>
10+
11+
<p>
12+
DASH-IF Conformance Tool is used to validate DASH content according to DASH-related media specifications. It aims to give information about the validity of the content against one or more developed media standards. Consequently, it reports on (un)expected behavior that can be observed in provided media services that are aimed to be working in alignment to these standards.
13+
</p>
14+
15+
<p>
16+
The development of the tool started in 2012 funded by DASH-IF and has been continuously updated with newer versions of the already supported standards and/or new standards as required. Currently, the tool is aligned with a large set of specifications, namely MPEG-DASH,ISO BMFF, DASH-IF IOP, CMAF, DVB-DASH, HbbTV and CTA WAVE. It also integrates file format header level parsing of media codecs, including AVC, HEVC, AAC,HE-AAC, HE-AACv2, AC-3, AC-4, E-AC-3, WebVTT and TTML.
17+
</p>
18+
19+
20+
<p>
21+
For each corresponding specification, the scope of the validation covers:
22+
</p>
23+
24+
25+
<ul>
26+
<li>
27+
<em>Media PresentationDescription (MPD)</em> validation where the MPD is checked if it is a well-formed XML file, appropriate according to DASH schema and MPD-level signaling is done correctly
28+
</li>
29+
<li>
30+
<em>Segment validation</em> where the media content pointed to by the MPD is validated at container level,
31+
</li>
32+
<li>
33+
<em>Cross validation</em> of the MPD-level elements and attributes as well as of the mediacontent(s) signaled at the same hierarchy.
34+
</li>
35+
</ul>
36+
37+
<p>
38+
The DASH-IF Conformance Tool is an open source software available on <a href="https://github.com/Dash-Industry-Forum/DASH-IF-Conformance" target="_blank">Github</a>. A live demo of the tool is also provided <a href="https://conformance.dashif.org/" target="_blank">here</a>.
39+
</p>
40+
</div>
41+
</x-layout>

jccp/resources/views/components/layout.blade.php

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,12 @@
1919
</head>
2020
<body>
2121
<livewire:navigation />
22+
<div class="alert alert-info">
23+
<h4>This version is currently in <strong>alpha</strong> state.</h4>
24+
<p>
25+
Many checks and elements have not been ported yet, if you need them, please use the <a href="https://conformance.dashif.org/">Stable version</a> instead.
26+
</p>
27+
</div>
2228
<div>
2329
{{ $slot }}
2430
</div>

jccp/resources/views/faq.blade.php

Lines changed: 125 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,125 @@
1+
<x-layout>
2+
<div class="alert alert-warning">
3+
<h4>Outdated</h4>
4+
<p>
5+
This content has not yet been updated to reflect the current version
6+
</p>
7+
</div>
8+
<div class="container">
9+
<h3>FAQ</h3>
10+
11+
<h4>What is Conformance Software Tool?</h4>
12+
13+
<p>The Conformance Software Tool is an open source software tool that checks whether the following elements conform to DASH-related media specifications</p>
14+
15+
<ul>
16+
<li>the provided MPEG-DASH MPD manifest</li>
17+
<li>optionally, the media content pointed to within the MPD</li>
18+
</ul>
19+
20+
<h4>What does the tool check?</h4>
21+
<p>
22+
By default, conformance software tool validates the provided MPD against:
23+
</p>
24+
25+
<ul>
26+
<li> ISO/IEC 23009-1 DASH MPD and Segment Formats as well as
27+
<li> The profiles provided in the @profiles attribute in the given MPD that the tool supports
28+
</ul>
29+
30+
<p>only at the MPD level which includes</p>
31+
32+
<ul>
33+
<li> Xlink Resolving
34+
<li> DASH Schema Validation
35+
<li> MPD-Level Checks
36+
</ul>
37+
38+
<p>
39+
Optionally, you can include additional tests as below:
40+
</p>
41+
42+
<ul>
43+
<li>Segment Validation
44+
<li> DASH-IF
45+
<li>DVB
46+
<li>HbbTV
47+
<li>CMAF
48+
<li>CTA WAVE
49+
</ul>
50+
51+
<h4>How can I use the tool for testing?</h4>
52+
53+
<p>
54+
Testing can be done in maximum 3 easy steps:
55+
</p>
56+
57+
<ul>
58+
<li>Provide MPD in the input field
59+
<ul>
60+
<li>URL
61+
<li>Upload / Drag&Drop file
62+
</ul>
63+
</li>
64+
<li>Select additional tests (optional)
65+
<li>Click RUN button
66+
</ul>
67+
68+
<p>
69+
For a visual usage guideline, you can check the tour guide on the navigation menu.
70+
</p>
71+
72+
73+
<h4>What does the "Include additional tests" mean?</h4>
74+
75+
<p>
76+
77+
This part provides additional tests that can be included by the user if desired. The options are:
78+
</p>
79+
80+
<ul>
81+
<li><em>Segment Validation</em>: By default, only MPD validation (Xlink resolving, DASH schema validation, MPD-level checks) is performed against the existing profiles in @profiles attribute and the enforced profiles, if any. By checking this option, the media in each Representation pointed to by the MPD will also be validated according to provided profiles and ISO/IEC 14496-12 for base media file format.
82+
</li>
83+
<li>
84+
<em>DASH-IF</em>: Enables validation checks against https://dashif.org/guidelines/dash264 profile according to DASH-IF IOP guidelines v4.3.
85+
</li>
86+
<li>
87+
<em>LL DASH-IF</em>: Enables validation checks against http://www.dashif.org/guidelines/low-latency-live-v5 profile according to Low Latency DASH-IF IOP guidelines v4.3 CR.
88+
</li>
89+
<li>
90+
<em>DVB</em>: Enables validation checks against urn:dvb:dash:profile:dvb-dash:2014 profile according to ETSI TS 103 285 v1.1.1.
91+
</li>
92+
<li
93+
<em>HbbTV</em>: Enables validation checks against urn:hbbtv:dash:profile:isoff-live:2012 profile according to HbbTV 1.5 and ETSI TS 102 796 v1.4.1.
94+
</li>
95+
<li>
96+
<em>CMAF</em>: Enables validation checks against CMAF specification for segmented media according to ISO/IEC 23000-19.
97+
</li>
98+
<li>
99+
<em>CTA WAVE</em>: Enables validation checks against WAVE content specification according to CTA-5001.
100+
</li>
101+
</ul>
102+
103+
104+
<p><b>NOTE</b>: Please also check the answer under the question, <b>What does the tool check?</b> for understanding the default operation of the tool.</p>
105+
106+
<h4>5. Are there any example MPDs that I can use for testing?</h4>
107+
108+
<p>DASH-IF provides example MPDs also called as test vectors covering various test cases and features. They are hosted and accessible at <a href="https://testassets.dashif.org/" target="_blank">testasset.dashif.org</a></p>
109+
110+
<h4>How can I contribute?</h4>
111+
112+
<p>The source code is hosted at <a href="https://github.com/Dash-Industry-Forum/DASH-IF-Conformance" target="_blank">https://github.com/Dash-Industry-Forum/DASH-IF-Conformance</a>. To contribute to the software:</p>
113+
114+
<ul>
115+
<li> Fork the repository(-ies) that will be changed in the scope of the contribution
116+
<li> Make changes to files locally
117+
<li> Test the changes against various MPDs
118+
<li> Commit and push the changes to respective fork(s)
119+
<li> Create pull request
120+
<li> Wait for reviewer feedback
121+
</ul>
122+
123+
<p><b>NOTE</b>: Depending on the feedback on the pull request is reviewed by the maintainers of the software, the above steps might need to be repeated by the contributers.</p>
124+
</div>
125+
</x-layout>
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
<x-layout>
2+
<livewire:consent-manager />
3+
<livewire:select-mpd />
4+
5+
<livewire:manifest-details />
6+
7+
</x-layout>

jccp/resources/views/livewire/navigation.blade.php

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<nav class="navbar navbar-expand-lg bg-primary">
1+
<nav class="navbar navbar-expand-lg bg-primary" data-bs-theme="dark">
22
<div class="container">
33
<a class="navbar-brand" href="/"><img style="background-color: white; width: fit-content; height: 3em; border-radius: 0.3em;" src="/images/logo.png">Conformance Tool</a>
44
<button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
<x-layout>
2+
<div class="alert alert-warning">
3+
<h4>Outdated</h4>
4+
<p>
5+
This content has not yet been updated to reflect the current version
6+
</p>
7+
</div>
8+
</x-layout>

jccp/resources/views/welcome.blade.php

Lines changed: 0 additions & 14 deletions
This file was deleted.

jccp/routes/web.php

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,19 @@
55
use App\Http\Controllers\ManifestController;
66

77
Route::get('/', function () {
8-
return view('welcome');
8+
return view('home');
9+
});
10+
11+
Route::get('/about', function () {
12+
return view('about');
13+
});
14+
15+
Route::get('/statistics', function () {
16+
return view('statistics');
17+
});
18+
19+
Route::get('/faq', function () {
20+
return view('faq');
921
});
1022

1123
Route::get('/mpd', [ManifestController::class, 'retrieve']);

0 commit comments

Comments
 (0)