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
|
<pre>Internet Engineering Task Force (IETF) F. Dijkstra
Request for Comments: 6453 SARA
Category: Informational R. Hughes-Jones
ISSN: 2070-1721 DANTE
December 2011
<span class="h1">A URN Namespace for the Open Grid Forum (OGF)</span>
Abstract
This document describes a URN (Uniform Resource Name) namespace that
is engineered by the Open Grid Forum (OGF) for naming persistent
resources.
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="./rfc5741#section-2">Section 2 of RFC 5741</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/rfc6453">http://www.rfc-editor.org/info/rfc6453</a>.
Copyright Notice
Copyright (c) 2011 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">Dijkstra & Hughes-Jones Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Requirements Language ......................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. URN Specification for "ogf" Namespace ID (NID) ..................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Namespace ID ...............................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Registration Information ...................................<a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Declared Registrant of the Namespace .......................<a href="#page-3">3</a>
<a href="#section-2.4">2.4</a>. Declaration of Syntactic Structure .........................<a href="#page-3">3</a>
<a href="#section-2.5">2.5</a>. Relevant Ancillary Documentation ...........................<a href="#page-4">4</a>
<a href="#section-2.6">2.6</a>. Identifier Uniqueness Considerations .......................<a href="#page-4">4</a>
<a href="#section-2.7">2.7</a>. Identifier Persistence Considerations ......................<a href="#page-4">4</a>
<a href="#section-2.8">2.8</a>. Process of Identifier Assignment ...........................<a href="#page-5">5</a>
<a href="#section-2.9">2.9</a>. Process of Identifier Resolution ...........................<a href="#page-5">5</a>
<a href="#section-2.10">2.10</a>. Rules for Lexical Equivalence .............................<a href="#page-5">5</a>
<a href="#section-2.11">2.11</a>. Conformance with URN Syntax ...............................<a href="#page-5">5</a>
<a href="#section-2.12">2.12</a>. Validation Mechanism ......................................<a href="#page-6">6</a>
<a href="#section-2.13">2.13</a>. Scope .....................................................<a href="#page-6">6</a>
<a href="#section-3">3</a>. Examples (Informative) ..........................................<a href="#page-6">6</a>
<a href="#section-4">4</a>. Namespace Considerations ........................................<a href="#page-6">6</a>
<a href="#section-5">5</a>. Community 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>. IANA Considerations .............................................<a href="#page-7">7</a>
<a href="#section-8">8</a>. Acknowledgements ................................................<a href="#page-7">7</a>
<a href="#section-9">9</a>. References ......................................................<a href="#page-8">8</a>
<a href="#section-9.1">9.1</a>. Normative References .......................................<a href="#page-8">8</a>
<a href="#section-9.2">9.2</a>. Informative References .....................................<a href="#page-8">8</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Open Grid Forum (OGF) is a standardisation development
organisation in the field of distributed computing. The OGF produces
documents such as working drafts, specifications, and schemata. For
more information, see <<a href="http://www.ogf.org/">http://www.ogf.org/</a>>.
Working groups in the OGF community have expressed the need for
global, distributed, persistent identifiers in working drafts and
standards. Motivated by this need, the OGF would like to assign URNs
to some resources in order to retain unique, permanent, location-
independent names for them.
This namespace specification is for a formal namespace.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Dijkstra & Hughes-Jones Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URN Specification for "ogf" Namespace ID (NID)</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Namespace ID</span>
"ogf" (where "ogf" is an acronym for "Open Grid Forum").
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Registration Information</span>
Registration Version Number: 1
Registration Date: December 2011
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Declared Registrant of the Namespace</span>
Technical Director
Open Grid Forum
P.O. Box 1738
Muncie, Indiana 47308
USA
<a href="http://www.ogf.org/">http://www.ogf.org/</a>
EMail: urn@ogf.org
The position of Technical Director is currently fulfilled by Joel
Replogle.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Declaration of Syntactic Structure</span>
The formal syntax definitions below are given in ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>].
The namespace-specific string (NSS) in the urn:ogf names hierarchy
begins with a subnamespace identifier (SNID), followed by a delimiter
and a subnamespace-dependent string
OGF-URN = "urn:ogf:" SNID ":" SUBNAMESPACE-SPECIFIC-STRING
where <SNID> is a unique subnamespace identifier for the
specification, and <SUBNAMESPACE-SPECIFIC-STRING> is a unique
identifier within the subnamespace identifier scope.
<SNID> has the same syntax as a <NID> as defined in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]:
SNID = ( ALPHA / DIGIT ) *31( ALPHA / DIGIT / "-" )
ALPHA and DIGIT are defined in <a href="./rfc5234#appendix-B">Appendix B of [RFC5234]</a>.
The Technical Director at OGF (or their successors) assigns SNIDs.
<span class="grey">Dijkstra & Hughes-Jones Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
The syntax of <SUBNAMESPACE-SPECIFIC-STRING> is dependent on the
<SNID> and MUST be defined by a Grid Forum Document [<a href="#ref-GFD.1" title=""GGF Document Series"">GFD.1</a>]. This
document does not pose any additional restrictions to the
<SUBNAMESPACE-SPECIFIC-STRING> other than what is defined in the NSS
syntax as defined by [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] or its successor:
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
<URN chars> is defined in <a href="./rfc2141#section-2.2">Section 2.2 of [RFC2141]</a>.
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Relevant Ancillary Documentation</span>
The Technical Director at OGF (or their successors) will keep a list
of assigned subnamespace identifiers and associated documentation at
<<a href="http://www.ogf.org/urn/">http://www.ogf.org/urn/</a>> [<a href="#ref-URN-OGF" title=""URN:OGF Hierarchy Registry and Documentation"">URN-OGF</a>].
The procedures regarding how to register a subnamespace identifier
are described in [<a href="#ref-GFD.191" title=""Procedure for Registration of Subnamespace Identifiers in the URN:OGF Hierarchy"">GFD.191</a>] and can also be found at the above
Website.
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Identifier Uniqueness Considerations</span>
Identifier uniqueness will be enforced by the Technical Director of
the Open Grid Forum.
The OGF Technical Director may sub-delegate part of the namespace to
third parties. It will not be permissible, neither by the OGF nor
any third party, to re-assign previously assigned URNs. A practical
consequence is that a previously assigned subnamespace cannot be
re-assigned, unless additional arrangements are made to prevent
identifier re-assignments.
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Identifier Persistence Considerations</span>
The Technical Director will only assign subnamespace identifiers for
persistent resources.
In order to enforce identifier persistence for individual resources,
each document defining subnamespace identifiers MUST contain a
section on the type of resource that is specified (e.g., whether a
URN in the subnamespace identifies a specific version of a resource,
the latest version of a resource, a specific manifestation, or a more
general concept).
The namespace identifier "ogf" MUST NOT change, even if the Open Grid
Forum changes its name or is disbanded.
<span class="grey">Dijkstra & Hughes-Jones Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Process of Identifier Assignment</span>
Assignment of subnamespace identifiers is limited to the OGF and
those authorities that are specifically designated by the OGF
Technical Director of the OGF. The OGF may assign portions of its
namespace (specifically, those under designated subnamespace
identifiers) for assignment by third parties.
The details of this process are specified in [<a href="#ref-GFD.191" title=""Procedure for Registration of Subnamespace Identifiers in the URN:OGF Hierarchy"">GFD.191</a>].
The syntax and semantics of each subnamespace MUST be defined by a
Grid Forum Document [<a href="#ref-GFD.1" title=""GGF Document Series"">GFD.1</a>] before the corresponding SNID is
assigned.
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Process of Identifier Resolution</span>
The OGF namespace is not currently listed with a Resolution Discovery
System (RDS), but nothing about the namespace prohibits the future
definition of appropriate resolution methods or listing with an RDS.
The OGF will maintain an index of all subnamespace identifiers on its
Website <<a href="http://www.ogf.org/urn/">http://www.ogf.org/urn/</a>>. This list may refer to known
Resolution Discovery Systems.
<span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. Rules for Lexical Equivalence</span>
The <SNID> part of URNs in the OGF hierarchy is case insensitive.
Thus, the <SNID> MUST be case normalised before comparison.
The rules for lexical equivalence of the
<SUBNAMESPACE-SPECIFIC-STRING> part of URNs in the OGF hierarchy is
specific for each SNID and MUST be defined when a SNID is assigned by
the OGF Technical Director. These definitions MUST include
information about case sensitivity, and in the case of %-escaped
octets, MUST define the exact normalisation to be used (e.g.,
interpret as octet, interpret as UTF-8, specify type of Unicode
normalisation factor, etc.).
<span class="h3"><a class="selflink" id="section-2.11" href="#section-2.11">2.11</a>. Conformance with URN Syntax</span>
The intention of this document is to only restrict the syntax of the
<SNID>. The syntax of the <SUBNAMESPACE-SPECIFIC-STRING> follows the
general syntax of a URN:
SUBNAMESPACE-SPECIFIC-STRING = 1*<URN chars>
<span class="grey">Dijkstra & Hughes-Jones Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
Documents defining a subnamespace identifier SHOULD specify further
syntactic restrictions in <SUBNAMESPACE-SPECIFIC-STRING>. It is
RECOMMENDED that these documents forbid the assignment of URNs
containing characters in the <reserved> set ("%", "/", "?", and "#")
as defined in [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>]. This is in accordance with <a href="./rfc3986#section-2.2">Section 2.2 of
[RFC3986]</a>.
For forward compatibility, it is RECOMMENDED that software
implementations that don't validate subnamespace-specific strings
validate the syntax according to the generic rules for validating
URIs, as defined in [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. URIs may contain all characters
defined in <URN chars>, including the characters in <reserved>
(albeit they have a special meaning), as well as the characters "&"
and "~".
<span class="h3"><a class="selflink" id="section-2.12" href="#section-2.12">2.12</a>. Validation Mechanism</span>
The validation mechanism of URNs in the OGF hierarchy is specific for
each SNID and SHOULD be defined when a SNID is assigned by the OGF
Technical Director.
URNs in the OGF hierarchy without an assigned SNID are considered to
be invalid.
<span class="h3"><a class="selflink" id="section-2.13" href="#section-2.13">2.13</a>. Scope</span>
Global URNs are relevant for the distributed computing community in
general, and the Open Grid Forum in particular.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples (Informative)</span>
Since no subnamespace identifiers have been defined yet, no actual
examples can be given. Therefore, the following examples are not
guaranteed to be real or even syntactically correct.
Grid Forum Documents defining the "gfd" and "network" subnamespace
identifiers may give the following examples.
o urn:ogf:gfd:136
o urn:ogf:network:canarie.ca:kisti-uninett-glif-001
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Namespace Considerations</span>
The Open Grid Forum (OGF) is a standardisation development
organisation in the field of distributed computing.
<span class="grey">Dijkstra & Hughes-Jones Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
The use of the OGF hierarchy is expected to be broad, including but
not limited to usage for:
o Grid Forum Documents
o XML (Extensible Markup Language) Schemata
o RDF (Resource Description Framework) Schemata
The Open Grid Forum is dedicated to openly publishing all technical
documentation related to URNs in the OGF hierarchy and allowing
unlimited distribution of these documents.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Community Considerations</span>
Members of the distributed computing community will benefit from
persistent and globally unique identifiers for use in protocols
developed by the Open Grid Forum.
Practical use of the urn:ogf namespace has been detected, and a
formal registration will allow the Open Grid Forum to document this
usage and enforce technical review of current practices.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general,
which are described in [<a href="./rfc1737" title=""Functional Requirements for Uniform Resource Names"">RFC1737</a>], [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>], and [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>].
It is recommended that implementers check the OGF registry and
documentation [<a href="#ref-URN-OGF" title=""URN:OGF Hierarchy Registry and Documentation"">URN-OGF</a>] before assuming that a given identifier is
valid or has a certain meaning.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
IANA has registered the "ogf" namespace identifier (NID) with a
reference to this document in the "Formal URN Namespaces"
sub-registry [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>] of the "Uniform Resource Names (URN)
Namespaces" registry [<a href="#ref-URN-NAMESPACES">URN-NAMESPACES</a>].
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
The template and useful examples from [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>] formed the basis for
this document. The authors would like to thank Joel Replogle and
Andre Mersky for setting up the urn:ogf subnamespace registry.
Jeroen van der Ham, Peter Saint-Andre, and Mykyta Yevstifeyev
proofread this document and provided valuable feedback.
<span class="grey">Dijkstra & Hughes-Jones Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-GFD.191">GFD.191</a>] Dijkstra, F., Hughes-Jones, R., Newby, G., and J.
Replogle, "Procedure for Registration of Subnamespace
Identifiers in the URN:OGF Hierarchy", GFD 191,
December 2011, <<a href="http://www.ogf.org/documents/GFD.191.pdf">http://www.ogf.org/documents/GFD.191.pdf</a>>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, January 2005.
[<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>,
January 2008.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-GFD.1">GFD.1</a>] Catlett, C., "GGF Document Series", GFD 1, April 2002,
<<a href="http://www.ogf.org/documents/GFD.1.pdf">http://www.ogf.org/documents/GFD.1.pdf</a>>.
[<a id="ref-RFC1737">RFC1737</a>] Sollins, K. and L. Masinter, "Functional Requirements for
Uniform Resource Names", <a href="./rfc1737">RFC 1737</a>, December 1994.
[<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.
[<a id="ref-URN-NAMESPACES">URN-NAMESPACES</a>]
IANA, "Uniform Resource Names (URN) Namespaces",
<<a href="http://www.iana.org/">http://www.iana.org/</a>>.
[<a id="ref-URN-OGF">URN-OGF</a>] Open Grid Forum, "URN:OGF Hierarchy Registry and
Documentation", <<a href="http://www.ogf.org/urn/">http://www.ogf.org/urn/</a>>.
<span class="grey">Dijkstra & Hughes-Jones Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6453">RFC 6453</a> URN Namespace for the OGF December 2011</span>
Authors' Addresses
Freek Dijkstra
SARA
Science Park 121
Amsterdam 1098 XG
NL
EMail: Freek.Dijkstra@sara.nl
Richard Hughes-Jones
DANTE
City House
126-130 Hills Road
Cambridge CB2 1PQ
UK
EMail: Richard.Hughes-Jones@dante.net
Dijkstra & Hughes-Jones Informational [Page 9]
</pre>
|
