forked from w3c/encrypted-media
-
Notifications
You must be signed in to change notification settings - Fork 0
/
initdata-format-registry-respec.html
162 lines (139 loc) · 7.36 KB
/
initdata-format-registry-respec.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Encrypted Media Extensions Stream Format and Initialization Data Format Registry</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
<script src="encrypted-media.js" class="remove"></script>
<script class="remove">
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "encrypted-media", <!-- The registry does not have its own short name. -->
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "https://w3c.github.io/encrypted-media/initdata-format-registry.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
// editors, add as many as you like
// only "name" is required
editors: [
{ name: "David Dorwin", url: "",
company: "Google Inc.", companyURL: "https://www.google.com/" },
{ name: "Adrian Bateman", url: "",
company: "Microsoft Corporation", companyURL: "https://www.microsoft.com/" },
{ name: "Mark Watson", url: "",
company: "Netflix Inc.", companyURL: "https://www.netflix.com/" },
],
otherLinks: [
{ key: "Repository",
href: "https://github.com/w3c/encrypted-media/"}
],
emeDefGroupName: "format-registry",
emeUnusedGroupNameExcludeList: ["encrypted-media",
"eme-references-from-registry"
],
// name of the WG
wg: "HTML Working Group",
// URI of the public WG page
wgURI: "http://www.w3.org/html/wg/",
// name (without the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-html-media",
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: "https://www.w3.org/2004/01/pp-impl/40318/status",
noIDLIn: true,
scheme: "https",
// Empty definitions for objects declared in the document are here to
// prevent error messages from being displayed for references to these objects.
definitionMap: {},
preProcess: [ encryptedMediaPreProcessor ],
// Empty definitions for objects declared in the document are here to
// prevent error messages from being displayed for references to these objects.
definitionMap: {},
postProcess: [ encryptedMediaPostProcessor ],
};
</script>
<!-- script to register bugs -->
<script src="https://w3c.github.io/webcomponents/assets/scripts/bug-assist.js"></script>
<meta name="bug.product" content="HTML WG">
<meta name="bug.component" content="Encrypted Media Extensions">
<link rel="stylesheet" href="eme.css">
<style type="text/css">
#registry table { border-collapse: collapse; border-style: hidden hidden none hidden; }
#registry table thead, table tbody { border-bottom: solid; }
#registry table tbody th:first-child { border-left: solid; }
#registry table tbody th { text-align: left; }
#registry table td, table th { border-left: solid; border-right: solid; border-bottom: solid thin; vertical-align: top; padding: 0.2em; }
</style>
</head>
<body>
<section id="abstract">
<p>This specification defines the stream and initialization data formats for use with the <a def-id="eme-spec"></a>.</p>
</section>
<section id="sotd">
<p>The Working Group maintains <a href="https://www.w3.org/brief/MjY5"> a list of all bug reports that the editors have not yet tried to address</a>.</p>
<p>Implementors should be aware that this specification is not stable. <strong>Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways.</strong> Vendors interested in implementing this specification before it eventually reaches the Candidate Recommendation stage should join the mailing list mentioned below and take part in the discussions.</p>
</section>
<section id="purpose">
<h2>Purpose</h2>
<p>This registry is intended to enhance interoperability among implementations and users of encrypted media streams with the
<a def-id="eme-spec"></a> (EME) specification. In particular, this registry provides the means (1) to identify
and avoid collisions among initialization data type strings, and (2) to disclose information about encrypted data formats accepted by EME
implementations to promote interoperability.
</section>
<section id="organization">
<h2>Organization</h2>
<p>The registry maintains a mapping between <a def-id="initialization-data-type"></a> strings and encryption format specifications. The encryption format specifications describe the
structure and semantics of initialization data.</p>
<p>This registry is not intended to include any information on whether a byte stream format is encumbered by intellectual property claims. Implementors and users
are advised to seek appropriate legal counsel in this matter if they intend to implement or use a specific byte stream format.</p>
</section>
<section id="entry-requirements">
<h2>Registration Entry Requirements</h2>
<ol>
<li>Each entry must include a unique <a def-id="initialization-data-type"></a> string. If the byte stream format is derived-from an existing file format, then it should use the
MIME-type/subtype pairs typically used for the file format.</li>
<li>Each entry must include a link that references a publically available specification. It is recommended that such a specification be made available
without cost (other than reasonable shipping and handling if not available by online means).</li>
<li>Candidate entries must be announced on <a href="[email protected]">[email protected]</a>(<a href="[email protected]">subscribe</a>,
<a href="http://lists.w3.org/Archives/Public/public-html-media/">archives</a>) so they can be discussed and evaluated for compliance before being added to the
registry.</li>
</ol>
</section>
<section id="registry">
<h2>Registry</h2>
<table>
<thead>
<tr>
<th>Initialization Data Type</th>
<th>Public Specification(s)</th>
</tr>
</thead>
<tbody>
<tr>
<td>
cenc
</td>
<td><a href="cenc-format.html">ISO Common Encryption EME Stream Format and Initialization Data</a></td>
</tr>
<tr>
<td>
keyids
</td>
<td><a href="keyids-format.html">Key IDs Initialization Data Format</a></td>
</tr>
<tr>
<td>
webm
</td>
<td><a href="webm-format.html">WebM EME Stream Format and Initialization Data</a></td>
</tr>
</tbody>
</table>
</section>
</body>
</html>