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
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
|
<pre>Internet Engineering Task Force (IETF) V. Giralt
Request for Comments: 6338 Univ. Malaga
Category: Informational R. McDuff
ISSN: 2070-1721 Univ. Queensland
August 2011
<span class="h1">Definition of a Uniform Resource Name (URN) Namespace</span>
<span class="h1">for the Schema for Academia (SCHAC)</span>
Abstract
This document describes a Uniform Resource Name (URN) namespace for
the Schema for Academia (SCHAC).
The namespace described in this document is for naming persistent
resources defined by the SCHAC participants internationally, their
working groups, and other designated subordinates. The main use of
this namespace will be for the creation of controlled vocabulary
values for attributes in the SCHAC schema. These values will be
associated with particular instances of persons or objects belonging
to any of the SCHAC object classes.
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/rfc6338">http://www.rfc-editor.org/info/rfc6338</a>.
<span class="grey">Giralt & McDuff Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
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="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Schema for Academia (SCHAC) international activity was born
inside the Task Force on European Middleware Coordination and
Collaboration (TF-EMC2) of the Trans-European Research and Education
Networking Association (TERENA) [<a href="#ref-6" title=""Trans-European Research and Education Networking Association"">6</a>]. The initial aim of SCHAC was to
harmonize the disjoint person schemas of the participating countries
in order to have a common way for expressing data about persons,
exchanged between educational organizations. SCHAC, as are other
person schemas, is designed to ease the sharing of information about
a given individual between parties, mostly, but not limited to,
educational and research institutions. The main aims of this sharing
are to provide resources to individuals and to allow said individuals
to move, virtually and physically, between such institutions. Thus,
the SCHAC schema was defined with input from all participants'
national person schemas [<a href="#ref-7" title=""SCHAC activity web site"">7</a>].
SCHAC does not supplant other person schemas such as
organizationalPerson [<a href="#ref-8" title=""Lightweight Directory Access Protocol (LDAP): Schema for User Applications"">8</a>], inetOrgPerson [<a href="#ref-9" title=""Definition of the inetOrgPerson LDAP Object Class"">9</a>], or eduPerson [<a href="#ref-10" title=""eduPerson Object Class Specification"">10</a>]; it
extends those where needed for the purposes of Higher Education
outside the United States. This characteristic has made SCHAC,
originally a European effort, useful for groups outside Europe.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</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">RFC 2119</a> [<a href="#ref-1" title=""Key words for use in RFCs to Indicate Requirement Levels"">1</a>].
<span class="grey">Giralt & McDuff Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Specification Template</span>
Namespace ID:
schac
Registration Information:
Registration Version Number 1
Registration Date: 2011-06-22
Registrant of the namespace:
European Committee for Academic Middleware (ECAM)
Trans-European Research and Education Networking Association
(TERENA)
Singel
Amsterdam
The Netherlands
Designated contacts:
Contact: Licia Florio
Affiliation: TERENA
Singel 468 D
Amsterdam, 1017 AW
The Netherlands
EMail: florio@terena.org
Phone: +31(0)20 5304488
Contact: Victoriano Giralt
Affiliation: University of Malaga
Central ICT Services
Blvd. Louis Pasteur, 33
Campus de Teatinos
29071 Malaga
Spain
EMail: victoriano@uma.es
Phone: +34 95 213 1415
<span class="grey">Giralt & McDuff Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
Syntactic structure:
The Namespace Specific Strings (NSSs) of all URNs assigned by
SCHAC will conform to the syntax defined in <a href="./rfc2141#section-2.2">Section 2.2 of
RFC 2141</a>, "URN Syntax" [<a href="#ref-11" title=""URN Syntax"">11</a>]. In addition, all SCHAC URN NSSs will
consist of a left-to-right series of tokens delimited by colons.
The left-to-right sequence of colon-delimited tokens corresponds
to descending nodes in a tree. To the right of the lowest naming
authority node, there may be zero, one, or more levels of
hierarchical naming nodes terminating in a rightmost leaf node.
See the "Identifier assignment" section below for more on the
semantics of NSSs. This syntax convention is captured in the
following normative ABNF rules for SCHAC NSSs (see <a href="./rfc5234">RFC 5234</a> [<a href="#ref-2" title=""Augmented BNF for Syntax Specifications: ABNF"">2</a>]):
SCHAC-NSS = 1*subStChar *( ":" 1*subStChar )
subStChar = trans / "%" HEXDIG HEXDIG
trans = ALPHA / DIGIT / other / reserved
other = "(" / ")" / "+" / "," / "-" / "." /
"=" / "@" / ";" / "$" /
"_" / "!" / "*" / "'"
reserved = "/" / "?" / "#"
The exclusion of the colon from the list of "other" characters
means that the colon can only occur as a delimiter between string
tokens. Note that this ABNF rule set guarantees that any valid
SCHAC NSS is also a valid <a href="./rfc2141">RFC 2141</a> NSS.
Relevant ancillary documentation:
None.
Identifier uniqueness:
It is the responsibility of TERENA to guarantee uniqueness of the
names of immediately subordinate naming authorities. Each lower-
level naming authority in turn inherits the responsibility of
guaranteeing uniqueness of names in its branch of the naming tree.
<span class="grey">Giralt & McDuff Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
Identifier persistence:
TERENA bears ultimate responsibility for maintaining the usability
of SCHAC URNs over time. This responsibility MAY be delegated to
subordinate naming authorities per the discussion in the section
below on identifier assignment. That section provides a mechanism
for the delegation to be revoked in the case where a subordinate
naming authority ceases to function.
Identifier assignment:
TERENA will create an initial series of immediately subordinate
naming authorities, and will define a process for adding to that
list of authorities. Such a list, and the policy for adding to
it, will be published at the root registry page. Each country
with a representative in SCHAC will be invited to designate a
naming authority. Country-specific namespaces based on the
country Internet Top-Level Domain (TLD) [<a href="#ref-12" title=""Country TLDs"">12</a>] will then be assigned
to the designated authority. The subordinated namespaces int and
eu will remain under TERENA authority, controlled by the SCHAC
activity members, for entities of global, international, or
European interest. There is also the possibility of granting
subordinate namespaces to multi-country organizations; in this
case, the organizational Internet Fully Qualified Domain Name
(FQDN) will be used as the prefix.
As an example, a European-level interest entity would be any value
related to information used in the Higher Education European
Space, or the so-called Bologna process. Such entities will
belong in the eu subordinate namespace.
Global international entities could encompass values related to
the Grid community or values useful both for some European and for
some Australian universities. Such entities would belong in the
int subordinate namespace.
Examples of multi-country organizations include TERENA itself or
an association like the Educational Policy Institute (EPI)
(educationalpolicy.org) that has members from Australia, Canada,
and the US.
URNs intended for values of SCHAC attributes will include the
attribute name immediately after the NSS prefix, before any
geographical namespace delegation, such that any string can convey
information about the attribute for which it is a value. For
example, values for schacUserStatus will be of the form:
<span class="grey">Giralt & McDuff Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
urn:schac:userStatus:int
urn:schac:userStatus:au or
urn:schac:userStatus:terena.org
If at all possible, automated registry publication mechanisms will
be provided, based on the work on distributed URN registries done
by the TF-EMC2 task force members.
Institutions and communities affiliated with SCHAC participants
may request that they be granted subordinate naming authority
status. Uniqueness of these namespaces under country authority
will be based on the requestor's Internet FQDN. This
subordination procedure SHOULD be carried along the delegation
chain; i.e., if at all possible, all entities that receive a
delegated namespace MUST have a valid FQDN and MUST publish an
Internet accessible URN value registry, based on the URN registry
mechanisms designed by the TF-EMC2 task force members.
On at least an annual basis, TERENA will contact the liaisons or
directors of each immediately subordinate naming authority. If
there is no response, or if the respondent indicates that they
wish to relinquish naming authority, the authority over that
branch of the tree reverts to TERENA. This process will be
enforced recursively by each naming authority on its subordinates.
This process guarantees that responsibility for each branch of the
tree will lapse for less than one year, at worst, before being
reclaimed by a superior authority.
Lexical equivalence of two SCHAC Namespace Specific Strings (NSSs)
is defined below as an exact, case-sensitive string match. TERENA
will assign names of immediately subordinate naming authorities in
lowercase only. This forestalls the registration of two SCHAC-
subordinate naming authorities whose names differ only in case.
Attribute names will use the same mixed-case format as in the
schema definition.
Identifier resolution:
The 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.
TERENA will maintain a registry of all SCHAC-assigned URN values,
both final and for delegation, on its web site:
<a href="https://urnreg.terena.org/">https://urnreg.terena.org/</a>
<span class="grey">Giralt & McDuff Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
Delegation entries will have a pointer to the registry of the
subordinate naming authority. This SHOULD recurse down the
delegation tree, but registries for several delegated namespaces
MAY be maintained by a single naming authority.
All registries MUST publish their URNs over https links [<a href="#ref-3" title=""HTTP Over TLS"">3</a>]. The
https links MUST be secured by sites offering credentials signed
by a SCHAC-community recognized Certification Authority (CA) using
the latest secure methods for accessing a web site (which at
present is the latest version of Transport Layer Security (TLS)
[<a href="#ref-4" title=""The Transport Layer Security (TLS) Protocol Version 1.2"">4</a>]). Registries SHOULD consider the user interface implications
of their choice of CA, taking into account issues like browser
alerts and blind trust.
Lexical equivalence:
Lexical equivalence of two SCHAC Namespace Specific Strings (NSSs)
is defined as an exact, case-sensitive string match.
Conformance with URN syntax:
All SCHAC NSSs fully conform to <a href="./rfc2141">RFC 2141</a> syntax rules for NSSs.
Validation mechanism:
As specified in the "Identifier resolution" section above, TERENA
will maintain an index of all SCHAC-assigned URNs on its web site:
<a href="https://urnreg.terena.org/">https://urnreg.terena.org/</a>. Presence in that registry or in any
subordinate registry implies that a given URN is valid. Delegated
naming authorities MUST guarantee that values are valid in their
assigned spaces.
Scope:
Global.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Examples</span>
The following examples are not guaranteed to be real. They are
listed for pedagogical reasons only.
urn:schac:personalUniqueID:es:DNI:9999999Z
urn:schac:personalUniqueCode:es:uma.es:codUni:061696758X
urn:schac:userStatus:au:uq.edu.au:service:mail:receive:disabled
urn:schac:personalPosition:pl:umk.pl:programmer
<span class="grey">Giralt & McDuff Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
There are no additional security considerations beyond those normally
associated with the use and resolution of URNs in general.
In order to guarantee the validity and origin of SCHAC-NSS URN
values, they MUST be published over https links [<a href="#ref-3" title=""HTTP Over TLS"">3</a>]. The https links
MUST be secured by sites offering credentials signed by a SCHAC-
community recognized Certification Authority (CA) using the latest
secure methods for accessing a web site (which at present is the
latest version of TLS [<a href="#ref-4" title=""The Transport Layer Security (TLS) Protocol Version 1.2"">4</a>]).
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Namespace Considerations</span>
Registration of a Namespace Identifier (NID) specific to SCHAC is
reasonable given the following considerations:
SCHAC would like to assign URNs to some very fine-grained objects.
This does not seem to be the primary intended use of the XML.org
namespace (<a href="./rfc3120">RFC 3120</a>) [<a href="#ref-13" title=""A URN Namespace for XML.org"">13</a>], or the more tightly controlled
Organization for the Advancement of Structured Information
Standards (OASIS) [<a href="#ref-14" title=""Organization for the Advancement of Structured Information Standards: OASIS"">14</a>] namespace (<a href="./rfc3121">RFC 3121</a>) [<a href="#ref-15" title=""A URN Namespace for OASIS"">15</a>].
SCHAC seeks naming autonomy. SCHAC is not a member of OASIS, so
becoming a subordinate naming authority under the OASIS URN space
is not an option. There is the MACE (Middleware Architecture
Committee for Education) (<a href="./rfc3613">RFC 3613</a>) [<a href="#ref-16" title=""Definition of a Uniform Resource Name (URN) Namespace for the Middleware Architecture Committee for Education (MACE)"">16</a>] namespace, but the SCHAC
development is done outside of the MACE activity scope; thus, the
attributes and values do not belong in the MACE namespace. Using
the MACE namespace requires that the SCHAC namespace be placed
under one of the SCHAC participants' namespaces, which hinders its
global scope.
SCHAC will want to assign URNs to non-XML objects as well. That
is another reason that XML.org may not be an appropriate higher-
level naming authority for SCHAC.
Some of the already defined SCHAC attribute values have been assigned
URNs under the urn:mace:terena.org namespace. These values will
enter a deprecation cycle, with a clear indication that they will be
replaced by values under the new namespace once it is assigned. In
any case, <a href="./rfc3406">RFC 3406</a> [<a href="#ref-5" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">5</a>] (which replaced <a href="./rfc2611">RFC 2611</a>) includes an explicit
statement that two or more URNs may point to the same resource.
<span class="grey">Giralt & McDuff Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Community Considerations</span>
The assignment and use of identifiers within the namespace are open,
and the related rule is established by the SCHAC activity members.
Registration agencies (the next-level naming authorities) will be the
National Research and Education Networks (NRENs) and established
organizational cross-border organizations that participate in SCHAC.
It is expected that the majority of the European NRENs, their
constituencies, participants in the Australian Access Federation, and
some other international activities will make use of the SCHAC
namespace.
After the establishment of the SCHAC namespace, TERENA will establish
a registry service (analogously to other distributed pan-European
services, such as eduroam, PerfSONAR, etc.) for the namespace
clients. This registry will be available via the root page of the
namespace: <a href="https://urnreg.terena.org/">https://urnreg.terena.org/</a>. The policy for registrations
will be defined in documents available at the root page of the
registry.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
In accordance with <a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a> [<a href="#ref-5" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">5</a>], IANA has registered the Formal URN
Namespace 'schac' in the Registry of URN Namespaces, using the
registration template presented in <a href="#section-2">Section 2</a> of this document.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span>
SCHAC is the result of the TERENA TF-EMC2 task force and many others
that have contributed ideas to the development of the schema.
This document was discussed on the URN-NID list, with the special
help of Alfred Hoenes, who thoroughly reviewed the document, helped
us correct errors, and suggested clarifications to the text.
Peter Saint-Andre has also provided comments that have improved the
overall document quality, for which we herein thank him. We'd also
like to thank Chris Lonvick for helping us express our security
concerns in a better way. Finally, we thank other reviewers that
have helped us to give the final touches to the text.
Special thanks should go to Dyonisius Visser from the TERENA
technical team for taking the time and effort required to set up the
root instance of the namespace registry.
<span class="grey">Giralt & McDuff Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-1">1</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-2">2</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.
[<a id="ref-3">3</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
[<a id="ref-4">4</a>] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS)
Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>, August 2008.
[<a id="ref-5">5</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.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-6">6</a>] TERENA, "Trans-European Research and Education Networking
Association", <<a href="http://www.terena.org/">http://www.terena.org/</a>>.
[<a id="ref-7">7</a>] TERENA TF-EMC2, "SCHAC activity web site",
<<a href="http://www.terena.org/activities/tf-emc2/schac.html">http://www.terena.org/activities/tf-emc2/schac.html</a>>.
[<a id="ref-8">8</a>] Sciberras, A., Ed., "Lightweight Directory Access Protocol
(LDAP): Schema for User Applications", <a href="./rfc4519">RFC 4519</a>, June 2006.
[<a id="ref-9">9</a>] Smith, M., "Definition of the inetOrgPerson LDAP Object Class",
<a href="./rfc2798">RFC 2798</a>, April 2000.
[<a id="ref-10">10</a>] MACE-Dir, "eduPerson Object Class Specification",
December 2007, <<a href="http://middleware.internet2.edu/eduperson/docs/internet2-mace-dir-eduperson-200712.html">http://middleware.internet2.edu/eduperson/docs/</a>
<a href="http://middleware.internet2.edu/eduperson/docs/internet2-mace-dir-eduperson-200712.html">internet2-mace-dir-eduperson-200712.html</a>>.
[<a id="ref-11">11</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
[<a id="ref-12">12</a>] IANA, "Country TLDs", <<a href="http://www.iana.org/domains/root/db/">http://www.iana.org/domains/root/db/</a>>.
[<a id="ref-13">13</a>] Best, K. and N. Walsh, "A URN Namespace for XML.org", <a href="./rfc3120">RFC 3120</a>,
June 2001.
[<a id="ref-14">14</a>] OASIS, "Organization for the Advancement of Structured
Information Standards: OASIS", <<a href="http://www.oasis-open.org/">http://www.oasis-open.org/</a>>.
<span class="grey">Giralt & McDuff Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6338">RFC 6338</a> SCHAC URN Namespace August 2011</span>
[<a id="ref-15">15</a>] Best, K. and N. Walsh, "A URN Namespace for OASIS", <a href="./rfc3121">RFC 3121</a>,
June 2001.
[<a id="ref-16">16</a>] Morgan, R. and K. Hazelton, "Definition of a Uniform Resource
Name (URN) Namespace for the Middleware Architecture Committee
for Education (MACE)", <a href="./rfc3613">RFC 3613</a>, October 2003.
Authors' Addresses
Victoriano Giralt, M.D.
University of Malaga
Avd. Cervantes, 2
Malaga, Malaga E-29071
Spain
Phone: +34-95-213-1415
EMail: victoriano@uma.es
URI: <a href="http://www.uma.es/">http://www.uma.es/</a>
Dr. Rodney McDuff
The University of Queensland
EMail: r.mcduff@uq.edu.au
URI: <a href="http://www.uq.edu.au/">http://www.uq.edu.au/</a>
Giralt & McDuff Informational [Page 11]
</pre>
|
