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
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
|
<pre>Network Working Group M. Dolan
Request for Comments: 4246 TBT
Category: Informational February 2006
<span class="h1">International Standard Audiovisual Number (ISAN) URN Definition</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
The International Standard Audiovisual Number (ISAN) is a standard
numbering system for the unique and international identification of
audiovisual works. This document is the definition of the formal
Uniform Resource Name (URN) Namespace Identifier (NID) for ISAN.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. URN Namespace Definition Template ...............................<a href="#page-2">2</a>
<a href="#section-3">3</a>. Formal Syntax ...................................................<a href="#page-4">4</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-4">4</a>
<a href="#section-5">5</a>. Namespace Considerations ........................................<a href="#page-4">4</a>
<a href="#section-6">6</a>. Community Considerations ........................................<a href="#page-4">4</a>
<a href="#section-7">7</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-8">8</a>. References ......................................................<a href="#page-5">5</a>
<a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-5">5</a>
<a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-5">5</a>
<span class="grey">Dolan Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4246">RFC 4246</a> ISAN URN Definition February 2006</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document is the definition of the formal Uniform Resource Name
(URN) Namespace Identifier (NID) for ISAN.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URN Namespace Definition Template</span>
The following template is provided in accordance with [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>].
Namespace ID:
ISAN
Registration Information:
Version: 1
Date: 2004 11 22
Declared registrant of the namespace:
Name: ISAN International Agency
Address: 26 rue de St Jean, CH-1203 Geneva, Switzerland
Contact: Mr. Patrick Attallah, Managing Director
Declaration of structure:
The identifier structure is as follows:
URN:ISAN:<ISAN-NSS>
Where ISAN-NSS is conformant to URN syntax requirements defined in
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] and is further constrained by [<a href="#ref-ISO15706">ISO15706</a>] and in this
document. There are two forms, one with the version extension and
one without. The formal BNF is defined in <a href="#section-2">section 2</a> below.
Examples of the two forms are:
URN:ISAN:0123-1230-3210-2310-1
URN:ISAN:1881-66C7-3420-6541-9-9F3A-0245-U
Relevant ancillary documentation:
ISAN, its syntax, uses and its processes are defined in
[<a href="#ref-ISO15706">ISO15706</a>].
<span class="grey">Dolan Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4246">RFC 4246</a> ISAN URN Definition February 2006</span>
Identifier uniqueness considerations:
Uniqueness is guaranteed by the ISAN International Agency that
issues the numbers. Numbers are not re-assigned.
Identifier persistence considerations:
Persistence is guaranteed by ISO Registration Authority
processes and contracts with the ISAN International Agency.
Process of identifier assignment:
The details of the assignment process are defined from time to
time by the ISAN International Agency. However, in general, any
approved entity can request an ISAN number by providing the
required metadata information and paying the registration fee.
The ISAN International Agency may delegate to regional or market-
based Registration Agencies for portions of the registration
process.
Process for identifier resolution:
ISAN numbers are resolved by a direct or indirect lookup with the
ISAN International Agency. At this writing, a non-commercial,
manual system is available online at <a href="http://www.isan.org">http://www.isan.org</a>. The
resolution procedures may be modified from time to time by the
ISAN International Agency.
Rules for Lexical Equivalence:
The ISAN-NSS is unique by the nature of the ISAN International
Agency's number management. The ISAN-NSS is case-insensitive.
Upper and lower case characters are treated as identical.
Conformance with URN Syntax:
No special considerations. The syntax is fully conformant with
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
Validation mechanism:
The check digits provide syntax integrity. Lookup is via online
and offline services provided by the ISAN International Agency.
Scope: Global.
<span class="grey">Dolan Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4246">RFC 4246</a> ISAN URN Definition February 2006</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Formal Syntax</span>
The following syntax specification uses an augmented Backus-Naur Form
(BNF) and elements defined in the URN Syntax [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]. This syntax
here is derived from the syntax definition in [<a href="#ref-ISO15706">ISO15706</a>], constrained
to prohibit the space character as a separator.
<ISAN-NSS> ::= <root> <episode> [version]
<root> ::= 3*(<hexnum> "-")
<episode> ::= <hexnum> "-" <check>
<version> ::= 2*("-" <hexnum>) "-" <check>
<hexnum> ::= 4*(<hex>)
<check> ::= <upper> | <lower> | <number>
Note that <hex>, <upper>, <lower>, and <number> are defined in
[<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document only defines the syntax and resolution authority for
the ISAN numbers. Details of the resolution process and the security
of the assignment and resolution system processes are defined
external to this document by the ISAN International Agency and thus
outside the scope of this document.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Namespace Considerations</span>
ISAN is an external numbering system managed by an external agency
established by ISO. While URN namespaces may exist for which any
generic numbering system can be encoded, there is currently no direct
encoding for ISAN. An example of such a namespace is the MPEG-21
system.
ISAN numbers are reserved for use in identifying audiovisual works
for which there is a moving visual component, or components related
to such a work (e.g. subtitling track).
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Community Considerations</span>
The primary registrants for ISAN numbers are the producers and
studios of audiovisual works (movies and television shows). While
the system is not constrained to "major" works (any bona fide entity
can register any work), the primary benefits of its use come from
<span class="grey">Dolan Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4246">RFC 4246</a> ISAN URN Definition February 2006</span>
works that are widely distributed. The users of the ISAN system
range from the studios themselves to film and video archives and
libraries, rights administrators, program guide services, and
audience measurement services. Its potential for use in the Internet
community is as an identifier for streaming media.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
This document defines a URN NID registration that is to be entered
into the IANA registry of URN NIDs. It specifically requests the
NID, "ISAN".
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
[<a id="ref-ISO15706">ISO15706</a>] ISO 15706, Information and documentation - International
Standard Audiovisual Number (ISAN)
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P.
Faltstrom, "Uniform Resource Names (URN) Namespace
Definition Mechanisms", <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, October 2002.
Author's Address
Michael Dolan
TBT
PO Box 190
Del Mar, CA 92014 USA
EMail: md.1@newtbt.com
<span class="grey">Dolan Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4246">RFC 4246</a> ISAN URN Definition February 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Dolan Informational [Page 6]
</pre>
|
