forked from jcgregorio/uri-templates
-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathdraft-gregorio-uritemplate-08.html
2119 lines (1923 loc) · 107 KB
/
draft-gregorio-uritemplate-08.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
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
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>URI Template</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="URI Template">
<meta name="generator" content="xml2rfc v1.36 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">Network Working Group</td><td class="header">J. Gregorio</td></tr>
<tr><td class="header">Internet-Draft</td><td class="header">Google</td></tr>
<tr><td class="header">Intended status: Standards Track</td><td class="header">R. Fielding</td></tr>
<tr><td class="header">Expires: July 29, 2012</td><td class="header">Adobe</td></tr>
<tr><td class="header"> </td><td class="header">M. Hadley</td></tr>
<tr><td class="header"> </td><td class="header">MITRE</td></tr>
<tr><td class="header"> </td><td class="header">M. Nottingham</td></tr>
<tr><td class="header"> </td><td class="header">Rackspace</td></tr>
<tr><td class="header"> </td><td class="header">D. Orchard</td></tr>
<tr><td class="header"> </td><td class="header">Salesforce.com</td></tr>
<tr><td class="header"> </td><td class="header">Jan 26, 2012</td></tr>
</table></td></tr></table>
<h1><br />URI Template<br />draft-gregorio-uritemplate-08</h1>
<h3>Abstract</h3>
<p>
A URI Template is a compact sequence of characters
for describing a range of Uniform Resource Identifiers
through variable expansion.
This specification defines the URI Template
syntax and the process for expanding a URI Template into a
URI reference, along with guidelines for the
use of URI Templates on the Internet.
</p>
<h3>Status of this Memo</h3>
<p>
This Internet-Draft is submitted in full
conformance with the provisions of BCP 78 and BCP 79.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current
Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any time.
It is inappropriate to use Internet-Drafts as reference material or to cite
them other than as “work in progress.”</p>
<p>
This Internet-Draft will expire on July 29, 2012.</p>
<h3>Copyright Notice</h3>
<p>
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.</p>
<p>
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) 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.</p>
<a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#intro">1.</a>
Introduction<br />
<a href="#overview">1.1.</a>
Overview<br />
<a href="#types">1.2.</a>
Levels and Expression Types<br />
<a href="#design">1.3.</a>
Design Considerations<br />
<a href="#limitations">1.4.</a>
Limitations<br />
<a href="#notation">1.5.</a>
Notational Conventions<br />
<a href="#character-encoding">1.6.</a>
Character Encoding and Unicode Normalization<br />
<a href="#syntax">2.</a>
Syntax<br />
<a href="#literals">2.1.</a>
Literals<br />
<a href="#expressions">2.2.</a>
Expressions<br />
<a href="#variables">2.3.</a>
Variables<br />
<a href="#modifiers">2.4.</a>
Value Modifiers<br />
<a href="#prefix-values">2.4.1.</a>
Prefix Values<br />
<a href="#composite-values">2.4.2.</a>
Composite Values<br />
<a href="#expansion">3.</a>
Expansion<br />
<a href="#literal-expansion">3.1.</a>
Literal Expansion<br />
<a href="#expression-expansion">3.2.</a>
Expression Expansion<br />
<a href="#variable-expansion">3.2.1.</a>
Variable Expansion<br />
<a href="#op-simple">3.2.2.</a>
Simple String Expansion: {var}<br />
<a href="#op-plus">3.2.3.</a>
Reserved expansion: {+var}<br />
<a href="#op-crosshatch">3.2.4.</a>
Fragment expansion: {#var}<br />
<a href="#op-dot">3.2.5.</a>
Label expansion with dot-prefix: {.var}<br />
<a href="#op-slash">3.2.6.</a>
Path segment expansion: {/var}<br />
<a href="#op-semicolon">3.2.7.</a>
Path-style parameter expansion: {;var}<br />
<a href="#op-question">3.2.8.</a>
Form-style query expansion: {?var}<br />
<a href="#op-ampersand">3.2.9.</a>
Form-style query continuation: {&var}<br />
<a href="#anchor1">4.</a>
Security Considerations<br />
<a href="#iana">5.</a>
IANA Considerations<br />
<a href="#ack">6.</a>
Acknowledgments<br />
<a href="#rfc.references1">7.</a>
References<br />
<a href="#rfc.references1">7.1.</a>
Normative References<br />
<a href="#rfc.references2">7.2.</a>
Informative References<br />
<a href="#implementation">Appendix A.</a>
Implementation Hints<br />
<a href="#rfc.authors">§</a>
Authors' Addresses<br />
</p>
<br clear="all" />
<a name="intro"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Introduction</h3>
<a name="overview"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.1"></a><h3>1.1.
Overview</h3>
<p>
A Uniform Resource Identifier (URI) <a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a> is often
used to identify a specific resource within a common space of similar
resources (informally, a "URI space"). For example, personal web spaces
are often delegated using a common pattern, such as
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://example.com/~fred/
http://example.com/~mark/
</pre></div>
<p>
or a set of dictionary entries might be grouped in a hierarchy
by the first letter of the term, as in
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://example.com/dictionary/c/cat
http://example.com/dictionary/d/dog
</pre></div>
<p>
or a service interface might be invoked with various user input
in a common pattern, as in
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://example.com/search?q=cat&lang=en
http://example.com/search?q=chien&lang=fr
</pre></div>
<p>
A URI Template is a compact sequence of characters for describing a
range of Uniform Resource Identifiers through variable expansion.
</p>
<p>
URI Templates provide a mechanism for abstracting a space of
resource identifiers such that the variable parts can be easily
identified and described. URI templates can have many uses,
including discovery of available services, configuring resource
mappings, defining computed links, specifying interfaces, and
other forms of programmatic interaction with resources.
For example, the above resources could be described by the
following URI templates:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://example.com/~{username}/
http://example.com/dictionary/{term:1}/{term}
http://example.com/search{?q,lang}
</pre></div>
<p>
We define the following terms:
</p>
<ul class="text">
<li>expression -
The text between '{' and '}', including the enclosing braces,
as defined in <a class='info' href='#syntax'>Section 2<span> (</span><span class='info'>Syntax</span><span>)</span></a>.
</li>
<li>expansion -
The string result obtained from a template expression after
processing it according to its expression type, list of variable
names, and value modifiers, as defined in <a class='info' href='#expansion'>Section 3<span> (</span><span class='info'>Expansion</span><span>)</span></a>.
</li>
<li>template processor -
A program or library that, given a URI Template and a set of
variables with values, transforms the template string into a
URI-reference by parsing the template for expressions and
substituting each one with its corresponding expansion.
</li>
</ul><p>
</p>
<p>
A URI Template provides both a structural description of a URI
space and, when variable values are provided, machine-readable
instructions on how to construct a URI corresponding to those values.
A URI Template is transformed into a URI-reference by replacing each
delimited expression with its value as defined by the
expression type and the values of variables named within the
expression. The expression types range from simple string
expansion to multiple name=value lists. The expansions
are based on the URI generic syntax, allowing an implementation
to process any URI Template without knowing the scheme-specific
requirements of every possible resulting URI.
</p>
<p>
For example, the following URI Template includes a
form-style parameter expression, as indicated by the "?" operator
appearing before the variable names.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://www.example.com/foo{?query,number}
</pre></div>
<p>
The expansion process for expressions beginning with the
question-mark ("?") operator follows the same pattern
as form-style interfaces on the World Wide Web:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://www.example.com/foo{?query,number}
\_____________/
|
|
For each defined variable in [ 'query', 'number' ],
substitute "?" if it is the first substitution or "&"
thereafter, followed by the variable name, '=', and the
variable's value.
</pre></div>
<p>
If the variables have the values
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
query := "mycelium"
number := 100
</pre></div>
<p>
then the expansion of the above URI Template is
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://www.example.com/foo?query=mycelium&number=100
</pre></div>
<p>
Alternatively, if 'query' is undefined, then the expansion
would be
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://www.example.com/foo?number=100
</pre></div>
<p>
or if both variables are undefined, then it would be
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://www.example.com/foo
</pre></div>
<p>
A URI Template may be provided in absolute form, as in the examples
above, or in relative form. A template is expanded before the
resulting reference is resolved from relative to absolute form.
</p>
<p>
Although the URI syntax is used for the result, the template
string is allowed to contain the broader set of characters
that can be found in IRI references <a class='info' href='#RFC3987'>[RFC3987]<span> (</span><span class='info'>Duerst, M. and M. Suignard, “Internationalized Resource Identifiers (IRIs),” January 2005.</span><span>)</span></a>.
A URI Template is therefore also an IRI template, and the result
of template processing can be transformed to an IRI by following
the process defined in Section 3.2 of <a class='info' href='#RFC3987'>[RFC3987]<span> (</span><span class='info'>Duerst, M. and M. Suignard, “Internationalized Resource Identifiers (IRIs),” January 2005.</span><span>)</span></a>.
</p>
<a name="types"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.2"></a><h3>1.2.
Levels and Expression Types</h3>
<p>
URI Templates are similar to a macro language with a fixed set of
macro definitions: the expression type determines the expansion
process. The default expression type is simple string expansion, wherein
a single named variable is replaced by its value as a string after
pct-encoding any characters
not in the set of unreserved URI characters (<a class='info' href='#notation'>Section 1.5<span> (</span><span class='info'>Notational Conventions</span><span>)</span></a>).
</p>
<p>
Since most template processors implemented prior to this specification
have only implemented the default expression type, we refer to these as
Level 1 templates.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
.-----------------------------------------------------------------.
| Level 1 examples, with variables having values of |
| |
| var := "value" |
| hello := "Hello World!" |
| |
|-----------------------------------------------------------------|
| Op Expression Expansion |
|-----------------------------------------------------------------|
| | Simple string expansion (Sec 3.2.2) |
| | |
| | {var} value |
| | {hello} Hello%20World%21 |
`-----------------------------------------------------------------'
</pre></div>
<p>
Level 2 templates add the plus ("+") operator, for expansion of
values that are allowed to include reserved URI characters
(<a class='info' href='#notation'>Section 1.5<span> (</span><span class='info'>Notational Conventions</span><span>)</span></a>), and the crosshatch ("#") operator
for expansion of fragment identifiers.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
.-----------------------------------------------------------------.
| Level 2 examples, with variables having values of |
| |
| var := "value" |
| hello := "Hello World!" |
| path := "/foo/bar" |
| |
|-----------------------------------------------------------------|
| Op Expression Expansion |
|-----------------------------------------------------------------|
| + | Reserved string expansion (Sec 3.2.3) |
| | |
| | {+var} value |
| | {+hello} Hello%20World! |
| | {+path}/here /foo/bar/here |
| | here?ref={+path} here?ref=/foo/bar |
|-----+-----------------------------------------------------------|
| # | Fragment expansion, crosshatch-prefixed (Sec 3.2.4) |
| | |
| | X{#var} X#value |
| | X{#hello} X#Hello%20World! |
`-----------------------------------------------------------------'
</pre></div>
<p>
Level 3 templates allow multiple variables per expression,
each separated by a comma, and add more complex operators for
dot-prefixed labels,
slash-prefixed path segments,
semicolon-prefixed path parameters, and
the forms-style construction of a query syntax consisting of
name=value pairs that are separated by an ampersand character.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
.-----------------------------------------------------------------.
| Level 3 examples, with variables having values of |
| |
| var := "value" |
| hello := "Hello World!" |
| empty := "" |
| path := "/foo/bar" |
| x := "1024" |
| y := "768" |
| |
|-----------------------------------------------------------------|
| Op Expression Expansion |
|-----------------------------------------------------------------|
| | String expansion with multiple variables (Sec 3.2.2) |
| | |
| | map?{x,y} map?1024,768 |
| | {x,hello,y} 1024,Hello%20World%21,768 |
| | |
|-----+-----------------------------------------------------------|
| + | Reserved expansion with multiple variables (Sec 3.2.3) |
| | |
| | {+x,hello,y} 1024,Hello%20World!,768 |
| | {+path,x}/here /foo/bar,1024/here |
| | |
|-----+-----------------------------------------------------------|
| # | Fragment expansion with multiple variables (Sec 3.2.4) |
| | |
| | {#x,hello,y} #1024,Hello%20World!,768 |
| | {#path,x}/here #/foo/bar,1024/here |
| | |
|-----+-----------------------------------------------------------|
| . | Label expansion, dot-prefixed (Sec 3.2.5) |
| | |
| | X{.var} X.value |
| | X{.x,y} X.1024.768 |
| | |
|-----+-----------------------------------------------------------|
| / | Path segments, slash-prefixed (Sec 3.2.6) |
| | |
| | {/var} /value |
| | {/var,x}/here /value/1024/here |
| | |
|-----+-----------------------------------------------------------|
| ; | Path-style parameters, semicolon-prefixed (Sec 3.2.7) |
| | |
| | {;x,y} ;x=1024;y=768 |
| | {;x,y,empty} ;x=1024;y=768;empty |
| | |
|-----+-----------------------------------------------------------|
| ? | Form-style query, ampersand-separated (Sec 3.2.8) |
| | |
| | {?x,y} ?x=1024&y=768 |
| | {?x,y,empty} ?x=1024&y=768&empty= |
| | |
|-----+-----------------------------------------------------------|
| & | Form-style query continuation (Sec 3.2.9) |
| | |
| | ?fixed=yes{&x} ?fixed=yes&x=1024 |
| | {&x,y,empty} &x=1024&y=768&empty= |
| | |
`-----------------------------------------------------------------'
</pre></div>
<p>
Finally, Level 4 templates add value modifiers as an optional suffix
to each variable name. A prefix modifier (":") indicates that
only a limited number of characters from the beginning of the value are
used by the expansion (<a class='info' href='#prefix-values'>Section 2.4.1<span> (</span><span class='info'>Prefix Values</span><span>)</span></a>).
An explode ("*") modifier indicates that the variable is to be treated
as a composite value, consisting of either a list of names or an
associative array of (name, value) pairs, that is expanded as if each
member were a separate variable (<a class='info' href='#composite-values'>Section 2.4.2<span> (</span><span class='info'>Composite Values</span><span>)</span></a>).
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
.-----------------------------------------------------------------.
| Level 4 examples, with variables having values of |
| |
| var := "value" |
| hello := "Hello World!" |
| path := "/foo/bar" |
| list := ("red", "green", "blue") |
| keys := [("semi",";"),("dot","."),("comma",",")] |
| |
| Op Expression Expansion |
|-----------------------------------------------------------------|
| | String expansion with value modifiers (Sec 3.2.2) |
| | |
| | {var:3} val |
| | {var:30} value |
| | {list} red,green,blue |
| | {list*} red,green,blue |
| | {keys} semi,%3B,dot,.,comma,%2C |
| | {keys*} semi=%3B,dot=.,comma=%2C |
| | |
|-----+-----------------------------------------------------------|
| + | Reserved expansion with value modifiers (Sec 3.2.3) |
| | |
| | {+path:6}/here /foo/b/here |
| | {+list} red,green,blue |
| | {+list*} red,green,blue |
| | {+keys} semi,;,dot,.,comma,, |
| | {+keys*} semi=;,dot=.,comma=, |
| | |
|-----+-----------------------------------------------------------|
| # | Fragment expansion with value modifiers (Sec 3.2.4) |
| | |
| | {#path:6}/here #/foo/b/here |
| | {#list} #red,green,blue |
| | {#list*} #red,green,blue |
| | {#keys} #semi,;,dot,.,comma,, |
| | {#keys*} #semi=;,dot=.,comma=, |
| | |
|-----+-----------------------------------------------------------|
| . | Label expansion, dot-prefixed (Sec 3.2.5) |
| | |
| | X{.var:3} X.val |
| | X{.list} X.red,green,blue |
| | X{.list*} X.red.green.blue |
| | X{.keys} X.semi,%3B,dot,.,comma,%2C |
| | X{.keys*} X.semi=%3B.dot=..comma=%2C |
| | |
|-----+-----------------------------------------------------------|
| / | Path segments, slash-prefixed (Sec 3.2.6) |
| | |
| | {/var:1,var} /v/value |
| | {/list} /red,green,blue |
| | {/list*} /red/green/blue |
| | {/list*,path:4} /red/green/blue/%2Ffoo |
| | {/keys} /semi,%3B,dot,.,comma,%2C |
| | {/keys*} /semi=%3B/dot=./comma=%2C |
| | |
|-----+-----------------------------------------------------------|
| ; | Path-style parameters, semicolon-prefixed (Sec 3.2.7) |
| | |
| | {;hello:5} ;hello=Hello |
| | {;list} ;list=red,green,blue |
| | {;list*} ;list=red;list=green;list=blue |
| | {;keys} ;keys=semi,%3B,dot,.,comma,%2C |
| | {;keys*} ;semi=%3B;dot=.;comma=%2C |
| | |
|-----+-----------------------------------------------------------|
| ? | Form-style query, ampersand-separated (Sec 3.2.8) |
| | |
| | {?var:3} ?var=val |
| | {?list} ?list=red,green,blue |
| | {?list*} ?list=red&list=green&list=blue |
| | {?keys} ?keys=semi,%3B,dot,.,comma,%2C |
| | {?keys*} ?semi=%3B&dot=.&comma=%2C |
| | |
|-----+-----------------------------------------------------------|
| & | Form-style query continuation (Sec 3.2.9) |
| | |
| | {&var:3} &var=val |
| | {&list} &list=red,green,blue |
| | {&list*} &list=red&list=green&list=blue |
| | {&keys} &keys=semi,%3B,dot,.,comma,%2C |
| | {&keys*} &semi=%3B&dot=.&comma=%2C |
| | |
`-----------------------------------------------------------------'
</pre></div>
<a name="design"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.3"></a><h3>1.3.
Design Considerations</h3>
<p>
Mechanisms similar to URI Templates have been defined within several
specifications, including WSDL <a class='info' href='#WSDL'>[WSDL]<span> (</span><span class='info'>Weerawarana, S., Moreau, J., Ryman, A., and R. Chinnici, “Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language,” June 2007.</span><span>)</span></a>,
WADL <a class='info' href='#WADL'>[WADL]<span> (</span><span class='info'>Hadley, M., “Web Application Description Language,” August 2009.</span><span>)</span></a> and OpenSearch <a class='info' href='#OpenSearch'>[OpenSearch]<span> (</span><span class='info'>Clinton, D., “OpenSearch 1.1,” December 2011.</span><span>)</span></a>.
This specification extends and formally defines the syntax so that URI
Templates can be used consistently across multiple Internet applications
and within Internet message fields, while at the same time retaining
compatibility with those earlier definitions.
</p>
<p>
The URI Template syntax has been designed to carefully balance
the need for a powerful expansion mechanism with the need for
ease of implementation. The syntax is designed to be trivial
to parse while at the same time providing enough flexibility to
express many common template scenarios. Implementations are able
to parse the template and perform the expansions in a single pass.
</p>
<p>
Templates are simple and readable when used with common
examples because the single-character operators match the URI
generic syntax delimiters. The operator's associated delimiter
(".", ";", "/", "?", "&", and "#") is omitted when none of the
listed variables are defined. Likewise, the expansion process for ";"
(path-style parameters) will omit the "=" when the variable value
is empty, whereas the process for "?" (form-style parameters)
will not omit the "=" when the value is empty. Multiple variables
and list values have their values joined with "," if there is no
predefined joining mechanism for the operator. The "+" and "#"
operators will substitute unencoded reserved characters found
inside the variable values; the other operators will pct-encode
reserved characters found in the variable values prior to expansion.
</p>
<p>
The most common cases for URI spaces can be described with
Level 1 template expressions. If we were only concerned with
URI generation, then the template syntax could be limited to
just simple variable expansion, since more complex forms could
be generated by changing the variable values. However, URI
Templates have the additional goal of describing the layout of
identifiers in terms of preexisting data values. The template
syntax therefore includes operators that reflect how
resource identifiers are commonly allocated. Likewise, since
prefix substrings are often used to partition large spaces of
resources, modifiers on variable values provide a way
to specify both the substring and the full value string
with a single variable name.
</p>
<a name="limitations"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.4"></a><h3>1.4.
Limitations</h3>
<p>
Since a URI Template describes a superset of the identifiers,
there is no implication that every possible expansion for
each delimited variable expression corresponds to a URI of an
existing resource. Our expectation is that an application
constructing URIs according to the template will be provided
with an appropriate set of values for the variables being
substituted, or at least a means of validating user data-entry
for those values.
</p>
<p>
URI Templates are not URIs: they do not identify
an abstract or physical resource, they are not parsed as URIs,
and should not be used in places where a URI would be expected
unless the template expressions will be expanded by a template
processor prior to use. Distinct field, element, or attribute
names should be used to differentiate protocol elements that
carry a URI Template from those that expect a URI reference.
</p>
<p>
Some URI Templates can be used in reverse for the purpose of
variable matching: comparing the template to a fully formed
URI in order to extract the variable parts from that URI and
assign them to the named variables. Variable matching only works
well if the template expressions are delimited by the beginning or
end of the URI or by characters that cannot be part of the
expansion, such as reserved characters surrounding a simple
string expression. In general, regular expression languages
are better suited for variable matching.
</p>
<a name="notation"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.5"></a><h3>1.5.
Notational Conventions</h3>
<p>
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 class='info' href='#RFC2119'>[RFC2119]<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a>.
</p>
<p>
This specification uses the Augmented Backus-Naur Form (ABNF)
notation of <a class='info' href='#RFC5234'>[RFC5234]<span> (</span><span class='info'>Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.</span><span>)</span></a>. The following ABNF rules
are imported from the normative references <a class='info' href='#RFC5234'>[RFC5234]<span> (</span><span class='info'>Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.</span><span>)</span></a>,
<a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a>, and <a class='info' href='#RFC3987'>[RFC3987]<span> (</span><span class='info'>Duerst, M. and M. Suignard, “Internationalized Resource Identifiers (IRIs),” January 2005.</span><span>)</span></a>.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<dfn>ALPHA</dfn> = <span class='val'>%x41-5A</span> / <span class='val'>%x61-7A</span> <em>; A-Z / a-z</em>
<dfn>DIGIT</dfn> = <span class='val'>%x30-39</span> <em>; 0-9</em>
<dfn>HEXDIG</dfn> = <cite class='key'>DIGIT</cite> / "<span class='str'>A</span>" / "<span class='str'>B</span>" / "<span class='str'>C</span>" / "<span class='str'>D</span>" / "<span class='str'>E</span>" / "<span class='str'>F</span>"
<em>; case-insensitive</em>
<dfn>pct-encoded</dfn> = "<span class='str'>%</span>" <cite class='key'>HEXDIG</cite> <cite class='key'>HEXDIG</cite>
<dfn>unreserved</dfn> = <cite class='key'>ALPHA</cite> / <cite class='key'>DIGIT</cite> / "<span class='str'>-</span>" / "<span class='str'>.</span>" / "<span class='str'>_</span>" / "<span class='str'>~</span>"
<dfn>reserved</dfn> = <cite class='id'>gen-delims</cite> / <cite class='id'>sub-delims</cite>
<dfn>gen-delims</dfn> = "<span class='str'>:</span>" / "<span class='str'>/</span>" / "<span class='str'>?</span>" / "<span class='str'>#</span>" / "<span class='str'>[</span>" / "<span class='str'>]</span>" / "<span class='str'>@</span>"
<dfn>sub-delims</dfn> = "<span class='str'>!</span>" / "<span class='str'>$</span>" / "<span class='str'>&</span>" / "<span class='str'>'</span>" / "<span class='str'>(</span>" / "<span class='str'>)</span>"
/ "<span class='str'>*</span>" / "<span class='str'>+</span>" / "<span class='str'>,</span>" / "<span class='str'>;</span>" / "<span class='str'>=</span>"
<dfn>ucschar</dfn> = <span class='val'>%xA0-D7FF</span> / <span class='val'>%xF900-FDCF</span> / <span class='val'>%xFDF0-FFEF</span>
/ <span class='val'>%x10000-1FFFD</span> / <span class='val'>%x20000-2FFFD</span> / <span class='val'>%x30000-3FFFD</span>
/ <span class='val'>%x40000-4FFFD</span> / <span class='val'>%x50000-5FFFD</span> / <span class='val'>%x60000-6FFFD</span>
/ <span class='val'>%x70000-7FFFD</span> / <span class='val'>%x80000-8FFFD</span> / <span class='val'>%x90000-9FFFD</span>
/ <span class='val'>%xA0000-AFFFD</span> / <span class='val'>%xB0000-BFFFD</span> / <span class='val'>%xC0000-CFFFD</span>
/ <span class='val'>%xD0000-DFFFD</span> / <span class='val'>%xE1000-EFFFD</span>
<dfn>iprivate</dfn> = <span class='val'>%xE000-F8FF</span> / <span class='val'>%xF0000-FFFFD</span> / <span class='val'>%x100000-10FFFD</span>
</pre></div>
<a name="character-encoding"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.6"></a><h3>1.6.
Character Encoding and Unicode Normalization</h3>
<p>
This specification uses the terms
"character",
"character encoding scheme",
"code point",
"coded character set",
"glyph",
"non-ASCII",
"normalization",
"protocol element", and
"regular expression"
as they are defined in <a class='info' href='#RFC6365'>[RFC6365]<span> (</span><span class='info'>Hoffman, P. and J. Klensin, “Terminology Used in Internationalization in the IETF,” September 2011.</span><span>)</span></a>.
</p>
<p>
The ABNF notation defines its terminal values to be
non-negative integers (code points) that are a superset of the
US-ASCII coded character set <a class='info' href='#ASCII'>[ASCII]<span> (</span><span class='info'>American National Standards Institute, “Coded Character Set - 7-bit American Standard Code for Information Interchange,” 1986.</span><span>)</span></a>. This
specification defines terminal values as code points within the
Unicode coded character set <a class='info' href='#UNIV6'>[UNIV6]<span> (</span><span class='info'>The Unicode Consortium, “The Unicode Standard, Version 6.0.0,” October 2011.</span><span>)</span></a>.
</p>
<p>
In spite of the syntax and template expansion process being defined
in terms of Unicode code points, it should be understood that
templates occur in practice as a sequence of characters in
whatever form or encoding is suitable for the context in which
they occur, whether that be octets embedded in a network protocol
element or glyphs painted on the side of a bus.
This specification does not mandate any particular character encoding
scheme for mapping between URI Template characters and the octets used to
store or transmit those characters.
When a URI Template appears in a protocol element, the character
encoding scheme is defined by that protocol; without such a definition,
a URI Template is assumed to be in the same character encoding scheme as
the surrounding text. It is only during the process of template
expansion that a string of characters in a URI Template is REQUIRED
to be processed as a sequence of Unicode code points.
</p>
<p>
The Unicode Standard <a class='info' href='#UNIV6'>[UNIV6]<span> (</span><span class='info'>The Unicode Consortium, “The Unicode Standard, Version 6.0.0,” October 2011.</span><span>)</span></a> defines various
equivalences between sequences of characters for various purposes.
Unicode Standard Annex #15 <a class='info' href='#UTR15'>[UTR15]<span> (</span><span class='info'>Davis, M. and M. Duerst, “Unicode Normalization Forms,” April 2003.</span><span>)</span></a> defines various
Normalization Forms for these equivalences. The normalization form
determines how to consistently encode equivalent strings.
In theory, all URI processing implementations, including template
processors, should use the same normalization form for generating
a URI reference. In practice, they do not. If a value has been
provided by the same server as the resource, then it can be assumed
that the string is already in the form expected by that server.
If a value is provided by a user, such as via a data-entry dialog,
then the string SHOULD be normalized as Normalization Form C
(NFC: Canonical Decomposition, followed by Canonical Composition)
prior to being used in expansions by a template processor.
</p>
<p>
Likewise, when non-ASCII data that represents readable strings is
pct-encoded for use in a URI reference, a template processor MUST
first encode the string as UTF-8 <a class='info' href='#RFC3629'>[RFC3629]<span> (</span><span class='info'>Yergeau, F., “UTF-8, a transformation format of ISO 10646,” November 2003.</span><span>)</span></a> and then
pct-encode any octets that are not allowed in a URI reference.
</p>
<a name="syntax"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Syntax</h3>
<p>
A URI Template is a string of printable Unicode characters
that contains zero or more embedded variable expressions, each
expression being delimited by a matching pair of braces ('{', '}').
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<dfn>URI-Template</dfn> = <span class='rep'>*</span>( <cite class='id'>literals</cite> / <cite class='id'>expression</cite> )
</pre></div>
<p>
Although templates (and template processor implementations) are
described above in terms of four gradual levels, we define the
URI-Template syntax in terms of the ABNF for Level 4. A template
processor limited to lower level templates MAY exclude the ABNF
rules applicable only to higher levels. However, it is RECOMMENDED
that all parsers implement the full syntax such that unsupported
levels can be properly identified as such to the end user.
</p>
<a name="literals"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.1"></a><h3>2.1.
Literals</h3>
<p>
The characters outside of expressions in a URI Template string
are intended to be copied literally to the URI-reference if the
character is allowed in a URI (reserved / unreserved / pct-encoded)
or, if not allowed, copied to the URI-reference as the sequence of
pct-encoded triplets corresponding to that character's encoding
in UTF-8 <a class='info' href='#RFC3629'>[RFC3629]<span> (</span><span class='info'>Yergeau, F., “UTF-8, a transformation format of ISO 10646,” November 2003.</span><span>)</span></a>.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<dfn>literals</dfn> = <span class='val'>%x21</span> / <span class='val'>%x23-24</span> / <span class='val'>%x26</span> / <span class='val'>%x28-3B</span> / <span class='val'>%x3D</span> / <span class='val'>%x3F-5B</span>
/ <span class='val'>%x5D</span> / <span class='val'>%x5F</span> / <span class='val'>%x61-7A</span> / <span class='val'>%x7E</span> / <cite class='id'>ucschar</cite> / <cite class='id'>iprivate</cite>
/ <cite class='id'>pct-encoded</cite>
<em>; any Unicode character except: CTL, SP,</em>
<em>; DQUOTE, "'", "%" (aside from pct-encoded),</em>
<em>; "<", ">", "\", "^", "`", "{", "|", "}"</em>
</pre></div>
<a name="expressions"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.2"></a><h3>2.2.
Expressions</h3>
<p>
Template expressions are the parameterized parts of a URI Template.
Each expression contains an optional operator, which defines the
expression type and its corresponding expansion process, followed by a
comma-separated list of variable specifiers (variable names and
optional value modifiers). If no operator is provided, the expression
defaults to simple variable expansion of unreserved values.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<dfn>expression</dfn> = "<span class='str'>{</span>" [ <cite class='id'>operator</cite> ] <cite class='id'>variable-list</cite> "<span class='str'>}</span>"
<dfn>operator</dfn> = <cite class='id'>op-level2</cite> / <cite class='id'>op-level3</cite> / <cite class='id'>op-reserve</cite>
<dfn>op-level2</dfn> = "<span class='str'>+</span>" / "<span class='str'>#</span>"
<dfn>op-level3</dfn> = "<span class='str'>.</span>" / "<span class='str'>/</span>" / "<span class='str'>;</span>" / "<span class='str'>?</span>" / "<span class='str'>&</span>"
<dfn>op-reserve</dfn> = "<span class='str'>=</span>" / "<span class='str'>,</span>" / "<span class='str'>!</span>" / "<span class='str'>@</span>" / "<span class='str'>|</span>"
</pre></div>
<p>
The operator characters have been chosen to reflect each of their roles
as reserved characters in the URI generic syntax. The operators defined
in <a class='info' href='#expansion'>Section 3<span> (</span><span class='info'>Expansion</span><span>)</span></a> of this specification include:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+ Reserved character strings;
# Fragment identifiers prefixed by "#";
. Name labels or extensions prefixed by ".";
/ Path segments prefixed by "/";
; Path parameter name or name=value pairs prefixed by ";";
? Query component beginning with "?" and consisting of
name=value pairs separated by "&"; and,
& Continuation of query-style &name=value pairs within
a literal query component.
</pre></div>
<p>
The operator characters equals ("="), comma (","), exclamation ("!"),
at-sign ("@"), and pipe ("|") are reserved for future extensions.
</p>
<p>
The expression syntax specifically excludes use of the dollar ("$")
and parentheses ["(" and ")"] characters so that they remain
available for use outside the scope of this specification.
For example, a macro language might use these characters to apply
macro substitution to a string prior to that string being processed
as a URI Template.
</p>
<a name="variables"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.3"></a><h3>2.3.
Variables</h3>
<p>
After the operator (if any), each expression contains a list of
one or more comma-separated variable specifiers (varspec).
The variable names serve multiple purposes: documentation for
what kinds of values are expected, identifiers for associating
values within a template processor, and the literal string to use
for the name in name=value expansions (aside from when exploding
an associative array). Variable names are case-sensitive because
the name might be expanded within a case-sensitive URI component.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<dfn>variable-list</dfn> = <cite class='id'>varspec</cite> <span class='rep'>*</span>( "<span class='str'>,</span>" <cite class='id'>varspec</cite> )
<dfn>varspec</dfn> = <cite class='id'>varname</cite> [ <cite class='id'>modifier-level4</cite> ]
<dfn>varname</dfn> = <cite class='id'>varchar</cite> <span class='rep'>*</span>( ["<span class='str'>.</span>"] <cite class='id'>varchar</cite> )
<dfn>varchar</dfn> = <cite class='key'>ALPHA</cite> / <cite class='key'>DIGIT</cite> / "<span class='str'>_</span>" / <cite class='id'>pct-encoded</cite>
</pre></div>
<p>
A varname MAY contain one or more pct-encoded triplets.
These triplets are considered an essential part of the variable name
and are not decoded during processing.
A varname containing pct-encoded characters is not the same variable
as a varname with those same characters decoded. Applications that
provide URI Templates are expected to be consistent in their use of
pct-encoding within variable names.
</p>
<p>
An expression MAY reference variables that are unknown to the template