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
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
|
<pre>Internet Engineering Task Force (IETF) P. Lemieux
Request for Comments: 7972 Sandflow Consulting LLC
Obsoletes: <a href="./rfc7302">7302</a> September 2016
Category: Informational
ISSN: 2070-1721
<span class="h1">Entertainment Identifier Registry (EIDR) URN Namespace Definition</span>
Abstract
Entertainment Identifier Registry (EIDR) Identifiers are used for the
globally unique identification of motion picture and television
content. This document defines the formal Uniform Resource Name
(URN) Namespace Identifier (NID) for EIDR Identifiers.
This document obsoletes <a href="./rfc7302">RFC 7302</a>.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7972">http://www.rfc-editor.org/info/rfc7972</a>.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Lemieux Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Completed URN Namespace Definition Template . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Namespace Considerations . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4">4</a>. Community Considerations . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#appendix-A">Appendix A</a>. Summary of Changes (Informative) . . . . . . . . . . <a href="#page-10">10</a>
<a href="#appendix-A.1">A.1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#appendix-A.2">A.2</a>. Changes from <a href="./rfc7302">RFC 7302</a> . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document defines the formal Uniform Resource Name (URN)
Namespace Identifier (NID) for EIDR Identifiers.
EIDR Identifiers are centrally registered, globally unique
identifiers for audiovisual works and their variants, primarily film
and television. A unique set of metadata parameters describing the
associated work is bound to the EIDR Identifier at the time of
registration.
EIDR Identifiers are a special kind of DOI Name allocated by EIDR
Association specifically for audiovisual works. The Digital Object
Identifier (DOI) system provides an infrastructure for persistent
unique identification of objects of any type and is specified in
[<a href="#ref-ISO26234" title=""ISO 26324:2012 Information and documentation -- Digital object identifier system"">ISO26234</a>]. A DOI Name is the identifier that is permanently
assigned to an object. The use of DOI Names ensures persistence,
global uniqueness, and an open resolution infrastructure.
As a DOI Name, an EIDR Identifier has two components: a prefix
assigned exclusively to EIDR Association by the DOI Registration
Authority and a suffix defined by EIDR Association. Currently, EIDR
Identifiers use the prefix "10.5240", but additional prefixes might
be introduced in the future.
The following is an example of an EIDR Identifier in its canonical
representation:
10.5240/7791-8534-2C23-9030-8610-5
where "10.5240" is the prefix and "7791-8534-2C23-9030-8610-5" is the
suffix.
<span class="grey">Lemieux Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
The canonical URN representation of the same EIDR Identifier is:
urn:eidr:10.5240:7791-8534-2C23-9030-8610-5
Note that ":" is used as separator between the prefix and the suffix
since "/" is a URN reserved character.
[<a id="ref-EIDR-OVERVIEW">EIDR-OVERVIEW</a>] and [<a href="#ref-EIDR-INTRO">EIDR-INTRO</a>] provide additional background
information.
This document obsoletes <a href="./rfc7302">RFC 7302</a>. See <a href="#appendix-A">Appendix A</a> for a summary of
changes.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Completed URN Namespace Definition Template</span>
The namespace definition according to the template in [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>] is as
follows:
Namespace ID:
eidr
Registration Information:
Version 1
2014-03-03
Declared registrant of the namespace:
Name:
Entertainment Identifier Registry Association
Address:
c/o Alliances Management
544 Hillside Road
Redwood City, CA 94062
USA
Contact:
URL: <a href="http://eidr.org/contact/">http://eidr.org/contact/</a>
Email: info@eidr.org
<span class="grey">Lemieux Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
Declaration of syntactic structure:
An EIDR Identifier is a special kind of DOI Name (see [<a href="#ref-ISO26234" title=""ISO 26324:2012 Information and documentation -- Digital object identifier system"">ISO26234</a>])
and, as such, consists of two components: a prefix denoted EIDR-
PREFIX and a suffix denoted EIDR-SUFFIX. The URN representation
URN-EIDR of an EIDR Identifier conforms to the syntax (expressed
using [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>]):
URN-EIDR = "urn:eidr:" EIDR-NSS
EIDR-NSS = EIDR-PREFIX ":" EIDR-SUFFIX
EIDR-PREFIX = 1*EIDR-CHARS
EIDR-SUFFIX = 1*EIDR-CHARS
EIDR-CHARS = ALPHA / DIGIT / "-" / "." / "_"
The only value of EIDR-PREFIX currently in use is "10.5240".
Additional prefix values conforming to the EIDR-PREFIX syntax
might be introduced by EIDR Association in the future. In all
cases, each of these additional prefix values will be associated
with suffix values that conform to a subset of the EIDR-SUFFIX
syntax. These additional prefixes and their corresponding
suffixes will be documented in future revisions to this
registration.
An implementation can process an EIDR-NSS with an unknown prefix
as an opaque string per the "Rules of Lexical Equivalence" below,
and resolve it as a generic DOI Name per the "Process for
identifier resolution" below.
When EIDR-PREFIX is equal to "10.5240", the syntax of EIDR-SUFFIX
is further constrained according to the RP2079-SUFFIX syntax
specified in [<a href="#ref-SMPTERP2079">SMPTERP2079</a>]:
RP2079-SUFFIX = 5(4HEXDIG "-") CHECK
CHECK = DIGIT / ALPHA
where CHECK is the Mod 37,36 check character as specified in
[<a href="#ref-ISO7064" title=""Information technology -- Security techniques -- Check character systems"">ISO7064</a>], computed over the 20 hexadecimal digits HEXDIG of
RP2079-SUFFIX.
EXAMPLE: urn:eidr:10.5240:7791-8534-2C23-9030-8610-5
Relevant ancillary documentation:
[<a id="ref-ISO26234">ISO26234</a>] specifies DOI Name syntax and registration.
[<a id="ref-SMPTERP2079">SMPTERP2079</a>] specifies the syntax of the EIDR Identifier with the
prefix "10.5240".
<span class="grey">Lemieux Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
Identifier uniqueness considerations:
An EIDR Identifier is a DOI Name. The ISO 26324 Registration
Authority ensures DOI Name uniqueness; therefore, the URN-EIDR
derived from an EIDR Identifier is guaranteed to be unique and
never reassigned.
Furthermore, an EIDR Identifier is associated with a single URN-
EIDR.
Identifier persistence considerations:
An EIDR Identifier is a DOI Name. The ISO 26324 Registration
Authority ensures that a DOI Name remains valid indefinitely;
therefore, the URN-EIDR derived from an EIDR Identifier remains
valid indefinitely.
Process of identifier assignment:
EIDR Association registers each EIDR Identifier with the ISO 26324
Registration Authority.
Entities involved in the motion picture and television industry,
either directly in the production of content or in its
distribution and related services, are eligible to apply for
registrant status. Registrants pay an annual membership fee that
depends on the size of the company.
Process for identifier resolution:
As a DOI Name, the resolution of the EIDR Identifier associated
with an EIDR-NSS is handled by the ISO 26324 Registration
Authority.
The ISO 26324 Registration Authority operates a web service that
allows the EIDR Identifier associated with an EIDR-NSS to be
resolved by issuing an HTTP GET request to the following URI (see
[<a href="./rfc7231" title=""Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"">RFC7231</a>] and [<a href="./rfc2818" title=""HTTP Over TLS"">RFC2818</a>]):
"<a href="https://doi.org/">https://doi.org/</a>" URN-EIDR
If the EIDR Identifier exists, then an XML Schema instance
document (see [<a href="#ref-XMLSchema">XMLSchema</a>]) containing metadata associated with the
EIDR Identifier is returned; otherwise, the HTTP status code "404
Not Found" is returned.
<span class="grey">Lemieux Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
EXAMPLE: <a href="https://doi.org/urn:eidr:10.5240:7791-8534-2C23-9030-8610-5">https://doi.org/urn:eidr:10.5240:7791-8534-2C23-9030-8610-5</a>
NOTE: The web service uses the HTTP Accept header to determine the
format of the response. When using a web browser to access the
resource above, the query string "?locatt=type:Full" is appended
to the URI to explicitly request an XML response.
EIDR Association operates additional services specifically
tailored to EIDR users (see [<a href="#ref-EIDR-SERVICES">EIDR-SERVICES</a>] and [<a href="#ref-DOI-EIDR-PROXY">DOI-EIDR-PROXY</a>]).
These services include additional features, e.g., the ability to
register EIDR Identifiers and web-based GUI tools.
Rules for Lexical Equivalence:
Lexical equivalence of the URN-EIDR is defined by case-insensitive
string match.
NOTE: The URN-EIDR includes the "urn:eidr:" string, as specified
under "Declaration of syntactic structure".
Conformance with URN Syntax:
As specified above, the syntax of the URN-EIDR is a subset of the
URN syntax specified in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
Validation mechanism:
The validity of an EIDR-NSS can only be guaranteed by completing
the resolution process.
For EIDR-NSS with an EIDR-PREFIX equal to "10.5240", the CHECK
value can be used for integrity checking, as specified above.
Scope:
EIDR Identifiers are centrally registered, globally unique
identifiers for use with audiovisual works worldwide.
<span class="grey">Lemieux Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Namespace Considerations</span>
EIDR Identifiers are intended for use in Internet applications, where
URNs are routinely used to identify audiovisual resources. There is
no direct mapping from EIDR Identifiers to existing URN namespaces.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Community Considerations</span>
The primary registrants of EIDR Identifiers are producers and
distributors of audiovisual works, metadata aggregators, and
audiovisual archives. Any bona fide member of the ecosystem can
become an EIDR member and register any work. EIDR Identifiers can be
used by anyone to unambiguously identify an audiovisual asset and
retrieve underlying metadata. The primary benefits of their use are
associated with works in wide distribution, management of long or
complex distribution chains, and aggregation of information from
multiple sources.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has registered the Formal URN Namespace 'eidr' in the "Uniform
Resource Names (URN) Namespaces" registry, using the registration
template in <a href="#section-2">Section 2</a> of this document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
This document specifies the syntax of the URN-EIDR namespace and
makes no security representations. Furthermore, the details of
assignment and resolution processes are defined external to this
document by EIDR Association and the ISO 26324 Registration
Authority, and are thus outside the scope of this document. Note,
however, that failure to conform to the syntactic and lexical
equivalence rules in this specification when using an EIDR Identifier
as a criteria for accessing restricted resources can result in
granting unauthorized access to these resources.
<span class="grey">Lemieux Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-ISO26234">ISO26234</a>] International Organization for Standardization (ISO), "ISO
26324:2012 Information and documentation -- Digital object
identifier system", ISO Standard 26324, June 2012.
[<a id="ref-ISO7064">ISO7064</a>] International Organization for Standardization,
"Information technology -- Security techniques -- Check
character systems", ISO Standard 7064, February 2003.
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, DOI 10.17487/RFC2141,
May 1997, <<a href="http://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
DOI 10.17487/RFC5234, January 2008,
<<a href="http://www.rfc-editor.org/info/rfc5234">http://www.rfc-editor.org/info/rfc5234</a>>.
[<a id="ref-SMPTERP2079">SMPTERP2079</a>]
Society of Motion Picture and Television Engineers,
"Digital Object Identifier (DOI) Name and Entertainment ID
Registry (EIDR) Identifier Representations",
DOI 10.5594/SMPTE.RP2079.2013, SMPTE RP 2079, 2014.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-DOI-EIDR-PROXY">DOI-EIDR-PROXY</a>]
Entertainment Identifier Registry Association, "EIDR and
the DOI Proxy", May 2015,
<<a href="http://eidr.org/documents/EIDR_and_the_DOI_Proxy.pdf">http://eidr.org/documents/EIDR_and_the_DOI_Proxy.pdf</a>>.
[<a id="ref-EIDR-INTRO">EIDR-INTRO</a>]
Entertainment Identifier Registry Association, "EIDR: ID
Format Ver. 1.1", August 2013,
<<a href="http://eidr.org/documents/EIDR_ID_Format_v1.1.pdf">http://eidr.org/documents/EIDR_ID_Format_v1.1.pdf</a>>.
[<a id="ref-EIDR-OVERVIEW">EIDR-OVERVIEW</a>]
Entertainment Identifier Registry Association, "EIDR
Overview", November 2013, <<a href="http://eidr.org/documents/2013-11-01_EIDR_Overview_FINAL.pdf">http://eidr.org/</a>
<a href="http://eidr.org/documents/2013-11-01_EIDR_Overview_FINAL.pdf">documents/2013-11-01_EIDR_Overview_FINAL.pdf</a>>.
[<a id="ref-EIDR-SERVICES">EIDR-SERVICES</a>]
Entertainment Identifier Registry Association, "EIDR
System Version 2.0: Registry User's Guide", August 2013,
<<a href="http://eidr.org/documents/EIDR_2.0_Registry_User_Guide.pdf">http://eidr.org/documents/</a>
<a href="http://eidr.org/documents/EIDR_2.0_Registry_User_Guide.pdf">EIDR_2.0_Registry_User_Guide.pdf</a>>.
<span class="grey">Lemieux Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
[<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>,
DOI 10.17487/RFC2818, May 2000,
<<a href="http://www.rfc-editor.org/info/rfc2818">http://www.rfc-editor.org/info/rfc2818</a>>.
[<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>, DOI 10.17487/RFC3406,
October 2002, <<a href="http://www.rfc-editor.org/info/rfc3406">http://www.rfc-editor.org/info/rfc3406</a>>.
[<a id="ref-RFC7231">RFC7231</a>] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Semantics and Content", <a href="./rfc7231">RFC 7231</a>,
DOI 10.17487/RFC7231, June 2014,
<<a href="http://www.rfc-editor.org/info/rfc7231">http://www.rfc-editor.org/info/rfc7231</a>>.
[<a id="ref-rfcdiff">rfcdiff</a>] "Rfcdiff Tool", <<a href="https://tools.ietf.org/tools/rfcdiff/">https://tools.ietf.org/tools/rfcdiff/</a>>.
[<a id="ref-XMLSchema">XMLSchema</a>]
Holstege, M. and A. Vedamuthu, "W3C XML Schema Definition
Language (XSD): Component Designators", W3C Candidate
Recommendation CR-xmlschema-ref-20100119, January 2010,
<<a href="http://www.w3.org/TR/2010/CR-xmlschema-ref-20100119">http://www.w3.org/TR/2010/CR-xmlschema-ref-20100119</a>>.
<span class="grey">Lemieux Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7972">RFC 7972</a> EIDR URN Namespace Definition September 2016</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Summary of Changes (Informative)</span>
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. Introduction</span>
This Appendix summarizes changes across revisions of this
specification. This summary is informative and not intended to be
exhaustive. Readers seeking a definitive list of changes are instead
encouraged to use tools such as [<a href="#ref-rfcdiff" title=""Rfcdiff Tool"">rfcdiff</a>].
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Changes from <a href="./rfc7302">RFC 7302</a></span>
o "Process for identifier resolution" paragraph: The syntax for the
URI supplied to the web service is modified to use (a) the 'https'
scheme and (b) the URN-EIDR representation of the EIDR Identifier.
Author's Address
Pierre-Anthony Lemieux
Sandflow Consulting LLC
Email: pal@sandflow.com
Lemieux Informational [Page 10]
</pre>
|
