forked from jcgregorio/uri-templates
-
Notifications
You must be signed in to change notification settings - Fork 2
/
rfc2629.html
1825 lines (1561 loc) · 57.2 KB
/
rfc2629.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
<html><head><title>Writing I-Ds and RFCs using XML</title>
<STYLE type='text/css'>
.title { color: #990000; font-size: 22px; line-height: 22px; font-weight: bold; text-align: right;
font-family: helvetica, arial, sans-serif }
.filename { color: #666666; font-size: 18px; line-height: 28px; font-weight: bold; text-align: right;
font-family: helvetica, arial, sans-serif }
p.copyright { color: #000000; font-size: 10px;
font-family: verdana, charcoal, helvetica, arial, sans-serif }
p { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
ol { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
pre { margin-left: 3em; color: #333333 }
ul.toc { color: #000000; line-height: 16px;
font-family: verdana, charcoal, helvetica, arial, sans-serif }
H3 { color: #333333; font-size: 16px; line-height: 16px; font-family: helvetica, arial, sans-serif }
H4 { color: #000000; font-size: 14px; font-family: helvetica, arial, sans-serif }
TD.header { color: #ffffff; font-size: 10px; font-family: arial, helvetica, san-serif; valign: top }
TD.author-text { color: #000000; font-size: 10px;
font-family: verdana, charcoal, helvetica, arial, sans-serif }
TD.author { color: #000000; font-weight: bold; margin-left: 4em; font-size: 10px; font-family: verdana, charcoal, helvetica, arial, sans-serif }
A:link { color: #990000; font-size: 10px; font-weight: bold;
font-family: MS Sans Serif, verdana, charcoal, helvetica, arial, sans-serif }
A:visited { color: #333333; font-weight: bold; font-size: 10px;
font-family: MS Sans Serif, verdana, charcoal, helvetica, arial, sans-serif }
A:name { color: #333333; font-weight: bold; font-size: 10px;
font-family: MS Sans Serif, verdana, charcoal, helvetica, arial, sans-serif }
.link2 { color:#ffffff; font-weight: bold; text-decoration: none;
font-family: monaco, charcoal, geneva, MS Sans Serif, helvetica, monotype, verdana, sans-serif;
font-size: 9px }
.RFC { color:#666666; font-weight: bold; text-decoration: none;
font-family: monaco, charcoal, geneva, MS Sans Serif, helvetica, monotype, verdana, sans-serif;
font-size: 9px }
.hotText { color:#ffffff; font-weight: normal; text-decoration: none;
font-family: charcoal, monaco, geneva, MS Sans Serif, helvetica, monotype, verdana, sans-serif;
font-size: 9px }
</style>
</head>
<body bgcolor="#ffffff" text="#000000" alink="#000000" vlink="#666666" link="#990000">
<table border="0" cellpadding="0" cellspacing="2" width="30" height="30" align="right">
<tr>
<td bgcolor="#000000" align="center" valign="center" width="30" height="30">
<font face="monaco, MS Sans Serif" color="#666666" size="1">
<b><span class="RFC"> RFC </span></b>
</font>
<font face="charcoal, MS Sans Serif, helvetica, arial, sans-serif" size="1" color="#ffffff">
<span class="hotText">2629</span>
</font>
</td>
</tr>
<tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b> TOC </b></font></a><br></td></tr>
</table>
<table width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table width="100%" border="0" cellpadding="2" cellspacing="1">
<tr valign="top"><td width="33%" bgcolor="#666666" class="header">Network Working Group</td><td width="33%" bgcolor="#666666" class="header">M. Rose</td></tr>
<tr valign="top"><td width="33%" bgcolor="#666666" class="header">Request for Comments: 2629</td><td width="33%" bgcolor="#666666" class="header">Invisible Worlds, Inc.</td></tr>
<tr valign="top"><td width="33%" bgcolor="#666666" class="header">Category: Informational</td><td width="33%" bgcolor="#666666" class="header">June 1999</td></tr>
</table></td></tr></table>
<div align="right"><font face="monaco, MS Sans Serif" color="#990000" size="+3"><b><br><span class="title">Writing I-Ds and RFCs using XML</span></b></font></div>
<font face="verdana, helvetica, arial, sans-serif" size="2">
<h3>Status of this Memo</h3>
<p>
This memo provides information for the Internet community.
It does not specify an Internet standard of any kind.
Distribution of this memo is unlimited.</p>
<h3>Copyright Notice</h3>
<p>
Copyright (C) The Internet Society (1999). All Rights Reserved.</p>
<h3>Abstract</h3>
<p>
This memo presents a technique for using XML
(Extensible Markup Language)
as a source format for documents in the Internet-Drafts (I-Ds) and
Request for Comments (RFC) series.
</p>
<a name="toc"><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="30" align="right">
<tr>
<td bgcolor="#000000" align="center" valign="center" width="30" height="30">
<font face="monaco, MS Sans Serif" color="#666666" size="1">
<b><span class="RFC"> RFC </span></b>
</font>
<font face="charcoal, MS Sans Serif, helvetica, arial, sans-serif" size="1" color="#ffffff">
<span class="hotText">2629</span>
</font>
</td>
</tr>
<tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b> TOC </b></font></a><br></td></tr>
</table>
<h3>Table of Contents</h3>
<ul compact class="toc">
<b><a href="#anchor1">1.</a>
Introduction<br></b>
<b><a href="#anchor2">2.</a>
Using the DTD to Write I-Ds and RFCs<br></b>
<b><a href="#xml_basics">2.1</a>
XML basics<br></b>
<b><a href="#front_matter">2.2</a>
Front matter<br></b>
<b><a href="#anchor3">2.2.1</a>
The title Element<br></b>
<b><a href="#author">2.2.2</a>
The author Element<br></b>
<b><a href="#date">2.2.3</a>
The date Element<br></b>
<b><a href="#anchor4">2.2.4</a>
Meta Data Elements<br></b>
<b><a href="#anchor5">2.2.5</a>
The abstract Element<br></b>
<b><a href="#anchor6">2.2.6</a>
The note Element<br></b>
<b><a href="#anchor7">2.2.7</a>
Status, Copyright Notice, Table of Contents<br></b>
<b><a href="#ipr">2.2.7.1</a>
Conformance with RFC 2026<br></b>
<b><a href="#anchor8">2.2.8</a>
Everything in the Front<br></b>
<b><a href="#anchor9">2.3</a>
The Middle<br></b>
<b><a href="#section">2.3.1</a>
The section Element<br></b>
<b><a href="#t">2.3.1.1</a>
The t Element<br></b>
<b><a href="#anchor10">2.3.1.2</a>
The list Element<br></b>
<b><a href="#figure">2.3.1.3</a>
The figure Element<br></b>
<b><a href="#xref">2.3.1.4</a>
The xref Element<br></b>
<b><a href="#eref">2.3.1.5</a>
The eref Element<br></b>
<b><a href="#iref">2.3.1.6</a>
The iref Element<br></b>
<b><a href="#anchor11">2.3.1.7</a>
The vspace Element<br></b>
<b><a href="#back_matter">2.4</a>
Back matter<br></b>
<b><a href="#references">2.4.1</a>
The references Element<br></b>
<b><a href="#anchor12">2.4.2</a>
Appendices<br></b>
<b><a href="#anchor13">2.4.3</a>
Copyright Status<br></b>
<b><a href="#anchor14">3.</a>
Processing the XML Source File<br></b>
<b><a href="#anchor15">3.1</a>
Editing<br></b>
<b><a href="#anchor16">3.1.1</a>
Checking<br></b>
<b><a href="#xml2rfc">3.2</a>
Converting to Text Format<br></b>
<b><a href="#anchor17">3.3</a>
Converting to HTML Format<br></b>
<b><a href="#anchor18">3.4</a>
Viewing<br></b>
<b><a href="#anchor19">3.5</a>
Searching<br></b>
<b><a href="#anchor20">4.</a>
Security Considerations<br></b>
<b><a href="#rfc.references1">§</a>
References<br></b>
<b><a href="#rfc.authors">§</a>
Author's Address<br></b>
<b><a href="#rfc">A.</a>
The rfc Element<br></b>
<b><a href="#rfc.dtd">B.</a>
The RFC DTD<br></b>
<b><a href="#anchor21">C.</a>
Acknowledgements<br></b>
<b><a href="#rfc.index">§</a>
Index<br></b>
<b><a href="#rfc.copyright">§</a>
Full Copyright Statement<br></b>
</ul>
<br clear="all">
<a name="anchor1"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b> TOC </b></font></a><br></td></tr></table>
<h3>1. Introduction</h3>
<p>
This memo describes how to write a document for the I-D and RFC series
using <a href="#XML">the Extensible Markup Language</a>[1] (XML).
This memo has three goals:
<ol class="text">
<li>
To describe a simple XML Document Type Definition (DTD) that is
powerful enough to handle the simple formatting requirements of RFC-like
documents whilst allowing for meaningful markup of descriptive
qualities.
</li>
<li>
To describe software that processes XML source files,
including a tool that produces documents
conforming to <a href="#refs.RFC2223">RFC 2223</a>[2],
HTML format, and so on.
</li>
<li>
To provide the proof-of-concept for the first two goals
(this memo was written using this DTD and produced using that
software).
</li>
</ol>
<p>
</p>
<p>
It is beyond the scope of this memo to discuss the political
ramifications of using XML as a source format for RFC-like documents.
Rather,
it is simply noted that adding minimal markup to plain text:
<ul class="text">
<li>
allows the traditional production of textual RFC-like documents using
familiar editors;
</li>
<li>
requires some, albeit minimal, additions to existing software
environments; and,
</li>
<li>
permits information to be organized, searched, and retrieved
using both unstructured and structured mechanisms.
</li>
</ul>
<p>
</p>
<a name="anchor2"><br><hr size="1" shade="0"></a>
<table border="0" cellpadding="0" cellspacing="2" width="30" height="15" align="right"><tr><td bgcolor="#990000" align="center" width="30" height="15"><a href="#toc" CLASS="link2"><font face="monaco, MS Sans Serif" color="#ffffff" size="1"><b> TOC </b></font></a><br></td></tr></table>
<h3>2. Using the DTD to Write I-Ds and RFCs</h3>
<p>
We do not provide a formal or comprehensive description of XML.
Rather,
this section discusses just enough XML to use a Document Type
Declaration (DTD) to write RFC-like documents.
</p>
<p>
If you're already familiar with XML,
skip to <a href="#rfc.dtd">The RFC DTD</a> to look at the DTD.
</p>
<h4><a name="xml_basics">2.1</a> XML basics</h4>
<p>
There are very few rules when writing in XML,
as the syntax is simple.
There are five terms you'll need to know:
<ol class="text">
<li>
An "element" usually refers to a start tag, an end tag, and all the
characters in between,
e.g.,
"<example>text and/or nested elements</example>"
</li>
<li>
An "empty element" combines the start tag and the end tag,
e.g.,
"<empty/>".
You don't find these in HTML.
</li>
<li>
An "attribute" is part of an element.
If present, they occur in the start tag, e.g.,
"<example name='value'>".
Of course,
they can also appear in empty elements, e.g.,
"<empty name='value'/>".
</li>
<li>
An "entity" is a textual macro that starts with "&".
Don't worry about these,
you'll only use them whenever you want to put a "&" or a "<" in
your text.
</li>
<li>
A "token" is a string of characters.
The first character is either a letter or an underscore ("_").
Any characters that follow are either letters, numbers, an
underscore, or a period (".").
</li>
</ol>
<p>
</p>
<p>
First,
start your source file with an XML declaration,
a reference to the DTD,
and the "rfc" element:
</p>
</font><pre>
<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<rfc>
...
</rfc>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
Ignore the first two lines
-- the declaration and the reference --
and simply treat them as opaque strings.
Nothing else should be present after the "</rfc>" tag.
</p>
<p>
Second,
make sure that all elements are properly matched and nested.
A properly matched element that starts with
"<example>" is eventually followed with "</example>".
(Empty elements are always matched.)
Elements are properly nested when they don't overlap.
</p>
<p>
For example,
</p>
</font><pre>
<outer>
...
<inner>
...
</inner>
...
</outer>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
is properly nested.
</p>
<p>
However,
</p>
</font><pre>
<outer>
...
<inner>
...
</outer>
...
</inner>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
overlaps, so the elements aren't properly nested.
</p>
<p>
Third,
never use "<" or "&" in your text.
Instead, use either "&lt;" or "&amp;", respectively.
</p>
<p>
Fourth,
there are two quoting characters in XML, 'apostrophe' and "quotation".
Make sure that all attributes values are quoted,
e.g., "<example name='value'>",
If the value contains one of the quoting characters,
then use the other to quote the value,
e.g., "<example name='"'>",
If the value contains both quoting characters,
then use one of them to quote the value,
and replace occurrances of that character in the attribute value with
either '&apos;' (apostrophe) or "&quot;" (quotation),
e.g., "<example name='"&apos;"'>".
</p>
<p>
If you want to put a comment in your source file,
here's the syntax:
</p>
</font><pre>
<!-- comments can be multiline,
if you wish -->
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
Finally,
XML is case sensitive.
</p>
<h4><a name="front_matter">2.2</a> Front matter</h4>
<p>
Immediately following the "<rfc>" tag is the "front"
element:
</p>
</font><pre>
<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<rfc>
<front>
<title ...>
<author ...>
<author ...>
<date ...>
<area ...>
<workgroup ...>
<keyword ...>
<keyword ...>
<abstract ...>
<note ...>
</front>
...
</rfc>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
(Note that in all examples,
indentation is used only for expository purposes.)
</p>
<p>
The "front" element consists of a "title" element,
one or more "author" elements,
a "date" element,
one or more optional "area" elements,
one or more optional "workgroup" elements,
one or more optional "keyword" elements,
an optional "abstract" element.
and,
one or more optional "note" elements.
</p>
<h4><a name="anchor3">2.2.1</a> The title Element</h4>
<p>
The "title" element identifies the title of the document.
Because the title will be used in the headers of the document when formatted
according to <a href="#refs.RFC2223">[2]</a>,
if the title is more than 42 characters,
then an abbreviation should also be provided,
e.g.,
</p>
</font><pre>
<title abbrev="Much Ado about Nothing">
The IETF's Discussion on "Source Format of RFC Documents"
</title>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<h4><a name="author">2.2.2</a> The author Element</h4>
<p>
Each "author" element identifies a document author.
Since a document may have more than one author,
more than one "author" element may be present.
If the author is a person,
then three attributes must be present in the "<author>" tag,
"initials", "surname", and "fullname",
e.g.,
</p>
</font><pre>
<author initials="M.T." surname="Rose"
fullname="Marshall T. Rose">
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "author" element itself consists of an "organization" element,
and,
an optional "address" element.
</p>
<p>
The "organization" element is similar to the "title"
element,
in that an abbreviation may be paired with a long organization name
using the "abbrev" attribute, e.g.,
</p>
</font><pre>
<organization abbrev="ISI">
USC/Information Sciences Institute
</organization>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "address" element consists of an optional "postal" element,
an optional "phone" element,
an optional "facsimile" element,
an optional "email" element,
and,
an optional "uri" element.
</p>
<p>
The "postal" element contains one or more "street" elements,
followed by any combination of "city", "region" (state or province),
"code" (zipcode or postal code), and "country" elements, e.g.,
</p>
</font><pre>
<postal>
<street>660 York Street</street>
<street>M/S 40</street>
<city>San Francisco</city> <region>CA</region>
<code>94110</code>
<country>US</country>
</postal>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
This flexibility is provided to allow for different national
formats for postal addresses.
Note however,
that although the order of the "city", "region", "code", and "country"
elements isn't specified,
at most one of each may be present.
Regardless,
these elements must not be re-ordered during processing by an XML
application
(e.g., display applications must preserve the ordering of the
information contained in these elements).
Finally,
the value of the "country" element should be a two-letter
code from ISO 3166.
</p>
<p>
The "phone", "facsimile", "email", and "uri" elements are
simple, e.g.,
</p>
</font><pre>
<phone>+1 415 695 3975</phone>
<email>[email protected]</email>
<uri>http://invisible.net/</uri>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<h4><a name="date">2.2.3</a> The date Element</h4>
<p>
The "date" element identifies the publication date of the
document.
It consists of a month and a year, e.g.,
</p>
</font><pre>
<date month="February" year="1999" />
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "date" element also has an optional day attribute.
</p>
<h4><a name="anchor4">2.2.4</a> Meta Data Elements</h4>
<p>
The "front" element may contain meta data --
the content of these elements does not appear in printed versions of
the document.
</p>
<p>
A document has one or more optional "area",
"workgroup" and "keyword" elements, e.g.,
</p>
</font><pre>
<area>General</area>
<workgroup>RFC Beautification Working Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>XML</keyword>
<keyword>Extensible Markup Language</keyword>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "area" elements identify a general category for the
document
(e.g., one of "Applications", "General", "Internet", "Management",
"Operations", "Routing", "Security", "Transport", or "User"),
while the "workgroup" elements identify the IETF working groups that
produced the document,
and the "keyword" elements identify useful search terms.
</p>
<h4><a name="anchor5">2.2.5</a> The abstract Element</h4>
<p>
A document may have an "abstract" element,
which contains one or more <a href="#t">"t" elements</a>.
In general,
only a single "t" element is present,
e.g.,
</p>
</font><pre>
<abstract>
<t>This memo presents a technique for using XML
(Extensible Markup Language) as a source format
for documents in the Internet-Drafts (I-Ds) and
Request for Comments (RFC) series.</t>
</abstract>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<h4><a name="anchor6">2.2.6</a> The note Element</h4>
<p>
A document may have one or more "note" elements,
each of which contains one or more <a href="#t">"t" elements</a>.
There is a mandatory "title" attribute.
In general,
the "note" element contains text from the IESG,
e.g.,
</p>
</font><pre>
<note title="IESG Note">
<t>The IESG has something to say.</t>
</note>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<h4><a name="anchor7">2.2.7</a> Status, Copyright Notice, Table of Contents</h4>
<p>
Note that text relating to the memo's status, copyright notice, or
table of contents is not included in the document's markup -- this is
automatically inserted by an XML application when it produces either
a text or HTML version of the document.
</p>
<h4><a name="ipr">2.2.7.1</a> Conformance with RFC 2026</h4>
<p>
If an Internet-Draft is being produced,
then the "ipr" attribute should be present in the "<rfc>"
tag at the beginning of the file.
The value of the attribute should be one of:
<blockquote class="text"><dl>
<dt>full2026:</dt>
<dd>
indicating that the document is in full conformance with all
the provisions of Section 10 of RFC 2026;
</dd>
<dt>noDerivativeWorks2026:</dt>
<dd>
indicating that the document is in full
conformance with all the provisions of Section 10 of RFC 2026 except that the
right to produce derivative works is not granted; or,
</dd>
<dt>none:</dt>
<dd>
indicating that the document is NOT offered in accordance with
Section 10 of RFC 2026, and the author does not provide the IETF with any rights
other than to publish as an Internet-Draft.
</dd>
</dl></blockquote>
<p>
In the latter case,
a copyright notice will not be automatically inserted during
processing by an XML application.
</p>
<p>
Consult <a href="#refs.RFC2026">[3]</a> for further details.
</p>
<p>
Finally,
if the Internet-Draft is being submitted to an automated process,
then the "docName" attribute should be present in the "<rfc>"
tag at the beginning of the file.
The value of this attribute contains the document (not file) name
associated with this Internet-Draft, e.g.,
</p>
</font><pre>
<rfc ipr="full" docName="draft-mrose-writing-rfcs-01">
...
</rfc>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
</p>
<h4><a name="anchor8">2.2.8</a> Everything in the Front</h4>
<p>
So,
putting it all together, we have, e.g.,
</p>
</font><pre>
<front>
<title>Writing I-Ds and RFCs using XML</title>
<author initials="M.T." surname="Rose"
fullname="Marshall T. Rose">
<organization>Invisible Worlds, Inc.</organization>
<address>
<postal>
<street>660 York Street</street>
<street>M/S 40</street>
<city>San Francisco</city> <region>CA</region>
<code>94110</code>
<country>US</country>
</postal>
<phone>+1 415 695 3975</phone>
<email>[email protected]</email>
<uri>http://invisible.net/</uri>
</address>
</author>
<date month="February" year="1999" />
<area>General</area>
<workgroup>RFC Beautification Working Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>XML</keyword>
<keyword>Extensible Markup Language</keyword>
<abstract>
<t>This memo presents a technique for using XML
(Extensible Markup Language) as a source format
for documents in the Internet-Drafts (I-Ds) and
Request for Comments (RFC) series.</t>
</abstract>
</front>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<h4><a name="anchor9">2.3</a> The Middle</h4>
<p>
The "middle" element contains all the sections of the document
except for the bibliography and appendices:
</p>
</font><pre>
...
</front>
<middle>
<section ...>
<section ...>
<section ...>
</middle>
<back>
...
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "middle" element consists of one or more "section"
elements.
</p>
<h4><a name="section">2.3.1</a> The section Element</h4>
<p>
Each "section" element contains a section of the document.
There is a mandatory attribute,
"title",
that identifies the title of the section.
There is also an optional attribute,
"anchor",
that is used for cross-referencing with
<a href="#xref">the "xref" element</a>,
e.g.,
</p>
</font><pre>
<section anchor="intro" title="Introduction">
...
</section>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "section" element is recursive --
each contains any number and combination of "t", "figure", and "section"
elements, e.g.,
</p>
</font><pre>
<section title="The Middle">
...
<section title="The section Element">
...
<section title="The t Element">...</section>
<section title="The list Element">...</section>
<section title="The figure Element">...</section>
<section title="The xref Element">...</section>
<section title="The eref Element">...</section>
<section title="The iref Element">...</section>
</section>
</section>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<h4><a name="t">2.3.1.1</a> The t Element</h4>
<p>
The "t" element contains any number and combination of
paragraphs, lists, and figures.
If a cross-reference is needed to a section, figure, or reference,
<a href="#xref">the "xref" element</a> is used;
similarly,
if an external-reference is needed,
<a href="#eref">the "eref" element</a> is used.
Indexing of text is provided by the
<a href="#iref">the "iref" element</a>.
</p>
<h4><a name="anchor10">2.3.1.2</a> The list Element</h4>
<p>
The "list" element contains one or more items.
Each item is a "t" element,
allowing for recursion, e.g.,
</p>
</font><pre>
<list style="numbers">
<t>The first item.</t>
<t>The second item, which contains two bulleted sub-items:
<list style="symbols">
<t>The first sub-item.</t>
<t>The second sub-item.</t>
</list>
</t>
</list>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "list" element has an optional attribute,
"style",
having the value "numbers" (for numeric lists),
"symbols" (for bulleted lists),
"hanging" (for hanging lists),
or,
"empty" (for indented text).
If a "list" element is nested,
the default value is taken from its closest parent;
otherwise,
the default value is "empty".
</p>
<p>
When nested within a "hanging list" element,
the "t" element has an optional attribute,
"hangText" that specifies the text to be inserted, e.g.,
</p>
</font><pre>
<list style="hanging">
<t hangText="full2026:">indicating that the document is in
full conformance with all the provisions of Section 10 of
RFC 2026;</t>
<t hangText="noDerivativeWorks2026:">indicating that the
document is in full conformance with all the provisions of
Section 10 of RFC 2026 except that the right to produce
derivative works is not granted; or,</t>
<t hangText="none:">indicating that the document is NOT
offered in accordance with Section 10 of RFC 2026, and
the author does not provide the IETF with any rights other
than to publish as an Internet-Draft.</t>
</list>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<h4><a name="figure">2.3.1.3</a> The figure Element</h4>
<p>
The "figure" element groups an optional "preamble" element,
an "artwork" element,
and an optional "postamble" element together.
The "figure" element also has an optional "anchor" attribute that is
used for cross-referencing with
<a href="#xref">the "xref" element</a>.
There is also an optional "title" attribute that identifies the title
of the figure.
</p>
<p>
The "preamble" and "postamble" elements,
if present,
are simply text.
If a cross-reference is needed to a section, figure, or reference,
<a href="#xref">the "xref" element</a> is used;
similarly,
if an external-reference is needed,
<a href="#eref">the "eref" element</a> is used.
Indexing of text is provided by the
<a href="#iref">the "iref" element</a>.
</p>
<p>
The "artwork" element,
which must be present,
contains "ASCII artwork".
Unlike text contained in the "t", "preamble", or "postamble" elements,
both horizontal and vertical whitespace is significant in the "artwork"
element.
</p>
<p>
So,
putting it all together, we have, e.g.,
</p>
</font><pre>
<figure anchor="figure_example">
<preamble>So,
putting it all together, we have, e.g.,</preamble>
<artwork>
ascii artwork goes here...
be sure to use "&lt;" or "&amp;" instead of "<" and "&",
respectively!
</artwork>
<postamble>which is a very simple example.</postamble>
</figure>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
which is a very simple example.
</p>
<p>
If you have artwork with a lot of "<" characters,
then there's an XML trick you can use:
</p>
</font><pre>
<figure>
<preamble>If you have artwork with a lot of "&lt;"
characters, then there's an XML trick you can
use:</preamble>
<artwork><![CDATA[
ascii artwork goes here...
just don't use "]]" in your artwork!
]]></artwork>
<postamble>The "&lt;![CDATA[ ... ]]>" construct is called
a CDATA block -- everything between the innermost brackets
is left alone by the XML application.</postamble>
</figure>
</pre><font face="verdana, helvetica, arial, sans-serif" size="2">
<p>
The "<![CDATA[ ... ]]>" construct is called a CDATA
block -- everything between the innermost brackets is left alone by
the XML application.
</p>
<p>
Because the "figure" element represents a logical grouping of text
and artwork,
an XML application producing a text version of the document should
attempt to keep these elements on the same page.
Because <a href="#refs.RFC2223">RFC 2223</a>[2] allows no more than 69
characters by 49 lines of content on each page,
XML applications should be prepared to prematurely introduce page
breaks to allow for better visual grouping.
</p>
<p>
Finally,
the "artwork" element has two optional attributes:
"name" and "type".
The former is used to suggest a filename to use when storing the
content of the "artwork" element,
whilst the latter contains a suggestive data-typing for the content.
</p>
<h4><a name="xref">2.3.1.4</a> The xref Element</h4>
<p>
The "xref" element is used to cross-reference sections, figures, and
references.
The mandatory "target" attribute is used to link back to the "anchor"
attribute of the "section", "figure", and "reference" elements.
The value of the "anchor" and "target" attributes should be formatted