/[suikacvs]/doc/rfc-ja/rfc2629-ja.html
Suika

Contents of /doc/rfc-ja/rfc2629-ja.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1 - (show annotations) (download) (as text)
Fri May 3 06:21:37 2002 UTC (22 years ago) by wakaba
Branch: MAIN
File MIME type: text/html
*** empty log message ***

1 <?xml version="1.0" encoding="iso-2022-jp"?>
2 <?xml-stylesheet href="http://suika.fam.cx/~wakaba/lang/rfc/translate/rfc-ja-style.css" type="text/css"?>
3 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns:h="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/1999/xhtml">
5 <head profile="http://suika.fam.cx/~wakaba/lang/rfc/translate/html-profile">
6 <meta http-equiv="Content-Style-Type" content="text/css"/>
7 <title>
8 RFC 2629:
9 XML $B$r;H$C$F(B I-D $B$d(B RFC $B$r=q$/(B (Writing I-Ds and RFCs using XML)
10 </title>
11 <link rel="stylesheet" href="http://suika.fam.cx/~wakaba/lang/rfc/translate/rfc-ja-style.css" type="text/css"/>
12 <meta name="ietf-area" content="General"/>
13 <meta name="keyword" xml:lang="en" content="RFC, Request for Comments, I-D, Internet-Draft, XML, Extensible Markup Language, "/>
14 <meta name="keyword" content="$B3HD%%^!<%/IU$18@8l(B, "/>
15 </head>
16 <body>
17 <div id="rfc--table">
18 <ul id="rfc--table-left">
19 <li>Network Working Group</li>
20 <li>Request for Comments: 2629</li>
21 <li>
22 <span class="t-pair">
23 <span xml:lang="en" class="t-l-en t-hide-no">Category: Informational</span>
24 </span>
25 </li>
26 <li>
27 <span class="t-pair">
28 <span xml:lang="ja" class="t-l-ja">$BJ,N`(B: $B;29M(B</span>
29 </span>
30 </li>
31 </ul>
32 <ul id="rfc--table-right">
33 <li title="Marshall T. Rose">M.T. Rose</li>
34 <li>Invisible Worlds, Inc.</li>
35 <li>
36 <span class="t-pair">
37 <span xml:lang="en" class="t-l-en"> June 1999</span>
38 </span>
39 </li>
40 <li>
41 <span class="t-pair">
42 <span xml:lang="ja" class="t-l-ja">1999$BG/(B6$B7n(B</span>
43 </span>
44 </li>
45 </ul>
46 </div>
47 <div class="t-pair t-heading" id="rfc-title">
48 <h1 class="rfc-title t-l-en" xml:lang="en">Writing I-Ds and RFCs using XML</h1>
49 <h1 class="rfc-title t-l-ja" xml:lang="ja">XML $B$r;H$C$F(B I-D $B$d(B RFC $B$r=q$/(B</h1>
50 </div>
51 <div id="rfc-status" class="rfc-section">
52 <div class="t-pair">
53 <h1 xml:lang="en" class="t-l-en">Status of this Memo</h1>
54 <h1 xml:lang="ja" class="t-l-ja">$B$3$N%a%b$N0LCVIU$1(B</h1>
55 </div>
56 <div class="rfc-t">
57 <div class="t-pair">
58 <p class="t-l-en" xml:lang="en">
59 This memo provides information for the Internet community.
60 It does not specify an Internet standard of any kind.
61 Distribution of this memo is unlimited.
62 </p>
63 <p class="t-l-ja" xml:lang="ja">
64 $B$3$N%a%b$O!"(B Internet $B<R2q$K>pJs$rDs6!$7$^$9!#$$$+$J$k<oN`$N(B
65 Internet $BI8=`$r5,Dj$9$k$b$N$G$b$"$j$^$;$s!#$3$N%a%b$NG[I[$O@)8B$7$^$;$s!#(B
66 </p>
67 </div>
68 </div>
69 </div>
70 <div id="rfc-copyright-notice" class="rfc-section">
71 <div class="t-pair">
72 <h1 xml:lang="en" class="t-l-en">Copyright Notice</h1>
73 <h1 xml:lang="ja" class="t-l-ja">$BCx:n8"I=<((B</h1>
74 </div>
75 <div class="t-pair">
76 <p class="t-l-en t-hide-no" xml:lang="en">Copyright &#x00A9;
77 <a href="http://www.isoc.org/">The Internet Society</a>
78 (1999).
79 All Rights Reserved.</p>
80 <p class="t-l-ja" xml:lang="ja">$BCx:n8"(B &#x00A9;
81 <a href="http://www.isoc.org/">The Internet Society</a>
82 (1999)$B!#A48"J]N1!#(B</p>
83 </div>
84 </div>
85 <div class="rfc-section" id="rfc.abstract">
86 <div class="t-pair t-heading">
87 <h1 xml:lang="en" class="t-l-en">Abstract</h1>
88 <h1 xml:lang="ja" class="t-l-ja">$B35MW(B</h1>
89 </div>
90 <div class="rfc-t">
91 <div class="t-pair">
92 <p xml:lang="en" class="t-l-en">
93 This memo presents a technique for using XML
94 (Extensible Markup Language)
95 as a source format for documents in the Internet-Drafts (I-Ds)
96 and Request for Comments (RFC) series.
97 </p>
98 <p xml:lang="ja" class="t-l-ja">
99 $B$3$N%a%b$O!"(B XML ($B3HD%%^!<%/IU$18@8l(B) $B$r(B Internet-Draft (I-D)
100 $B$d(B Request for Comments (RFC) $B7ONs$NJ8=q$N867A<0$H$7$F;HMQ$9$k<jK!$r@bL@$7$^$9!#(B
101 </p>
102 </div>
103 </div>
104 </div>
105
106 <div class="rfc-section" id="rfc.section.1">
107 <div class="t-pair t-heading">
108 <h1 xml:lang="en" class="t-l-en">1. Introduction</h1>
109 <h1 xml:lang="ja" class="t-l-ja">1.
110 $B$O$8$a$K(B</h1>
111 </div>
112 <div class="rfc-t" id="rfc.section.1.p.1">
113 <div class="t-pair">
114 <p xml:lang="en" class="t-l-en">
115 This memo describes how to write a document for the I-D and
116 RFC series using <span class="rfc-xref">
117 <a href="#XML" title="Extensible Markup Language (XML) 1.0">the Extensible Markup
118 Language
119 &#x00A0;<sup>[1]</sup>
120 </a>
121 </span> (XML). This memo has three goals:
122 </p>
123 <p xml:lang="ja" class="t-l-ja">
124 $B$3$N%a%b$O!"(B I-D $B$*$h$S(B RFC
125 $B7ONs$NJ8=q$r(B<a href="#XML" title="$B3HD%2DG=%^!<%/IU$18@8l(B (XML) 1.0">$B3HD%%^!<%/IU$18@8l(B
126 &#x00A0;<sup>[1]</sup>
127 </a> (XML)
128 $B$r;H$C$F=q$/J}K!$r@bL@$7$^$9!#$3$N%a%b$K$O!";0$D$NL\E*$,$"$j$^$9!#(B
129 </p>
130 </div>
131
132 <ol class="rfc-list-numbers text">
133 <li>
134 <div class="t-pair">
135 <p xml:lang="en" class="t-l-en">
136 To describe a simple XML Document Type Definition (DTD) that is
137 powerful enough to handle the simple formatting requirements of RFC-like
138 documents whilst allowing for meaningful markup of descriptive
139 qualities.
140 </p>
141 <p xml:lang="ja" class="t-l-ja">
142 $B0UL#%^!<%/IU$1$N5-=RIJ<A$,2DG=$J(B RFC
143 $B7?J8=q$NC1=c$J=q<0$E$1MW7o$r<h$j07$&$N$K==J,6/NO$G$"$k(B XML
144 $BJ8=q7?Dj5A(B (DTD) $B$N@bL@(B
145 </p>
146 </div>
147 </li>
148 <li>
149 <div class="t-pair">
150 <p xml:lang="en" class="t-l-en">
151 To describe software that processes XML source files,
152 including a tool that produces documents
153 conforming to <span class="rfc-xref">
154 <a href="#refs.RFC2223" title="Instructions to RFC Authors">RFC 2223
155 &#x00A0;<sup>[2]</sup>
156 </a>
157 </span>,
158 HTML format, and so on.
159 </p>
160 <p xml:lang="ja" class="t-l-ja">
161 <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">RFC 2223
162 &#x00A0;<sup>[2]</sup>
163 </a> $B$KE,9g$9$kJ8=q(B,
164 HTML $B7A<0(B, $B$=$NB>$r@8@.$9$kF;6q$r4^$`!"(B
165 XML $B8;%U%!%$%k$r=hM}$9$k%=%U%H%&%'%"$N@bL@(B
166 </p>
167 </div>
168 </li>
169 <li>
170 <div class="t-pair">
171 <p xml:lang="en" class="t-l-en">
172 To provide the proof-of-concept for the first two goals
173 (this memo was written using this DTD and produced using that
174 software).
175 </p>
176 <p xml:lang="ja" class="t-l-ja">
177 $BA0=R$N(B2$B$D$NL\E*$N35G0$N>ZL@$NDs6!(B ($B$3$N%a%b$O$=$N(B DTD
178 $B$r;H$C$F<9I.$5$l!"$=$&$7$?%=%U%H%&%'%"$r;H$C$F@8@.$5$l$^$7$?!#(B)
179 </p>
180 </div>
181 </li>
182 </ol>
183 </div>
184 <div class="rfc-t" id="rfc.section.1.p.2">
185 <div class="t-pair">
186 <p xml:lang="en" class="t-l-en">
187 It is beyond the scope of this memo to discuss the political
188 ramifications of using XML as a source format for RFC-like documents.
189 Rather,
190 it is simply noted that adding minimal markup to plain text:
191 </p>
192 <p xml:lang="ja" class="t-l-ja">
193 RFC $BE*J8=q$N8;7A<0$H$7$F(B XML $B$r;H$&$3$H$N@/<#E*5DO@$O$3$N%a%b$NE,MQHO0O30$G$9!#$=$l$h$j$b!"J?J8(B (plain text) $B$K:G>.$N%^!<%/IU$1$r2C$($k$3$H$G!"(B
194 </p>
195 </div>
196
197 <ul class="rfc-list-symbols text">
198 <li>
199 <div class="t-pair">
200 <p xml:lang="en" class="t-l-en">
201 allows the traditional production of textual RFC-like documents using
202 familiar editors;
203 </p>
204 <p xml:lang="ja" class="t-l-ja">
205 $B$h$/CN$i$l$F$$$k%(%G%#%?!<$r;H$C$FJ8;z$J(B RFC $BE*J8=q$NEAE}E*@8@.$,2DG=$K$J$k(B
206 </p>
207 </div>
208 </li>
209 <li>
210 <div class="t-pair">
211 <p xml:lang="en" class="t-l-en">
212 requires some, albeit minimal, additions to existing software
213 environments; and,
214 </p>
215 <p xml:lang="ja" class="t-l-ja">
216 $B4v$D$+!":GDc$G$b!"4{B8$N%=%U%H%&%'%"4D6-$KDI2C$,I,MW$G$"$k(B
217 </p>
218 </div>
219 </li>
220 <li>
221 <div class="t-pair">
222 <p xml:lang="en" class="t-l-en">
223 permits information to be organized, searched, and retrieved
224 using both unstructured and structured mechanisms.
225 </p>
226 <p xml:lang="ja" class="t-l-ja">
227 $BHs9=B$2=!&9=B$2=$NN>5!9=$r;H$C$F>pJs$rAH?%2=$7$?$j8!:w$7$?$j<h$j=P$7$?$j=PMh$k(B
228 </p>
229 </div>
230 </li>
231 </ul>
232
233 <div class="t-pair">
234 <p xml:lang="ja" class="t-l-ja">
235 $B$H$$$&$3$H$rC1$K5-$9$b$N$G$9!#(B
236 </p>
237 </div>
238 </div>
239 </div>
240
241 <div class="rfc-section" id="rfc.section.2">
242 <div class="t-pair t-heading">
243 <h1 xml:lang="en" class="t-l-en">2. Using the DTD to Write I-Ds and RFCs</h1>
244 <h1 xml:lang="ja" class="t-l-ja">2.
245 I-D $B$d(B RFC $B$r=q$/$N$K(B DTD $B$r;H$&(B</h1>
246 </div>
247 <div class="rfc-t" id="rfc.section.2.p.1">
248 <div class="t-pair">
249 <p xml:lang="en" class="t-l-en">
250 We do not provide a formal or comprehensive description of XML.
251 Rather,
252 this section discusses just enough XML to use a Document Type
253 Declaration (DTD) to write RFC-like documents.
254 </p>
255 <p xml:lang="ja" class="t-l-ja">
256 XML $B$K$D$$$F$N@5<0$J!"$"$k$$$OJq3gE*$J@bL@$O$7$^$;$s!#(B
257 $B$3$N@a$G$O!"(B RFC $BE*J8=q$r=q$/$?$a$NJ8=q7?@k8@(B (DTD)
258 $B$r;H$&$N$KI,MW$J$@$1$NOC$r$7$^$9!#(B
259 </p>
260 </div>
261 </div>
262 <div class="rfc-t" id="rfc.section.2.p.2">
263 <div class="t-pair">
264 <p xml:lang="en" class="t-l-en">
265 If you're already familiar with XML,
266 skip to <span class="rfc-xref">
267 <a href="#rfc.dtd" title="The RFC DTD">
268 section 2</a>
269 </span> to look at the DTD.
270 </p>
271 <p xml:lang="ja" class="t-l-ja">
272 XML $B$K$D$$$F4{$K$h$/J,$+$C$F$$$k$J$i!"(B<a href="#rfc.dtd" title="The RFC DTD">
273 $BImB0=q(BB</a>$B$KHt$s$G!"(B DTD $B$r8fMw2<$5$$!#(B
274 </p>
275 </div>
276 </div>
277
278 <div class="rfc-section" id="rfc.section.2.1">
279 <div class="t-pair t-heading" id="xml_basics">
280 <h2 xml:lang="en" class="t-l-en">2.1. XML basics</h2>
281 <h2 xml:lang="ja" class="t-l-ja">2.1.
282 XML $B$N4pAC(B</h2>
283 </div>
284 <div class="rfc-t" id="rfc.section.2.1.p.1">
285 <div class="t-pair">
286 <p xml:lang="en" class="t-l-en">
287 There are very few rules when writing in XML,
288 as the syntax is simple.
289 There are five terms you'll need to know:
290 </p>
291 <p xml:lang="ja" class="t-l-ja">
292 XML $B$O9=J8$,4JC1$J$N$G!"=q$/;~$KI,MW$J$N$O$[$s$N>/$7$N5,B'$@$1$G$9!#CN$C$F$*$/$Y$-$3$H$O(B5$B$D$"$j$^$9!#(B
293 </p>
294 </div>
295
296 <ol class="rfc-list-numbers text">
297 <li>
298 <div class="t-pair">
299 <p xml:lang="en" class="t-l-en">
300 An $B!H(Belement$B!I(B usually refers to a start tag, an end tag, and all the
301 characters in between,
302 e.g.,
303 "&lt;example&gt;text and/or nested elements&lt;/example&gt;"
304 </p>
305 <p xml:lang="ja" class="t-l-ja">
306 $B!VMWAG!W$ODL>o3+;O%?%0$H=*N;%?%0!"$=$l$K4V$NA4$F$NJ8;z!"Nc$($P(B
307 <samp>$B!V(B&lt;$BNc(B&gt;$BJ8;z$H$+F~$l;R$NMWAG(B&lt;/$BNc(B&gt;$B!W(B</samp>
308 $B$r;X$7$^$9!#(B
309 </p>
310 </div>
311 </li>
312 <li>
313 <div class="t-pair">
314 <p xml:lang="en" class="t-l-en">
315 An "empty element" combines the start tag and the end tag,
316 e.g.,
317 "&lt;empty/&gt;".
318 You don't find these in HTML.
319 </p>
320 <p xml:lang="ja" class="t-l-ja">
321 $B!V6uMWAG!W$O3+;O%?%0$H=*N;%?%0$,$/$C$D$$$F!"(B
322 <samp>$B!V(B&lt;$B6u(B/&gt;$B!W(B</samp> $B$N$h$&$K$J$j$^$9!#(B
323 HTML $B$K$O$3$l$O$"$j$^$;$s!#(B
324 </p>
325 </div>
326 </li>
327 <li>
328 <div class="t-pair">
329 <p xml:lang="en" class="t-l-en">
330 An "attribute" is part of an element.
331 If present, they occur in the start tag, e.g.,
332 "&lt;example name='value'&gt;".
333 Of course,
334 they can also appear in empty elements, e.g.,
335 "&lt;empty name='value'/&gt;".
336 </p>
337 <p xml:lang="ja" class="t-l-ja">
338 $B!VB0@-!W$OMWAG$N0lIt$G$9!#B8:_$9$k>l9g!"3+;O%?%0Cf$K!"(B
339 <samp>$B!V(B&lt;$BNc(B $BL>A0(B='$BCM(B'&gt;$B!W(B</samp>
340 $B$NMM$K8=$l$^$9!#$b$A$m$s!"6uMWAGCf$G$b(B
341 <samp>$B!V(B&lt;$B6u(B $BL>A0(B='$BCM(B'/&gt;$B!W(B</samp> $B$NMM$K;H$($^$9!#(B
342 </p>
343 </div>
344 </li>
345 <li>
346 <div class="t-pair">
347 <p xml:lang="en" class="t-l-en">
348 An "entity" is a textual macro that starts with "&amp;".
349 Don't worry about these,
350 you'll only use them whenever you want to put a "&amp;" or a "&lt;" in
351 your text.
352 </p>
353 <p xml:lang="ja" class="t-l-ja">
354 $B!V<BBN!W$OJ8;z%^%/%m$G!"!V(B&amp;$B!W$G;O$^$j$^$9!#(B
355 $B$J!A$K?4G[$7$J$5$s$J!"!V(B&amp;$B!W$d!V(B&lt;$B!W$rJ8Cf$KF~$l$?$$;~$K$@$1$$$D$G$b;H$&$3$H$,=PMh$^$9!#(B
356 </p>
357 </div>
358 </li>
359 <li>
360 <div class="t-pair">
361 <p xml:lang="en" class="t-l-en">
362 A "token" is a string of characters.
363 The first character is either a letter or an underscore ("_").
364 Any characters that follow are either letters, numbers, an
365 underscore, or a period (".").
366 </p>
367 <p xml:lang="ja" class="t-l-ja">
368 $B!V;z6g(B (token)$B!W(B $B$OJ8;z$NNs$G$9!#:G=i$NJ8;z$OJ8;z$+2<@~(B ($B!V(B_$B!W(B)
369 $B$G$9!#$=$N8e$NJ8;z$OJ8;z!"?t;z!"2<@~!"6gE@(B ($B!V(B.$B!W(B) $B$G$9!#(B
370 <ins class="t-note t-l-ja" xml:lang="ja">
371 (<span class="t-note-title">$BLuCm(B:</span>$B$3$3$GJ8;z$H$O!"(B26$B!_(B2$B<oN`$N4pK\%i%F%s;zJl$N$3$H$G$9!#(B)
372 </ins>
373 </p>
374 </div>
375 </li>
376 </ol>
377 </div>
378 <div class="rfc-figure">
379 <span class="rfc-figure-id" id="rfc.figure.u.1">&#x00A0;</span>
380 <div class="rfc-preamble">
381 <div class="t-pair">
382 <p xml:lang="en" class="t-l-en">
383 First,
384 start your source file with an XML declaration,
385 a reference to the DTD,
386 and the "rfc" element:
387 </p>
388 <p xml:lang="ja" class="t-l-ja">
389 $B:G=i$K!"8;%U%!%$%k$O(B XML $B@k8@(B, DTD $B$X$N;2>H(B, $B!V(Brfc$B!WMWAG$G;O$a$^$9!#(B
390 </p>
391 </div>
392 </div>
393 <pre class="rfc-artwork" xml:space="preserve">
394 &lt;?xml version="1.0"?&gt;
395 &lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd"&gt;
396 &lt;rfc&gt;
397 ...
398 &lt;/rfc&gt;
399 </pre>
400 <div class="rfc-postamble">
401 <div class="t-pair">
402 <p xml:lang="en" class="t-l-en">
403 Ignore the first two lines
404 $B!=!=(B the declaration and the reference $B!=!=(B
405 and simply treat them as opaque strings.
406 Nothing else should be present after the "&lt;/rfc&gt;" tag.
407 </p>
408 <p xml:lang="ja" class="t-l-ja">
409 $B:G=i$N(B2$B9T(B ($B@k8@$H;2>H(B) $B$OL5;k$7!"C1$K<vJ8$@$H;W$C$F2<$5$$!#(B
410 $B!V(B&lt;/rfc&gt;$B!W%?%0$N8e$K$O2?$b8=$l$k$Y$-$G$O$"$j$^$;$s!#(B
411 <ins class="t-note t-l-ja" xml:lang="ja">
412 (<span class="t-note-title">$BLuCm(B:</span>rfc $BMWAG$K$D$$$F$O!"(B <a href="#rfc" title="rfc $BMWAG(B">
413 $BImB0=q(BA</a> $B$K@bL@$,$"$j$^$9!#(B)
414 </ins>
415 </p>
416 </div>
417 </div>
418 </div>
419 <div class="rfc-t" id="rfc.section.2.1.p.3">
420 <div class="t-pair">
421 <p xml:lang="en" class="t-l-en">
422 Second,
423 make sure that all elements are properly matched and nested.
424 A properly matched element that starts with
425 "&lt;example&gt;" is eventually followed with "&lt;/example&gt;".
426 (Empty elements are always matched.)
427 Elements are properly nested when they don't overlap.
428 </p>
429 <p xml:lang="ja" class="t-l-ja">
430 $BFsHVL\$K!"A4$F$NMWAG$,E,@Z$KBP1~!&F~$l;R$K$J$C$F$$$k$+3N$+$a$F2<$5$$!#(B
431 <samp>$B!V(B&lt;$BNc(B&gt;$B!W(B</samp> $B$G;O$^$kE,@Z$KBP1~$9$kMWAG$O!":G=*E*$K$O(B
432 <samp>$B!V(B&lt;/$BNc(B&gt;$B!W(B</samp> $B$,B3$/$3$H$K$J$j$^$9!#(B
433 ($B6uMWAG$O>o$KBP1~$7$F$$$^$9!#(B)
434 $B3FMWAG$O=EJ#$7$F$$$J$$;~$GE,@Z$KF~$l;R$K$J$C$F$$$^$9!#(B
435 </p>
436 </div>
437 </div>
438 <div class="rfc-figure">
439 <span class="rfc-figure-id" id="rfc.figure.u.2">&#x00A0;</span>
440 <div class="rfc-preamble">
441 <div class="t-pair">
442 <p xml:lang="en" class="t-l-en">
443 For example,
444 </p>
445 <p xml:lang="ja" class="t-l-ja">
446 $BNc$($P!"(B
447 </p>
448 </div>
449 </div>
450 <pre class="rfc-artwork" xml:space="preserve">
451 &lt;outer&gt;
452 ...
453 &lt;inner&gt;
454 ...
455 &lt;/inner&gt;
456 ...
457 &lt;/outer&gt;
458 </pre>
459 <div class="rfc-postamble">
460 <div class="t-pair">
461 <p xml:lang="en" class="t-l-en">
462 is properly nested.
463 </p>
464 <p xml:lang="ja" class="t-l-ja">
465 $B$OE,@Z$KF~$jAH$s$G$$$^$9!#(B
466 </p>
467 </div>
468 </div>
469 </div>
470 <div class="rfc-figure">
471 <span class="rfc-figure-id" id="rfc.figure.u.3">&#x00A0;</span>
472 <div class="rfc-preamble">
473 <div class="t-pair">
474 <p xml:lang="en" class="t-l-en">
475 However,
476 </p>
477 <p xml:lang="ja" class="t-l-ja">
478 $B$7$+$7!"(B
479 </p>
480 </div>
481 </div>
482 <pre class="rfc-artwork" xml:space="preserve">
483 &lt;outer&gt;
484 ...
485 &lt;inner&gt;
486 ...
487 &lt;/outer&gt;
488 ...
489 &lt;/inner&gt;
490 </pre>
491 <div class="rfc-postamble">
492 <div class="t-pair">
493 <p xml:lang="en" class="t-l-en">
494 overlaps, so the elements aren't properly nested.
495 </p>
496 <p xml:lang="ja" class="t-l-ja">
497 $B$O=E$J$C$F$$$k$N$G!"MWAG$O@5$7$/F~$l;R$K$J$C$F$$$^$;$s!#(B
498 </p>
499 </div>
500 </div>
501 </div>
502 <div class="rfc-t" id="rfc.section.2.1.p.6">
503 <div class="t-pair">
504 <p xml:lang="en" class="t-l-en">
505 Third,
506 never use "&lt;" or "&amp;" in your text.
507 Instead, use either "&amp;lt;" or "&amp;amp;", respectively.
508 </p>
509 <p xml:lang="ja" class="t-l-ja">
510 $B;0HVL\$K!"!V(B&lt;$B!W$d!V(B&amp;$B!W$rJ8Cf$K;H$C$F$O$$$1$^$;$s!#Be$o$j$K!"$=$l$>$l!V(B&amp;lt;$B!W$H!V(B&amp;amp;$B!W$r;H$$$^$9!#(B
511 </p>
512 </div>
513 </div>
514 <div class="rfc-t" id="rfc.section.2.1.p.7">
515 <div class="t-pair">
516 <p xml:lang="en" class="t-l-en">
517 Fourth,
518 there are two quoting characters in XML, 'apostrophe' and "quotation".
519 Make sure that all attributes values are quoted,
520 e.g., "&lt;example name='value'&gt;",
521 If the value contains one of the quoting characters,
522 then use the other to quote the value,
523 e.g., "&lt;example name='"'&gt;",
524 If the value contains both quoting characters,
525 then use one of them to quote the value,
526 and replace occurrances of that character in the attribute value with
527 either '&amp;apos;' (apostrophe) or "&amp;quot;" (quotation),
528 e.g., "&lt;example name='"&amp;apos;"'&gt;".
529 </p>
530 <p xml:lang="ja" class="t-l-ja">
531 $B;MHVL\$K!"(B XML $B$G$O(B '$B%"%]%9%H%m%U%#(B' $B$H(B "$B0zMQ(B"
532 $B$NFs<oN`$N0zMQJ8;z$,$"$j$^$9!#A4$F$NB0@-CM$r!"(B
533 <samp>$B!V(B6lt;$BNc(B $BL>A0(B='$BCM(B'&gt;$B!W(B</samp> $B$NMM$K0zMQId$G0O$`$3$H$r3NG'$7$F2<$5$$!#CM$K0zMQJ8;z$N0lJ}$,;H$o$l$F$$$k;~$O!"(B
534 <samp>$B!V(B&lt;$BNc(B $BL>A0(B='"'&gt;$B!W(B</samp> $B$NMM$KB>J}$rCM$r0O$`$N$K;H$$$^$9!#(B
535 $BCM$,0zMQJ8;z$NN>J}$r4^$s$G$$$k>l9g!"$I$A$i$+$rCM$r0O$`$N$K;H$$!"B0@-CM$K;H$o$l$F$$$kJ8;z$r(B '&amp;apos;' ($B%"%]%9%H%m%U%#(B) $B$^$?$O(B "&amp;quot;"
536 ($B0zMQ(B) $B$KCV$-49$($F!"(B <samp>$B!V(B&lt;$BNc(B $BL>A0(B='"&amp;apos;"'&gt;"$B!W(B</samp>
537 $B$N$h$&$K$7$^$9!#(B
538 </p>
539 </div>
540 </div>
541 <div class="rfc-figure">
542 <span class="rfc-figure-id" id="rfc.figure.u.4">&#x00A0;</span>
543 <div class="rfc-preamble">
544 <div class="t-pair">
545 <p xml:lang="en" class="t-l-en">
546 If you want to put a comment in your source file,
547 here's the syntax:
548 </p>
549 <p xml:lang="ja" class="t-l-ja">
550 $B8;%U%!%$%k$KCm<a$rF~$l$?$$;~$O!"<!$N9=J8$NMM$K$7$^$9!#(B
551 </p>
552 </div>
553 </div>
554
555 <div class="t-pair">
556 <p xml:lang="en" class="t-l-en">
557 <pre class="rfc-artwork" xml:space="preserve">
558 &lt;!-- comments can be multiline,
559 if you wish --&gt;
560 </pre>
561 </p>
562 <p xml:lang="ja" class="t-l-ja">
563 <pre class="rfc-artwork" xml:space="preserve">
564 &lt;!-- $BCm<a9T$O!"I,MW$J$i(B
565 $BJ#?t9T$K=PMh$^$9!#(B --&gt;
566 </pre>
567 <div class="rfc-postamble">
568 <ins class="t-note t-l-ja" xml:lang="ja">
569 (<span class="t-note-title">$BLuCm(B:</span>$B$^$?!"Cm<aCf$K!V(B--$B!W$r;H$C$F$O$$$1$^$;$s!#(B)
570 </ins>
571 </div>
572 </p>
573 </div>
574
575 </div>
576 <div class="rfc-t" id="rfc.section.2.1.p.9">
577 <div class="t-pair">
578 <p xml:lang="en" class="t-l-en">
579 Finally,
580 XML is case sensitive.
581 </p>
582 <p xml:lang="ja" class="t-l-ja">
583 $B8^HVL\$K!"(B XML $B$OBgJ8;z$H>.J8;z$r6hJL$7$^$9!#(B
584 </p>
585 </div>
586 </div>
587 </div>
588
589 <div class="rfc-section" id="rfc.section.2.2">
590 <div id="front_matter">
591 <h2>2.2. Front matter</h2>
592 </div>
593 <div class="rfc-figure">
594 <span class="rfc-figure-id" id="rfc.figure.u.5">&#x00A0;</span>
595 <div class="rfc-preamble">
596 <div class="t-pair">
597 <p xml:lang="en" class="t-l-en">
598 Immediately following the "&lt;rfc&gt;" tag is the "front"
599 element:
600 </p>
601 <p xml:lang="ja" class="t-l-ja">
602 "&lt;rfc&gt;" $B%?%0$ND>$08e$KB3$/$N$O(B "front" $BMWAG$G$9!#(B
603 </p>
604 </div>
605 </div>
606 <pre class="rfc-artwork" xml:space="preserve">
607 &lt;?xml version="1.0"?&gt;
608 &lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd"&gt;
609 &lt;rfc&gt;
610 &lt;front&gt;
611 &lt;title ...&gt;
612 &lt;author ...&gt;
613 &lt;author ...&gt;
614 &lt;date ...&gt;
615 &lt;area ...&gt;
616 &lt;workgroup ...&gt;
617 &lt;keyword ...&gt;
618 &lt;keyword ...&gt;
619 &lt;abstract ...&gt;
620 &lt;note ...&gt;
621 &lt;/front&gt;
622 ...
623 &lt;/rfc&gt;
624 </pre>
625 <div class="rfc-postamble">
626 <div class="t-pair">
627 <p xml:lang="en" class="t-l-en">
628 (Note that in all examples,
629 indentation is used only for expository purposes.)
630 </p>
631 <p xml:lang="ja" class="t-l-ja">
632 ($BA4$F$NNc$G!";z2<$2$O@bL@$N$?$a$@$1$K;H$C$F$$$k$3$H$KCm0U$7$F2<$5$$!#(B)
633 </p>
634 </div>
635 </div>
636 </div>
637 <div class="rfc-t" id="rfc.section.2.2.p.2">
638 <div class="t-pair">
639 <p xml:lang="en" class="t-l-en">
640 The "front" element consists of a "title" element,
641 one or more "author" elements,
642 a "date" element,
643 one or more optional "area" elements,
644 one or more optional "workgroup" elements,
645 one or more optional "keyword" elements,
646 an optional "abstract" element.
647 and,
648 one or more optional "note" elements.
649 </p>
650 <p xml:lang="ja" class="t-l-ja">
651 "front" $BMWAG$O(B "title" $BMWAG(B, 1$B$D0J>e$N(B "author" $BMWAG(B, "date" $BMWAG(B,
652 1$B$D0J>e$N>JN,2DG=$J(B "area" $BMWAG(B,
653 1$B$D0J>e$N>JN,2DG=$J(B "workgroup" $BMWAG(B,
654 1$B$D0J>e$N>JN,2DG=$J(B "keyword" $BMWAG(B,
655 $B>JN,2DG=$J(B "abstract" $BMWAG(B,
656 1$B$D0J>e$N>JN,2DG=$J(B "note" $BMWAG$+$i@.$j$^$9!#(B
657 </p>
658 </div>
659 </div>
660 <div class="rfc-section" id="rfc.section.2.2.1">
661 <div class="t-pair t-heading">
662 <h3 xml:lang="en" class="t-l-en">2.2.1. The title Element</h3>
663 <h3 xml:lang="ja" class="t-l-ja">2.2.1.
664 title $BMWAG(B</h3>
665 </div>
666 <div class="rfc-figure">
667 <span class="rfc-figure-id" id="rfc.figure.u.6">&#x00A0;</span>
668 <div class="rfc-preamble">
669 <div class="t-pair">
670 <p xml:lang="en" class="t-l-en">
671 The "title" element identifies the title of the document.
672 Because the title will be used in the headers of the document when formatted
673 according to <span class="rfc-xref">
674 <a href="#refs.RFC2223" title="Instructions to RFC Authors">[2]</a>
675 </span>,
676 if the title is more than 42 characters,
677 then an abbreviation should also be provided,
678 e.g.,
679 </p>
680 <p xml:lang="ja" class="t-l-ja">
681 "title" $BMWAG$O!"J8=q$NBj$r<1JL$7$^$9!#Bj$O(B
682 <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">[2]</a> $B$K=>$C$F@07A$9$k;~$KJ8=q$NF,$K;H$o$l$k$N$G!"Bj$O(B42$BJ8;z0J>e$N;~$O!">JN,7A$bM?$($k$Y$-$G$9!#Nc$($P!"<!$N$h$&$K$7$^$9!#(B
683 </p>
684 </div>
685 </div>
686 <pre class="rfc-artwork" xml:space="preserve">
687 &lt;title abbrev="Much Ado about Nothing"&gt;
688 The IETF's Discussion on "Source Format of RFC Documents"
689 &lt;/title&gt;
690 </pre>
691 </div>
692 </div>
693 <div class="rfc-section" id="rfc.section.2.2.2">
694 <div class="t-pair t-heading" id="author">
695 <h3 xml:lang="en" class="t-l-en">2.2.2. The author Element</h3>
696 <h3 xml:lang="ja" class="t-l-ja">2.2.2.
697 author $BMWAG(B</h3>
698 </div>
699 <div class="rfc-figure">
700 <span class="rfc-figure-id" id="rfc.figure.u.7">&#x00A0;</span>
701 <div class="rfc-preamble">
702 <div class="t-pair">
703 <p xml:lang="en" class="t-l-en">
704 Each "author" element identifies a document author.
705 Since a document may have more than one author,
706 more than one "author" element may be present.
707 If the author is a person,
708 then three attributes must be present in the "&lt;author&gt;" tag,
709 "initials", "surname", and "fullname",
710 e.g.,
711 </p>
712 <p xml:lang="ja" class="t-l-ja">
713 $B3F(B "author" $BMWAG$O!"J8=q$NMWAG$r<1JL$7$^$9!#J8=q$K$OJ#?t?M$NCx<T$,$$F@$^$9$N$G!"J#?t$N(B
714 "author" $BMWAG$r;H$&$3$H$,=PMh$^$9!#Cx<T$,?MJ*$G$"$k;~$O!"(B
715 "initials" ($BF,J8;z(B), "surname" ($B@+(B), "fullname" ($BA4L>(B) $B$N(B3$B$D$NB0@-$,(B
716 "author" $B%?%0$K$J$1$l$P$J$j$^$;$s!#Nc$($P!"<!$NMM$K$7$^$9!#(B
717 </p>
718 </div>
719 </div>
720 <pre class="rfc-artwork" xml:space="preserve">
721 &lt;author initials="M.T." surname="Rose"
722 fullname="Marshall T. Rose"&gt;
723 </pre>
724 </div>
725 <div class="rfc-t" id="rfc.section.2.2.2.p.2">
726 <div class="t-pair">
727 <p xml:lang="en" class="t-l-en">
728 The "author" element itself consists of an "organization" element,
729 and,
730 an optional "address" element.
731 </p>
732 <p xml:lang="ja" class="t-l-ja">
733 "author" $BMWAG<+?H$O(B "organization" $BMWAG$H!">JN,2DG=$J(B "address"
734 $BMWAG$+$i@.$j$^$9!#(B
735 </p>
736 </div>
737 </div>
738 <div class="rfc-figure">
739 <span class="rfc-figure-id" id="rfc.figure.u.8">&#x00A0;</span>
740 <div class="rfc-preamble">
741 <div class="t-pair">
742 <p xml:lang="en" class="t-l-en">
743 The "organization" element is similar to the "title"
744 element,
745 in that an abbreviation may be paired with a long organization name
746 using the "abbrev" attribute, e.g.,
747 </p>
748 <p xml:lang="ja" class="t-l-ja">
749 "organization" $BMWAG$O(B "title" $BMWAG$HF1$8MM$K!"D9$$AH?%L>$K(B
750 "abbrev" $BB0@-$r;H$C$F<!$NNc$NMM$K>JN,L>$r;XDj$9$k$3$H$,=PMh$^$9!#(B
751 </p>
752 </div>
753 </div>
754 <pre class="rfc-artwork" xml:space="preserve">
755 &lt;organization abbrev="ISI"&gt;
756 USC/Information Sciences Institute
757 &lt;/organization&gt;
758 </pre>
759 </div>
760 <div class="rfc-t" id="rfc.section.2.2.2.p.4">
761 <div class="t-pair">
762 <p xml:lang="en" class="t-l-en">
763 The "address" element consists of an optional "postal" element,
764 an optional "phone" element,
765 an optional "facsimile" element,
766 an optional "email" element,
767 and,
768 an optional "uri" element.
769 </p>
770 <p xml:lang="ja" class="t-l-ja">
771 "address" $BMWAG$O>JN,2DG=$J(B "postal" $BMWAG(B,
772 $B>JN,2DG=$J(B "phone" $BMWAG(B,
773 $B>JN,2DG=$J(B "facsimile" $BMWAG(B,
774 $B>JN,2DG=$J(B "email" $BMWAG(B,
775 $B>JN,2DG=$J(B "uri" $BMWAG$+$i@.$j$^$9!#(B
776 </p>
777 </div>
778 </div>
779 <div class="rfc-figure">
780 <span class="rfc-figure-id" id="rfc.figure.u.9">&#x00A0;</span>
781 <div class="rfc-preamble">
782 <div class="t-pair">
783 <p xml:lang="en" class="t-l-en">
784 The "postal" element contains one or more "street" elements,
785 followed by any combination of "city", "region" (state or province),
786 "code" (zipcode or postal code), and "country" elements, e.g.,
787 </p>
788 <p xml:lang="ja" class="t-l-ja">
789 "postal" $BMWAG$O<!$NNc$NMM$K!"(B1$B$D0J>e$N(B "street" $BMWAG(B, $B$=$l$KB3$/(B
790 "city", "region" ($B=#$dCOJ}(B), "code" ($BM9JXHV9f(B), "country"
791 $B3FMWAG$N<+M3$JAH9g$;$+$i@.$j$^$9!#(B
792 </p>
793 </div>
794 </div>
795 <pre class="rfc-artwork" xml:space="preserve">
796 &lt;postal&gt;
797 &lt;street&gt;660 York Street&lt;/street&gt;
798 &lt;street&gt;M/S 40&lt;/street&gt;
799 &lt;city&gt;San Francisco&lt;/city&gt; &lt;region&gt;CA&lt;/region&gt;
800 &lt;code&gt;94110&lt;/code&gt;
801 &lt;country&gt;US&lt;/country&gt;
802 &lt;/postal&gt;
803 </pre>
804 <div class="rfc-postamble">
805 <div class="t-pair">
806 <p xml:lang="en" class="t-l-en">
807 This flexibility is provided to allow for different national
808 formats for postal addresses.
809 Note however,
810 that although the order of the "city", "region", "code", and "country"
811 elements isn't specified,
812 at most one of each may be present.
813 Regardless,
814 these elements must not be re-ordered during processing by an XML
815 application
816 (e.g., display applications must preserve the ordering of the
817 information contained in these elements).
818 Finally,
819 the value of the "country" element should be a two-letter
820 code from ISO 3166.
821 </p>
822 <p xml:lang="ja" class="t-l-ja">
823 $B$3$N=@Fp$5$K$h$j!"0[$J$C$?9q2HM9JX=;=j7A<0$,;H$($^$9!#(B
824 $B$7$+$7!"(B "city", "region", "code", "country"
825 $B3FMWAG$N=g=x$O5,Dj$7$F$$$^$;$s$,!"$3$NFb$N$;$$$<$$(B1$B$D$O=P8=$9$k$+$b$7$l$J$$$3$H$KCm0U$7$F2<$5$$!#$H$K$+$/!"$3$l$i$NMWAG$O(B
826 XML $B1~MQ$N=hM}$N2aDx$G=g=x$rF~$lBX$($F$O$J$j$^$;$s!#(B
827 ($BNc$($P!"I=<(1~MQ$O$3$l$i$NMWAG$K4^$^$l$k>pJs$N=g=x$rJ]$?$J$1$l$P$J$j$^$;$s!#(B)
828 $B:G8e$K!"(B "country" $BMWAG$NCM$O(B ISO 3166 $B$N(B2$BJ8;zId9f$H$9$k$Y$-$G$9!#(B
829 </p>
830 </div>
831 </div>
832 </div>
833 <div class="rfc-figure">
834 <span class="rfc-figure-id" id="rfc.figure.u.10">&#x00A0;</span>
835 <div class="rfc-preamble">
836 <div class="t-pair">
837 <p xml:lang="en" class="t-l-en">
838 The "phone", "facsimile", "email", and "uri" elements are
839 simple, e.g.,
840 </p>
841 <p xml:lang="ja" class="t-l-ja">
842 "phone", "facsimile", "email", "uri" $B3FMWAG$O4JC1$G!"<!$NMM$J46$8$G$9!#(B
843 </p>
844 </div>
845 </div>
846 <pre class="rfc-artwork" xml:space="preserve">
847 &lt;phone&gt;+1 415 695 3975&lt;/phone&gt;
848 &lt;email&gt;mrose@not.invisible.net&lt;/email&gt;
849 &lt;uri&gt;http://invisible.net/&lt;/uri&gt;
850 </pre>
851 </div>
852 </div>
853 <div class="rfc-section" id="rfc.section.2.2.3">
854 <div class="t-pair t-heading" id="date">
855 <h3 xml:lang="en" class="t-l-en">2.2.3. The date Element</h3>
856 <h3 xml:lang="ja" class="t-l-ja">2.2.3.
857 date $BMWAG(B</h3>
858 </div>
859 <div class="rfc-figure">
860 <span class="rfc-figure-id" id="rfc.figure.u.11">&#x00A0;</span>
861 <div class="rfc-preamble">
862 <div class="t-pair">
863 <p xml:lang="en" class="t-l-en">
864 The "date" element identifies the publication date of the
865 document.
866 It consists of a month and a year, e.g.,
867 </p>
868 <p xml:lang="ja" class="t-l-ja">
869 "date" $BMWAG$OJ8=q$N=PHG$NF|IU$r<($7$^$9!#<!$N$h$&$K7n$HG/$+$i@.$j$^$9!#(B
870 </p>
871 </div>
872 </div>
873 <pre class="rfc-artwork" xml:space="preserve">
874 &lt;date month="February" year="1999" /&gt;
875 </pre>
876 <div class="rfc-postamble">
877 <div class="t-pair">
878 <p xml:lang="en" class="t-l-en">
879 The "date" element also has an optional day attribute.
880 </p>
881 <p xml:lang="ja" class="t-l-ja">
882 "date" $BMWAG$K$O>JN,2DG=$J(B day $BB0@-$b$"$j$^$9!#(B
883 </p>
884 </div>
885 </div>
886 </div>
887 </div>
888 <div class="rfc-section" id="rfc.section.2.2.4">
889 <div class="t-pair t-heading">
890 <h3 xml:lang="en" class="t-l-en">2.2.4. Meta Data Elements</h3>
891 <h3 xml:lang="ja" class="t-l-ja">2.2.4.
892 $B%a%?!&%G!<%?MWAG(B</h3>
893 </div>
894 <div class="rfc-t" id="rfc.section.2.2.4.p.1">
895 <div class="t-pair">
896 <p xml:lang="en" class="t-l-en">
897 The "front" element may contain meta data $B!=!=(B
898 the content of these elements does not appear in printed versions of
899 the document.
900 </p>
901 <p xml:lang="ja" class="t-l-ja">
902 "front" $BMWAG$O%a%?!&%G!<%?(B ($BFbMF$OJ8=q$N0u:~HG$K$O=P8=$7$J$$$b$N(B) $B$b4^$`$3$H$,=PMh$^$9!#(B
903 </p>
904 </div>
905 </div>
906 <div class="rfc-figure">
907 <span class="rfc-figure-id" id="rfc.figure.u.12">&#x00A0;</span>
908 <div class="rfc-preamble">
909 <div class="t-pair">
910 <p xml:lang="en" class="t-l-en">
911 A document has one or more optional "area",
912 "workgroup" and "keyword" elements, e.g.,
913 </p>
914 <p xml:lang="ja" class="t-l-ja">
915 $BJ8=q$O(B1$B$D0J>e$N>JN,2DG=$J(B "area", "workgroup", "keyword"
916 $B3FMWAG$r<!$NNc$NMM$K;}$A$^$9!#(B
917 </p>
918 </div>
919 </div>
920 <pre class="rfc-artwork" xml:space="preserve">
921 &lt;area&gt;General&lt;/area&gt;
922 &lt;workgroup&gt;RFC Beautification Working Group&lt;/workgroup&gt;
923 &lt;keyword&gt;RFC&lt;/keyword&gt;
924 &lt;keyword&gt;Request for Comments&lt;/keyword&gt;
925 &lt;keyword&gt;I-D&lt;/keyword&gt;
926 &lt;keyword&gt;Internet-Draft&lt;/keyword&gt;
927 &lt;keyword&gt;XML&lt;/keyword&gt;
928 &lt;keyword&gt;Extensible Markup Language&lt;/keyword&gt;
929 </pre>
930 <div class="rfc-postamble">
931 <div class="t-pair">
932 <p xml:lang="en" class="t-l-en">
933 The "area" elements identify a general category for the
934 document
935 (e.g., one of "Applications", "General", "Internet", "Management",
936 "Operations", "Routing", "Security", "Transport", or "User"),
937 while the "workgroup" elements identify the IETF working groups that
938 produced the document,
939 and the "keyword" elements identify useful search terms.
940 </p>
941 <p xml:lang="ja" class="t-l-ja">
942 "area" $BMWAG$OJ8=q$N0lHLJ,N`(B ("Applications" ($B1~MQ(B),
943 "General" ($B0lHL(B), "Internet", "Management" ($B7P1D(B),
944 "Operations" ($B:n6H(B), "Routing" ($B7PO)(B), "Security" ($BJ]0B(B),
945 "Transport" ($BM"Aw(B), "User" ($BMxMQ<T(B)) $B$r<($7!"(B
946 "workgroup" $BMWAG$OJ8=q$r=P$7$?(B IETF $B:n6HIt2q$r<($7!"(B
947 "keyword" $BMWAG$OM-MQ$J8!:w8l$r<($7$^$9!#(B
948 </p>
949 </div>
950 </div>
951 </div>
952 </div>
953 <div class="rfc-section" id="rfc.section.2.2.5">
954 <div class="t-pair t-heading">
955 <h3 xml:lang="en" class="t-l-en">2.2.5. The abstract Element</h3>
956 <h3 xml:lang="ja" class="t-l-ja">2.2.5.
957 abstract $BMWAG(B</h3>
958 </div>
959 <div class="rfc-figure">
960 <span class="rfc-figure-id" id="rfc.figure.u.13">&#x00A0;</span>
961 <div class="rfc-preamble">
962 <div class="t-pair">
963 <p xml:lang="en" class="t-l-en">
964 A document may have an "abstract" element,
965 which contains one or more <span class="rfc-xref">
966 <a href="#t" title="">"t" elements</a>
967 </span>.
968 In general,
969 only a single "t" element is present,
970 e.g.,
971 </p>
972 <p xml:lang="ja" class="t-l-ja">
973 $BJ8=q$K$O(B "abstract" $BMWAG$r;H$&$3$H$,=PMh$F!"(B
974 $B$=$l$K$O(B1$B$D0J>e$N(B <a href="#t" title="">"t" $BMWAG(B</a>$B$,4^$a$i$l$^$9!#DL>o!"<!$NNc$NMM$K!"(B "t" $BMWAG$r(B1$B$D$@$1;H$$$^$9!#(B
975 </p>
976 </div>
977 </div>
978
979 <div class="t-pair">
980 <p xml:lang="en" class="t-l-en">
981 <pre class="rfc-artwork" xml:space="preserve">
982 &lt;abstract&gt;
983 &lt;t&gt;This memo presents a technique for using XML
984 (Extensible Markup Language) as a source format
985 for documents in the Internet-Drafts (I-Ds) and
986 Request for Comments (RFC) series.&lt;/t&gt;
987 &lt;/abstract&gt;
988 </pre>
989 </p>
990 <p xml:lang="ja" class="t-l-ja">
991 <pre class="rfc-artwork" xml:space="preserve">
992 &lt;abstract&gt;
993 &lt;t&gt;$B$3$N%a%b$O!"(B XML ($B3HD%%^!<%/IU$18@8l(B) $B$r(B
994 Internet-Draft (I-D) $B$d(B Request for Comments (RFC)
995 $B7ONs$NJ8=q$N867A<0$H$7$F;HMQ$9$k<jK!$r@bL@$7$^$9!#(B&lt;/t&gt;
996 &lt;/abstract&gt;
997 </pre>
998 </p>
999 </div>
1000
1001 </div>
1002 </div>
1003 <div class="rfc-section" id="rfc.section.2.2.6">
1004 <div class="t-pair t-heading">
1005 <h3 xml:lang="en" class="t-l-en">2.2.6. The note Element</h3>
1006 <h3 xml:lang="ja" class="t-l-ja">2.2.6.
1007 note $BMWAG(B</h3>
1008 </div>
1009 <div class="rfc-figure">
1010 <span class="rfc-figure-id" id="rfc.figure.u.14">&#x00A0;</span>
1011 <div class="rfc-preamble">
1012 <div class="t-pair">
1013 <p xml:lang="en" class="t-l-en">
1014 A document may have one or more "note" elements,
1015 each of which contains one or more <span class="rfc-xref">
1016 <a href="#t" title="">"t" elements</a>
1017 </span>.
1018 There is a mandatory "title" attribute.
1019 In general,
1020 the "note" element contains text from the IESG,
1021 e.g.,
1022 </p>
1023 <p xml:lang="ja" class="t-l-ja">
1024 $BJ8=q$K$O(B1$B$D0J>e$N(B "note" $BMWAG$r;H$&$3$H$,=PMh$F!"(B
1025 $B$=$l$>$l(B1$B$D0J>e$N(B <a href="#t" title="">"t" $BMWAG(B</a>$B$,4^$a$i$l$^$9!#I,?\$N(B
1026 "title" $BB0@-$,$"$j$^$9!#DL>o!"(B "note" $BMWAG$O(B IESG
1027 $B$+$i$NJ8$r<!$NNc$NMM$KF~$l$^$9!#(B
1028 </p>
1029 </div>
1030 </div>
1031
1032 <div class="t-pair">
1033 <p xml:lang="en" class="t-l-en">
1034 <pre class="rfc-artwork" xml:space="preserve">
1035 &lt;note title="IESG Note"&gt;
1036 &lt;t&gt;The IESG has something to say.&lt;/t&gt;
1037 &lt;/note&gt;
1038 </pre>
1039 </p>
1040 <p xml:lang="ja" class="t-l-ja">
1041 <pre class="rfc-artwork" xml:space="preserve">
1042 &lt;note title="IESG $BCm5-(B"&gt;
1043 &lt;t&gt;IESG $B$OFC$K8@$&$3$H$O$"$j$^$;$s!#(B&lt;/t&gt;
1044 &lt;/note&gt;
1045 </pre>
1046 </p>
1047 </div>
1048
1049 </div>
1050 </div>
1051 <div class="rfc-section" id="rfc.section.2.2.7">
1052 <div class="t-pair t-heading">
1053 <h3 xml:lang="en" class="t-l-en">2.2.7. Status, Copyright Notice, Table of Contents</h3>
1054 <h3 xml:lang="ja" class="t-l-ja">2.2.7.
1055 $B0LCVIU$1(B, $BCx:n8"I=<((B, $BL\<!(B</h3>
1056 </div>
1057 <div class="rfc-t" id="rfc.section.2.2.7.p.1">
1058 <div class="t-pair">
1059 <p xml:lang="en" class="t-l-en">
1060 Note that text relating to the memo's status, copyright notice, or
1061 table of contents is not included in the document's markup $B!=!=(B this is
1062 automatically inserted by an XML application when it produces either
1063 a text or HTML version of the document.
1064 </p>
1065 <p xml:lang="ja" class="t-l-ja">
1066 $B%a%b$N0LCVIU$1$r@bL@$9$kJ8>O(B, $BCx:n8"I=<((B,
1067 $BL\<!$OJ8=q$N%^!<%/IU$1$K$O4^$a$^$;$s!#$3$l$O(B XML
1068 $B1~MQ$,J8=q$N(B text $BHG$d(B HTML $BHG$r@8@.$9$k;~$K<+F0E*$KA^F~$5$l$^$9!#(B
1069 </p>
1070 </div>
1071 </div>
1072 <div class="rfc-section" id="rfc.section.2.2.7.1">
1073 <div class="t-pair t-heading" id="ipr">
1074 <h4 xml:lang="en" class="t-l-en">2.2.7.1. Conformance with RFC 2026</h4>
1075 <h4 xml:lang="ja" class="t-l-ja">2.2.7.1.
1076 RFC 2026 $B$X$NE,9g@-(B</h4>
1077 </div>
1078 <div class="rfc-t" id="rfc.section.2.2.7.1.p.1">
1079 <div class="t-pair">
1080 <p xml:lang="en" class="t-l-en">
1081 If an Internet-Draft is being produced,
1082 then the "ipr" attribute should be present in the "&lt;rfc&gt;"
1083 tag at the beginning of the file.
1084 The value of the attribute should be one of:
1085 </p>
1086 <p xml:lang="ja" class="t-l-ja">
1087 Internet-Draft $B$,@8@.$5$l$k>l9g$K!"(B "ipr" $BB0@-$,%U%!%$%k$N$O$8$a$N(B
1088 "&lt;rfc&gt;"$B%?%0$K8=$l$k$Y$-$G$9!#$3$NB0@-$NCM$O<!$N$$$:$l$+$G$"$k$Y$-$G$9!#(B
1089 </p>
1090 </div>
1091
1092 <dl class="rfc-list-hanging">
1093 <dt>full2026:</dt>
1094 <dd>
1095 <div class="t-pair">
1096 <p xml:lang="en" class="t-l-en">
1097 indicating that the document is in full conformance with all
1098 the provisions of Section 10 of RFC 2026;
1099 </p>
1100 <p xml:lang="ja" class="t-l-ja">
1101 $BJ8=q$,(B <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">RFC 2026</a>
1102 $B$N(B<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">$BBh(B10$B>O(B</a>
1103 $B$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r<($7$^$9(B
1104 </p>
1105 </div>
1106 </dd>
1107 <dt>noDerivativeWorks2026:</dt>
1108 <dd>
1109 <div class="t-pair">
1110 <p xml:lang="en" class="t-l-en">
1111 indicating that the document is in full
1112 conformance with all the provisions of Section 10 of RFC 2026 except that the
1113 right to produce derivative works is not granted; or,
1114 </p>
1115 <p xml:lang="ja" class="t-l-ja">
1116 $BJ8=q$,!"GI@8E*:n6H$N@8@.$,G'$a$i$l$F$$$J$$$3$H$r=|$$$F!"(B
1117 <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">RFC 2026</a>
1118 $B$N(B<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">$BBh(B10$B>O(B</a>
1119 $B$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r<($7$^$9(B
1120 </p>
1121 </div>
1122 </dd>
1123 <dt>none:</dt>
1124 <dd>
1125 <div class="t-pair">
1126 <p xml:lang="en" class="t-l-en">
1127 indicating that the document is NOT offered in accordance with
1128 Section 10 of RFC 2026, and the author does not provide the IETF with any rights
1129 other than to publish as an Internet-Draft.
1130 </p>
1131 <p xml:lang="ja" class="t-l-ja">
1132 $BJ8=q$,(B
1133 <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">RFC 2026</a>
1134 $B$N(B<a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="RFC 2026">$BBh(B10$B>O(B</a>
1135 $B$K=>$C$F(B<strong>$B$*$i$:(B</strong>$B!"Cx<T$O(B IETF $B$K(B Internet-Draft
1136 $B$H$7$FH/9T$9$k0J30$N$$$+$J$k8"Mx$r$bDs6!$7$J$$$3$H$r<($7$^$9(B
1137 </p>
1138 </div>
1139 </dd>
1140 </dl>
1141
1142 <div class="t-pair">
1143 <p xml:lang="en" class="t-l-en">
1144 In the latter case,
1145 a copyright notice will not be automatically inserted during
1146 processing by an XML application.
1147 </p>
1148 <p xml:lang="ja" class="t-l-ja">
1149 $B8e<T$N>l9g$G$O!"Cx:n8"I=<($O(B XML $B1~MQ$K$h$j<+F0E*$K$OA^F~$5$l$^$;$s!#(B
1150 <ins class="t-note t-l-ja" xml:lang="ja">
1151 (<span class="t-note-title">$BLuCm(B:</span>$B8e<T(B (the latter case) $B$H$O:G8e$N>l9g$N$_(B?
1152 rfc2629.xslt $B$G$O$I$N>l9g$G$bA^F~$5$l$k$h$&$G$9$,(B...)
1153 </ins>
1154 </p>
1155 </div>
1156 </div>
1157 <div class="rfc-t" id="rfc.section.2.2.7.1.p.2">
1158 <div class="t-pair">
1159 <p xml:lang="en" class="t-l-en">
1160 Consult <span class="rfc-xref">
1161 <a href="#refs.RFC2026" title="The Internet Standards Process $B!=!=(B Revision 3">[3]</a>
1162 </span> for further details.
1163 </p>
1164 <p xml:lang="ja" class="t-l-ja">
1165 $B>\$7$/$O(B <a href="#refs.RFC2026" title="Internet $BI8=`2=2aDx(B $B!=!=(B $B2~D{(B3$BHG(B">[3]</a> $B$rD4$Y$F2<$5$$!#(B
1166 </p>
1167 </div>
1168 </div>
1169 <div class="rfc-figure">
1170 <span class="rfc-figure-id" id="rfc.figure.u.15">&#x00A0;</span>
1171 <div class="rfc-preamble">
1172 <div class="t-pair">
1173 <p xml:lang="en" class="t-l-en">
1174 Finally,
1175 if the Internet-Draft is being submitted to an automated process,
1176 then the "docName" attribute should be present in the "&lt;rfc&gt;"
1177 tag at the beginning of the file.
1178 The value of this attribute contains the document (not file) name
1179 associated with this Internet-Draft, e.g.,
1180 </p>
1181 <p xml:lang="ja" class="t-l-ja">
1182 $B:G8e$K!"(B Internet-Draft $B$,<+F0=hM}$K2s$5$l$?;~$O!"(B "docName"
1183 $BB0@-$,%U%!%$%k$N$O$8$a$N(B "&lt;rfc&gt;" $B%?%0Cf$K=P8=$9$k$Y$-$G$9!#(B
1184 $B$3$NB0@-$NCM$O(B Internet-Draft $B$K$D$1$i$l$?J8=q(B ($B%U%!%$%k$G$J$7$K(B)
1185 $B$NL>A0$G!"<!$NMM$K$J$j$^$9!#(B
1186 </p>
1187 </div>
1188 </div>
1189 <pre class="rfc-artwork" xml:space="preserve">
1190 &lt;rfc ipr="full" docName="draft-mrose-writing-rfcs-01"&gt;
1191 ...
1192 &lt;/rfc&gt;
1193 </pre>
1194
1195 <div class="rfc-postamble"/>
1196 </div>
1197 </div>
1198 </div>
1199 <div class="rfc-section" id="rfc.section.2.2.8">
1200 <div class="t-pair t-heading">
1201 <h3 xml:lang="en" class="t-l-en">2.2.8. Everything in the Front</h3>
1202 <h3 xml:lang="ja" class="t-l-ja">2.2.8.
1203 Front $BA4BN(B</h3>
1204 </div>
1205 <div class="rfc-figure">
1206 <span class="rfc-figure-id" id="rfc.figure.u.16">&#x00A0;</span>
1207 <div class="rfc-preamble">
1208 <div class="t-pair">
1209 <p xml:lang="en" class="t-l-en">
1210 So,
1211 putting it all together, we have, e.g.,
1212 </p>
1213 <p xml:lang="ja" class="t-l-ja">
1214 $B0J>e$r$^$H$a$k$H<!$NMM$K$J$j$^$9!#(B
1215 </p>
1216 </div>
1217 </div>
1218
1219 <div class="t-pair">
1220 <p xml:lang="en" class="t-l-en">
1221 <pre class="rfc-artwork" xml:space="preserve">
1222 &lt;front&gt;
1223 &lt;title&gt;Writing I-Ds and RFCs using XML&lt;/title&gt;
1224
1225 &lt;author initials="M.T." surname="Rose"
1226 fullname="Marshall T. Rose"&gt;
1227 &lt;organization&gt;Invisible Worlds, Inc.&lt;/organization&gt;
1228
1229 &lt;address&gt;
1230 &lt;postal&gt;
1231 &lt;street&gt;660 York Street&lt;/street&gt;
1232 &lt;street&gt;M/S 40&lt;/street&gt;
1233 &lt;city&gt;San Francisco&lt;/city&gt; &lt;region&gt;CA&lt;/region&gt;
1234 &lt;code&gt;94110&lt;/code&gt;
1235 &lt;country&gt;US&lt;/country&gt;
1236 &lt;/postal&gt;
1237
1238 &lt;phone&gt;+1 415 695 3975&lt;/phone&gt;
1239 &lt;email&gt;mrose@not.invisible.net&lt;/email&gt;
1240 &lt;uri&gt;http://invisible.net/&lt;/uri&gt;
1241 &lt;/address&gt;
1242 &lt;/author&gt;
1243
1244 &lt;date month="February" year="1999" /&gt;
1245
1246 &lt;area&gt;General&lt;/area&gt;
1247 &lt;workgroup&gt;RFC Beautification Working Group&lt;/workgroup&gt;
1248 &lt;keyword&gt;RFC&lt;/keyword&gt;
1249 &lt;keyword&gt;Request for Comments&lt;/keyword&gt;
1250 &lt;keyword&gt;I-D&lt;/keyword&gt;
1251 &lt;keyword&gt;Internet-Draft&lt;/keyword&gt;
1252 &lt;keyword&gt;XML&lt;/keyword&gt;
1253 &lt;keyword&gt;Extensible Markup Language&lt;/keyword&gt;
1254 &lt;abstract&gt;
1255 &lt;t&gt;This memo presents a technique for using XML
1256 (Extensible Markup Language) as a source format
1257 for documents in the Internet-Drafts (I-Ds) and
1258 Request for Comments (RFC) series.&lt;/t&gt;
1259 &lt;/abstract&gt;
1260 &lt;/front&gt;
1261 </pre>
1262 </p>
1263 <p xml:lang="ja" class="t-l-ja">
1264 <pre class="rfc-artwork" xml:space="preserve">
1265 &lt;front&gt;
1266 &lt;title&gt;XML $B$r;H$C$F(B I-D $B$d(B RFC $B$r=q$/(B&lt;/title&gt;
1267
1268 &lt;author initials="M.T." surname="Rose"
1269 fullname="Marshall T. Rose"&gt;
1270 &lt;organization&gt;Invisible Worlds, Inc.&lt;/organization&gt;
1271
1272 &lt;address&gt;
1273 &lt;postal&gt;
1274 &lt;street&gt;660 York Street&lt;/street&gt;
1275 &lt;street&gt;M/S 40&lt;/street&gt;
1276 &lt;city&gt;San Francisco&lt;/city&gt; &lt;region&gt;CA&lt;/region&gt;
1277 &lt;code&gt;94110&lt;/code&gt;
1278 &lt;country&gt;US&lt;/country&gt;
1279 &lt;/postal&gt;
1280
1281 &lt;phone&gt;+1 415 695 3975&lt;/phone&gt;
1282 &lt;email&gt;mrose@not.invisible.net&lt;/email&gt;
1283 &lt;uri&gt;http://invisible.net/&lt;/uri&gt;
1284 &lt;/address&gt;
1285 &lt;/author&gt;
1286
1287 &lt;date month="February" year="1999" /&gt;
1288
1289 &lt;area&gt;General&lt;/area&gt;
1290 &lt;workgroup&gt;RFC $BH~2=:n6HIt2q(B&lt;/workgroup&gt;
1291 &lt;keyword&gt;RFC&lt;/keyword&gt;
1292 &lt;keyword&gt;Request for Comments&lt;/keyword&gt;
1293 &lt;keyword&gt;I-D&lt;/keyword&gt;
1294 &lt;keyword&gt;Internet-Draft&lt;/keyword&gt;
1295 &lt;keyword&gt;XML&lt;/keyword&gt;
1296 &lt;keyword&gt;$B3HD%%^!<%/IU$18@8l(B&lt;/keyword&gt;
1297 &lt;abstract&gt;
1298 &lt;t&gt;$B$3$N%a%b$O!"(B XML ($B3HD%%^!<%/IU$18@8l(B) $B$r(B
1299 Internet-Draft (I-D) $B$d(B Request for Comments (RFC)
1300 $B7ONs$NJ8=q$N867A<0$H$7$F;HMQ$9$k<jK!$r@bL@$7$^$9!#(B&lt;/t&gt;
1301 &lt;/abstract&gt;
1302 &lt;/front&gt;
1303 </pre>
1304 </p>
1305 </div>
1306
1307 </div>
1308 </div>
1309 </div>
1310 <div class="rfc-section" id="rfc.section.2.3">
1311 <div>
1312 <h2>2.3. The Middle</h2>
1313 </div>
1314 <div class="rfc-figure">
1315 <span class="rfc-figure-id" id="rfc.figure.u.17">&#x00A0;</span>
1316 <div class="rfc-preamble">
1317 <div class="t-pair">
1318 <p xml:lang="en" class="t-l-en">
1319 The "middle" element contains all the sections of the document
1320 except for the bibliography and appendices:
1321 </p>
1322 <p xml:lang="ja" class="t-l-ja">
1323 "middle" $BMWAG$O;29MJ88%$HImB0=q$r=|$/J8=q$NA4$F$N@a$+$i@.$j$^$9!#(B
1324 </p>
1325 </div>
1326 </div>
1327 <pre class="rfc-artwork" xml:space="preserve">
1328 ...
1329 &lt;/front&gt;
1330 &lt;middle&gt;
1331 &lt;section ...&gt;
1332 &lt;section ...&gt;
1333 &lt;section ...&gt;
1334 &lt;/middle&gt;
1335 &lt;back&gt;
1336 ...
1337 </pre>
1338 <div class="rfc-postamble">
1339 <div class="t-pair">
1340 <p xml:lang="en" class="t-l-en">
1341 The "middle" element consists of one or more "section"
1342 elements.
1343 </p>
1344 <p xml:lang="ja" class="t-l-ja">
1345 "middle" $BMWAG$O(B1$B$D0J>e$N(B "section" $BMWAG$+$i@.$j$^$9!#(B
1346 </p>
1347 </div>
1348 </div>
1349 </div>
1350 <div class="rfc-section" id="rfc.section.2.3.1">
1351 <div class="t-pair t-heading" id="section">
1352 <h3 xml:lang="en" class="t-l-en">2.3.1. The section Element</h3>
1353 <h3 xml:lang="ja" class="t-l-ja">2.3.1.
1354 section $BMWAG(B</h3>
1355 </div>
1356 <div class="rfc-figure">
1357 <span class="rfc-figure-id" id="rfc.figure.u.18">&#x00A0;</span>
1358 <div class="rfc-preamble">
1359 <div class="t-pair">
1360 <p xml:lang="en" class="t-l-en">
1361 Each "section" element contains a section of the document.
1362 There is a mandatory attribute,
1363 "title",
1364 that identifies the title of the section.
1365 There is also an optional attribute,
1366 "anchor",
1367 that is used for cross-referencing with
1368 <span class="rfc-xref">
1369 <a href="#xref" title="">the "xref" element</a>
1370 </span>,
1371 e.g.,
1372 </p>
1373 <p xml:lang="ja" class="t-l-ja">
1374 $B3F(B "section" $BMWAG$OJ8=q$N@a$+$i@.$j$^$9!#I,?\$NB0@-(B "title"
1375 $B$O@a$NBj$rI=$7$^$9!#>JN,2DG=$NB0@-(B "anchor" $B$O(B
1376 <a href="#xref" title="">"xref" $BMWAG(B</a>$B$K$h$k8r:9;2>H$K;H$$$^$9!#(B
1377 $B<!$NNc$r8fMw2<$5$$!#(B
1378 </p>
1379 </div>
1380 </div>
1381 <pre class="rfc-artwork" xml:space="preserve">
1382 &lt;section anchor="intro" title="Introduction"&gt;
1383 ...
1384 &lt;/section&gt;
1385 </pre>
1386 </div>
1387 <div class="rfc-figure">
1388 <span class="rfc-figure-id" id="rfc.figure.u.19">&#x00A0;</span>
1389 <div class="rfc-preamble">
1390 <div class="t-pair">
1391 <p xml:lang="en" class="t-l-en">
1392 The "section" element is recursive $B!=!=(B
1393 each contains any number and combination of "t", "figure", and "section"
1394 elements, e.g.,
1395 </p>
1396 <p xml:lang="ja" class="t-l-ja">
1397 "section" $BMWAG$O:F5"E*$G!"3F!9G$0U$N?t!&AH9g$;$G(B "t",
1398 "figure", "section" $B3FMWAG$r<!$NNc$NG!$/;H$$$^$9!#(B
1399 </p>
1400 </div>
1401 </div>
1402 <pre class="rfc-artwork" xml:space="preserve">
1403 &lt;section title="The Middle"&gt;
1404 ...
1405 &lt;section title="The section Element"&gt;
1406 ...
1407 &lt;section title="The t Element"&gt;...&lt;/section&gt;
1408 &lt;section title="The list Element"&gt;...&lt;/section&gt;
1409 &lt;section title="The figure Element"&gt;...&lt;/section&gt;
1410 &lt;section title="The xref Element"&gt;...&lt;/section&gt;
1411 &lt;section title="The eref Element"&gt;...&lt;/section&gt;
1412 &lt;section title="The iref Element"&gt;...&lt;/section&gt;
1413 &lt;/section&gt;
1414 &lt;/section&gt;
1415 </pre>
1416 </div>
1417 <div class="rfc-section" id="rfc.section.2.3.1.1">
1418 <div class="t-pair t-heading" id="t">
1419 <h4 xml:lang="en" class="t-l-en">2.3.1.1. The t Element</h4>
1420 <h4 xml:lang="ja" class="t-l-ja">2.3.1.1.
1421 t $BMWAG(B</h4>
1422 </div>
1423 <div class="rfc-t" id="rfc.section.2.3.1.1.p.1">
1424 <div class="t-pair">
1425 <p xml:lang="en" class="t-l-en">
1426 The "t" element contains any number and combination of
1427 paragraphs, lists, and figures.
1428 If a cross-reference is needed to a section, figure, or reference,
1429 <span class="rfc-xref">
1430 <a href="#xref" title="">the "xref" element</a>
1431 </span> is used;
1432 similarly,
1433 if an external-reference is needed,
1434 <span class="rfc-xref">
1435 <a href="#eref" title="">the "eref" element</a>
1436 </span> is used.
1437 Indexing of text is provided by the
1438 <span class="rfc-xref">
1439 <a href="#iref" title="">the "iref" element</a>
1440 </span>.
1441 </p>
1442 <p xml:lang="ja" class="t-l-ja">
1443 "t" $BMWAG$OG$0U$N?t!&AH9g$;$NCJMn!&0lMw!&?^$+$i@.$j$^$9!#@a!&?^!&;29MJ88%$X$N8r:9;2>H$,I,MW$J$i!"(B <a href="#xref" title="">"xref" $BMWAG(B</a>
1444 $B$r;H$$$^$9!#F1MM$K30It;2>H$,I,MW$J$i!"(B <a href="#eref" title="">"eref"
1445 $BMWAG(B</a>$B$r;H$$$^$9!#J8>O$N:w0zIU$1$K$O(B <a href="#iref" title="">"iref"
1446 $BMWAG(B</a>$B$r;H$$$^$9!#(B
1447 </p>
1448 </div>
1449 </div>
1450 </div>
1451 <div class="rfc-section" id="rfc.section.2.3.1.2">
1452 <div class="t-pair t-heading">
1453 <h4 xml:lang="en" class="t-l-en">2.3.1.2. The list Element</h4>
1454 <h4 xml:lang="ja" class="t-l-ja">2.3.1.2.
1455 list $BMWAG(B</h4>
1456 </div>
1457 <div class="rfc-figure">
1458 <span class="rfc-figure-id" id="rfc.figure.u.20">&#x00A0;</span>
1459 <div class="rfc-preamble">
1460 <div class="t-pair">
1461 <p xml:lang="en" class="t-l-en">
1462 The "list" element contains one or more items.
1463 Each item is a "t" element,
1464 allowing for recursion, e.g.,
1465 </p>
1466 <p xml:lang="ja" class="t-l-ja">
1467 "list" $BMWAG$O(B1$B$D0J>e$N9`L\$+$i@.$j$^$9!#3F9`L\$O(B
1468 "t" $BMWAG$G!"7+$jJV$72DG=$G$9!#Nc$r8fMw$"$l(B:
1469 </p>
1470 </div>
1471 </div>
1472
1473 <div class="t-pair">
1474 <p xml:lang="en" class="t-l-en">
1475 <pre class="rfc-artwork" xml:space="preserve">
1476 &lt;list style="numbers"&gt;
1477 &lt;t&gt;The first item.&lt;/t&gt;
1478 &lt;t&gt;The second item, which contains two bulleted sub-items:
1479 &lt;list style="symbols"&gt;
1480 &lt;t&gt;The first sub-item.&lt;/t&gt;
1481 &lt;t&gt;The second sub-item.&lt;/t&gt;
1482 &lt;/list&gt;
1483 &lt;/t&gt;
1484 &lt;/list&gt;
1485 </pre>
1486 </p>
1487 <p xml:lang="ja" class="t-l-ja">
1488 <pre class="rfc-artwork" xml:space="preserve">
1489 &lt;list style="numbers"&gt;
1490 &lt;t&gt;$B:G=i$N9`L\!#(B&lt;/t&gt;
1491 &lt;t&gt;2$B$D$N>.9`L\$,$"$kFsHVL\$N9`L\(B
1492 &lt;list style="symbols"&gt;
1493 &lt;t&gt;$B:G=i$N>.9`L\(B&lt;/t&gt;
1494 &lt;t&gt;$BFsHVL\$N>.9`L\(B&lt;/t&gt;
1495 &lt;/list&gt;
1496 &lt;/t&gt;
1497 &lt;/list&gt;
1498 </pre>
1499 </p>
1500 </div>
1501
1502 <div class="rfc-postamble">
1503 <div class="t-pair">
1504 <p xml:lang="en" class="t-l-en">
1505 The "list" element has an optional attribute,
1506 "style",
1507 having the value "numbers" (for numeric lists),
1508 "symbols" (for bulleted lists),
1509 "hanging" (for hanging lists),
1510 or,
1511 "empty" (for indented text).
1512 If a "list" element is nested,
1513 the default value is taken from its closest parent;
1514 otherwise,
1515 the default value is "empty".
1516
1517 </p>
1518 <p xml:lang="ja" class="t-l-ja">
1519 "list" $BMWAG$O>JN,2DG=$J(B "style" $BB0@-$,$"$C$F!"(B "numbers"
1520 ($BHV9f$D$-0lMw(B), "symbols" ($B5-9f$D$-0lMw(B), "hanging" ($B$V$i2<$,$j0lMw(B),
1521 "empty" ($B;z2<$2J8(B) $B$N$$$:$l$+$NCM$r<h$k$3$H$,=PMh$^$9!#(B
1522 "list" $BMWAG$,F~$l;R$K$J$C$F$$$k;~!"4{DjCM$O0lHV6a$$?F$+$i<h$i$l$^$9!#$=$&$G$J$$;~$O!"4{DjCM$O(B "empty" $B$G$9!#(B
1523 </p>
1524 </div>
1525 </div>
1526 </div>
1527 <div class="rfc-figure">
1528 <span class="rfc-figure-id" id="rfc.figure.u.21">&#x00A0;</span>
1529 <div class="rfc-preamble">
1530 <div class="t-pair">
1531 <p xml:lang="en" class="t-l-en">
1532 When nested within a "hanging list" element,
1533 the "t" element has an optional attribute,
1534 "hangText" that specifies the text to be inserted, e.g.,
1535 </p>
1536 <p xml:lang="ja" class="t-l-ja">
1537 $B!V$V$i2<$,$j0lMw!W(B $BMWAGCf$GF~$l;R$K$J$C$F$$$k;~!"(B
1538 "t" $BMWAG$O>JN,2DG=$JB0@-(B "hangText" $B$r;}$A!"A^F~$5$l$kJ8;zNs$r;XDj$7$^$9!#<!$NNc$r;2>H$7$F2<$5$$!#(B
1539 </p>
1540 </div>
1541 </div>
1542
1543 <div class="t-pair">
1544 <p xml:lang="en" class="t-l-en">
1545 <pre class="rfc-artwork" xml:space="preserve">
1546 &lt;list style="hanging"&gt;
1547 &lt;t hangText="full2026:"&gt;indicating that the document is in
1548 full conformance with all the provisions of Section 10 of
1549 RFC 2026;&lt;/t&gt;
1550
1551 &lt;t hangText="noDerivativeWorks2026:"&gt;indicating that the
1552 document is in full conformance with all the provisions of
1553 Section 10 of RFC 2026 except that the right to produce
1554 derivative works is not granted; or,&lt;/t&gt;
1555
1556 &lt;t hangText="none:"&gt;indicating that the document is NOT
1557 offered in accordance with Section 10 of RFC 2026, and
1558 the author does not provide the IETF with any rights other
1559 than to publish as an Internet-Draft.&lt;/t&gt;
1560 &lt;/list&gt;
1561 </pre>
1562 </p>
1563 <p xml:lang="ja" class="t-l-ja">
1564 <pre class="rfc-artwork" xml:space="preserve">
1565 &lt;list style="hanging"&gt;
1566 &lt;t hangText="full2026:"&gt;$BJ8=q$,(B RFC 2026
1567 $B$NBh(B10$B>O$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r<($7$^$9(B&lt;/t&gt;
1568
1569 &lt;t hangText="noDerivativeWorks2026:"&gt;
1570 $BJ8=q$,!"GI@8E*:n6H$N@8@.$,G'$a$i$l$F$$$J$$$3$H$r=|$$$F!"(B
1571 RFC 2026 $B$NBh(B10$B>O$NA4$F$NMW7o$K40A4$KE,9g$9$k$3$H$r(B
1572 $B<($7$^$9(B&lt;/t&gt;
1573
1574 &lt;t hangText="none:"&gt;$BJ8=q$,(B RFC 2026 $B$NBh(B10$B>O$K=>$C$F(B
1575 *$B$*$i$:(B*$B!"Cx<T$O(B IETF $B$K(B Internet-Draft
1576 $B$H$7$FH/9T$9$k0J30$N$$$+$J$k8"Mx$r$bDs6!$7$J$$$3$H$r(B
1577 $B<($7$^$9(B&lt;/t&gt;
1578 &lt;/list&gt;
1579 </pre>
1580 </p>
1581 </div>
1582
1583 </div>
1584 </div>
1585 <div class="rfc-section" id="rfc.section.2.3.1.3">
1586 <div class="t-pair t-heading" id="figure">
1587 <h4 xml:lang="en" class="t-l-en">2.3.1.3. The figure Element</h4>
1588 <h4 xml:lang="ja" class="t-l-ja">2.3.1.3.
1589 figure $BMWAG(B</h4>
1590 </div>
1591 <div class="rfc-t" id="rfc.section.2.3.1.3.p.1">
1592 <div class="t-pair">
1593 <p xml:lang="en" class="t-l-en">
1594 The "figure" element groups an optional "preamble" element,
1595 an "artwork" element,
1596 and an optional "postamble" element together.
1597 The "figure" element also has an optional "anchor" attribute that is
1598 used for cross-referencing with
1599 <span class="rfc-xref">
1600 <a href="#xref" title="">the "xref" element</a>
1601 </span>.
1602 There is also an optional "title" attribute that identifies the title
1603 of the figure.
1604
1605 </p>
1606 <p xml:lang="ja" class="t-l-ja">
1607 "figure" $BMWAG$O>JN,2DG=$J(B "preamble" $BMWAG(B,
1608 "artwork" $BMWAG(B, $B>JN,2DG=$J(B "postable" $BMWAG$r$R$H$^$H$a$K$7$^$9!#(B
1609 "figure" $BMWAG$O>JN,2DG=$J(B "anchor" $BB0@-$b;}$C$F$$$F!"(B
1610 <a href="#xref" title="">"xref" $BMWAG(B</a>$B$K$h$k8r:9;2>H$K;H$&$3$H$,=PMh$^$9!#(B
1611 $B>JN,2DG=$J(B "title" $BB0@-$H$$$&$N$b$"$C$F!"?^$NBj$r<($7$^$9!#(B
1612 </p>
1613 </div>
1614 </div>
1615 <div class="rfc-t" id="rfc.section.2.3.1.3.p.2">
1616 <div class="t-pair">
1617 <p xml:lang="en" class="t-l-en">
1618 The "preamble" and "postamble" elements,
1619 if present,
1620 are simply text.
1621 If a cross-reference is needed to a section, figure, or reference,
1622 <span class="rfc-xref">
1623 <a href="#xref" title="">the "xref" element</a>
1624 </span> is used;
1625 similarly,
1626 if an external-reference is needed,
1627 <span class="rfc-xref">
1628 <a href="#eref" title="">the "eref" element</a>
1629 </span> is used.
1630 Indexing of text is provided by the
1631 <span class="rfc-xref">
1632 <a href="#iref" title="">the "iref" element</a>
1633 </span>.
1634 </p>
1635 <p xml:lang="ja" class="t-l-ja">
1636 "preamble" $B!&(B "postamble" $BN>MWAG$O!"B8:_$9$k>l9g!"C1=c$JJ8;zNs$G$9!#(B
1637 $B@a!&?^!&;29MJ88%$X$N8r:9;2>H$,I,MW$J>l9g$O!"(B
1638 <a href="#xref" title="">"xref"
1639 $BMWAG(B</a>$B$r;H$$$^$9!#F1MM$K!"30It;2>H$,I,MW$J$i!"(B
1640 <a href="#eref" title="">"eref" $BMWAG(B</a>$B$r;H$$$^$9!#J8>O$N:w0zIU$1$K$O(B
1641 <a href="#iref" title="">"iref" $BMWAG(B</a>$B$r;H$$$^$9!#(B
1642 </p>
1643 </div>
1644 </div>
1645 <div class="rfc-t" id="rfc.section.2.3.1.3.p.3">
1646 <div class="t-pair">
1647 <p xml:lang="en" class="t-l-en">
1648 The "artwork" element,
1649 which must be present,
1650 contains "ASCII artwork".
1651 Unlike text contained in the "t", "preamble", or "postamble" elements,
1652 both horizontal and vertical whitespace is significant in the "artwork"
1653 element.
1654 </p>
1655 <p xml:lang="ja" class="t-l-ja">
1656 "artwork" $BMWAG$O!"I,$:B8:_$7$J$1$l$P$J$i$:!"!V(BASCII $B3(!W$+$i@.$j$^$9!#(B
1657 "t", "preamble", "postamble" $B3FMWAGCf$NJ8;zNs$H$O0c$C$F!"?eJ?!&?bD>$I$A$i$N6uGr4V3V$b(B
1658 "artwork" $BMWAGCf$G$O0UL#$r;}$A$^$9!#(B
1659 </p>
1660 </div>
1661 </div>
1662 <div class="rfc-figure">
1663 <span class="rfc-figure-id" id="rfc.figure.u.22">&#x00A0;</span>
1664 <div class="rfc-preamble">
1665 <div class="t-pair">
1666 <p xml:lang="en" class="t-l-en">
1667 So,
1668 putting it all together, we have, e.g.,
1669 </p>
1670 <p xml:lang="ja" class="t-l-ja">
1671 $B$H$$$&$3$H$G!"A4$F$^$H$a$k$H!"<!$NNc$NMM$K$J$j$^$9!#(B
1672 </p>
1673 </div>
1674 </div>
1675
1676 <div class="t-pair">
1677 <p xml:lang="en" class="t-l-en">
1678 <pre class="rfc-artwork" xml:space="preserve">
1679 &lt;figure anchor="figure_example"&gt;
1680 &lt;preamble&gt;So,
1681 putting it all together, we have, e.g.,&lt;/preamble&gt;
1682 &lt;artwork&gt;
1683 ascii artwork goes here...
1684
1685 be sure to use "&amp;lt;" or "&amp;amp;" instead of "&lt;" and "&amp;",
1686 respectively!
1687 &lt;/artwork&gt;
1688 &lt;postamble&gt;which is a very simple example.&lt;/postamble&gt;
1689 &lt;/figure&gt;
1690 </pre>
1691 </p>
1692 <p xml:lang="ja" class="t-l-ja">
1693 <pre class="rfc-artwork" xml:space="preserve">
1694 &lt;figure anchor="figure_example"&gt;
1695 &lt;preamble&gt;$B$H$$$&$3$H$G!"A4$F$^$H$a$k$H!"(B
1696 $B<!$NNc$NMM$K$J$j$^$9!#(B&lt;/preamble&gt;
1697 &lt;artwork&gt;
1698 ascii $B3($,$3$3$KF~$j$^$9(B...
1699
1700 "&amp;lt;" $B$H$+(B "&amp;amp;" $B$r$=$l$>$l(B "&lt;" $B$H(B "&amp;"
1701 $B$NBe$o$j$K;H$&$s$@$h(B!
1702 &lt;/artwork&gt;
1703 &lt;postamble&gt;$BHs>o$KC1=c$JNc$G$7$?!#(B&lt;/postamble&gt;
1704 &lt;/figure&gt;
1705 </pre>
1706 </p>
1707 </div>
1708
1709 <div class="rfc-postamble">
1710 <div class="t-pair">
1711 <p xml:lang="en" class="t-l-en">
1712 which is a very simple example.
1713 </p>
1714 <p xml:lang="ja" class="t-l-ja">
1715 $BHs>o$KC1=c$JNc$G$7$?!#(B
1716 </p>
1717 </div>
1718 </div>
1719 </div>
1720 <div class="rfc-figure">
1721 <span class="rfc-figure-id" id="rfc.figure.u.23">&#x00A0;</span>
1722 <div class="rfc-preamble">
1723 <div class="t-pair">
1724 <p xml:lang="en" class="t-l-en">
1725 If you have artwork with a lot of "&lt;" characters,
1726 then there's an XML trick you can use:
1727 </p>
1728 <p xml:lang="ja" class="t-l-ja">
1729 $BBt;3$N(B "&lt;" $BJ8;z$,3($NCf$K$"$k>l9g$O!"$3$N$h$&$J(B
1730 XML $BKbK!$r;H$&$3$H$,=PMh$^$9!#(B
1731 </p>
1732 </div>
1733 </div>
1734
1735 <div class="t-pair">
1736 <p xml:lang="en" class="t-l-en">
1737 <pre class="rfc-artwork" xml:space="preserve">
1738 &lt;figure&gt;
1739 &lt;preamble&gt;If you have artwork with a lot of "&amp;lt;"
1740 characters, then there's an XML trick you can
1741 use:&lt;/preamble&gt;
1742 &lt;artwork&gt;&lt;![CDATA[
1743 ascii artwork goes here...
1744
1745 just don't use "]]" in your artwork!
1746 ]]&gt;&lt;/artwork&gt;
1747 &lt;postamble&gt;The "&amp;lt;![CDATA[ ... ]]&gt;" construct is called
1748 a CDATA block -- everything between the innermost brackets
1749 is left alone by the XML application.&lt;/postamble&gt;
1750 &lt;/figure&gt;
1751 </pre>
1752 </p>
1753 <p xml:lang="ja" class="t-l-ja">
1754 <pre class="rfc-artwork" xml:space="preserve">
1755 &lt;figure&gt;
1756 &lt;preamble&gt;$BBt;3$N(B "&amp;lt;" $BJ8;z$,3($NCf$K$"$k>l9g$O!"(B
1757 $B$3$N$h$&$J(B XML $BKbK!$r;H$&$3$H$,=PMh$^$9!#(B&lt;/preamble&gt;
1758 &lt;artwork&gt;&lt;![CDATA[
1759 ascii $B$,$3$3$KMh$^$9(B...
1760
1761 $BC1$K(B "]]" $B$r3($NCf$G;H$o$J$$$@$1$G$9(B!
1762 ]]&gt;&lt;/artwork&gt;
1763 &lt;postamble&gt;"&amp;lt;![CDATA[ ... ]]&gt;" $B9=B$$O(B CDATA
1764 $B2t$H8F$P$l$^$9!#0lHVFbB&$N3g8L$N4V$N$b$N$OA4$F(B XML
1765 $B1~MQ$K43>D$5$l$^$;$s!#(B&lt;/postamble&gt;
1766 &lt;/figure&gt;
1767 </pre>
1768 </p>
1769 </div>
1770
1771 <div class="rfc-postamble">
1772 <div class="t-pair">
1773 <p xml:lang="en" class="t-l-en">
1774 The "&lt;![CDATA[ ... ]]&gt;" construct is called a CDATA
1775 block $B!=!=(B everything between the innermost brackets is left alone by
1776 the XML application.
1777 </p>
1778 <p xml:lang="ja" class="t-l-ja">
1779 <samp>$B!V(B&lt;![CDATA[ ... ]]&gt;$B!W(B</samp> $B9=B$$O(B CDATA
1780 $B2t$H8F$P$l$^$9!#0lHVFbB&$N3g8L$N4V$N$b$N$OA4$F(B XML $B1~MQ$K43>D$5$l$^$;$s!#(B
1781 </p>
1782 </div>
1783 </div>
1784 </div>
1785 <div class="rfc-t" id="rfc.section.2.3.1.3.p.6">
1786 <div class="t-pair">
1787 <p xml:lang="en" class="t-l-en">
1788 Because the "figure" element represents a logical grouping of text
1789 and artwork,
1790 an XML application producing a text version of the document should
1791 attempt to keep these elements on the same page.
1792 Because <span class="rfc-xref">
1793 <a href="#refs.RFC2223" title="Instructions to RFC Authors">RFC 2223
1794 &#x00A0;<sup>[2]</sup>
1795 </a>
1796 </span> allows no more than 69
1797 characters by 49 lines of content on each page,
1798 XML applications should be prepared to prematurely introduce page
1799 breaks to allow for better visual grouping.
1800 </p>
1801 <p xml:lang="ja" class="t-l-ja">
1802 "figure" $BMWAG$OJ8=q$H3($NO@M}E*$J=89g$rI=8=$9$k$N$G!"J8=q$N(B
1803 text $BHG$r@8@.$9$k(B XML $B1~MQ$O3FMWAG$rF10lJGCf$KF~$l$k$h$&$K:v$9$k$Y$-$G$9!#(B
1804 <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">RFC 2223
1805 &#x00A0;<sup>[2]</sup>
1806 </a>
1807 $B$,3FJG(B49$B9T$NFbMF$G(B, 69$BJ8;z$rD6$($k$N$rG'$a$F$$$J$$$N$G!"(B
1808 XML $B1~MQ$O$h$jNI$$;k3PE*=89g2=$r9T$&$?$a$KM=$a2~JG$9$k=`Hw$r$7$F$*$/$Y$-$G$9!#(B
1809 </p>
1810 </div>
1811 </div>
1812 <div class="rfc-t" id="rfc.section.2.3.1.3.p.7">
1813 <div class="t-pair">
1814 <p xml:lang="en" class="t-l-en">
1815 Finally,
1816 the "artwork" element has two optional attributes:
1817 "name" and "type".
1818 The former is used to suggest a filename to use when storing the
1819 content of the "artwork" element,
1820 whilst the latter contains a suggestive data-typing for the content.
1821 </p>
1822 <p xml:lang="ja" class="t-l-ja">
1823 $B:G8e$K!"(B "artwork" $BMWAG$O(B2$B$D$N>JN,2DG=$JB0@-(B "name", "type"
1824 $B$r;}$A$^$9!#A0<T$O(B "artwork" $BMWAG$NFbMF$rJ]4I$9$k;~$K;H$&%U%!%$%kL>$N0F$r?d$9$N$K;H$$$^$9!#8e<T$OFbMF$N%G!<%?7?$r<($9$N$K;H$$$^$9!#(B
1825 </p>
1826 </div>
1827 </div>
1828 </div>
1829 <div class="rfc-section" id="rfc.section.2.3.1.4">
1830 <div class="t-pair t-heading" id="xref">
1831 <h4 xml:lang="en" class="t-l-en">2.3.1.4. The xref Element</h4>
1832 <h4 xml:lang="ja" class="t-l-ja">2.3.1.4.
1833 xref $BMWAG(B</h4>
1834 </div>
1835 <div class="rfc-t" id="rfc.section.2.3.1.4.p.1">
1836 <div class="t-pair">
1837 <p xml:lang="en" class="t-l-en">
1838 The "xref" element is used to cross-reference sections, figures, and
1839 references.
1840 The mandatory "target" attribute is used to link back to the "anchor"
1841 attribute of the "section", "figure", and "reference" elements.
1842 The value of the "anchor" and "target" attributes should be formatted
1843 according to the token syntax in <span class="rfc-xref">
1844 <a href="#xml_basics" title="XML basics">
1845 section 2.1</a>
1846 </span>.
1847 </p>
1848 <p xml:lang="ja" class="t-l-ja">
1849 "xref" $BMWAG$O@a!&?^!&;29MJ88%$N8r:9;2>H$K;H$$$^$9!#I,?\$N(B
1850 "target" $BB0@-$O(B "section", "figure", "reference" $BMWAG$N(B
1851 "anchor" $BB0@-$K5U@\B3$9$k$N$K;H$$$^$9!#(B
1852 "anchor" $B$*$h$S(B "target" $BN>B0@-$NCM$O(B <a href="#xml_basics" title="XML $B$N4pAC(B">2.1$B@a(B</a>
1853 $B$N;z6g(B (token) $B9=J8$K=>$$=q<02=$5$l$k$Y$-$G$9!#(B
1854 </p>
1855 </div>
1856 </div>
1857 <div class="rfc-figure">
1858 <span class="rfc-figure-id" id="rfc.figure.u.24">&#x00A0;</span>
1859 <div class="rfc-preamble">
1860 <div class="t-pair">
1861 <p xml:lang="en" class="t-l-en">
1862 If used as an empty element,
1863 e.g.,
1864 </p>
1865 <p xml:lang="ja" class="t-l-ja">
1866 $B6uMWAG$H$7$F;H$&;~$O(B
1867 </p>
1868 </div>
1869 </div>
1870
1871 <div class="t-pair">
1872 <p xml:lang="en" class="t-l-en">
1873 <pre class="rfc-artwork" xml:space="preserve">
1874 according to the token syntax in &lt;xref target="xml_basics" /&gt;.
1875 </pre>
1876 </p>
1877 <p xml:lang="ja" class="t-l-ja">
1878 <pre class="rfc-artwork" xml:space="preserve">
1879 &lt;xref target="xml_basics" /&gt; $B$N;z6g(B (token) $B9=J8$K=>$$(B
1880 </pre>
1881 </p>
1882 </div>
1883
1884 <div class="rfc-postamble">
1885 <div class="t-pair">
1886 <p xml:lang="en" class="t-l-en">
1887 then the XML application inserts an appropriate phrase
1888 during processing,
1889 such as "Section 2.1" or
1890 "&lt;a href="#xml_basics"&gt;XML Basics&lt;/a&gt;".
1891 </p>
1892 <p xml:lang="ja" class="t-l-ja">
1893 $B$NMM$K$J$j!"(B XML $B1~MQ$O(B <samp>$B!V(B2.1 $B@a!W(B</samp> $B$d(B
1894 <samp>$B!V(B&lt;a href="#xml_basics"&gt;XML $B$N4pAC(B&lt;/a&gt;$B!W(B</samp>
1895 $B$N$h$&$KE,@Z$JJ8;zNs$r=hM}$K$h$jA^F~$7$^$9!#(B
1896 </p>
1897 </div>
1898 </div>
1899 </div>
1900 <div class="rfc-figure">
1901 <span class="rfc-figure-id" id="rfc.figure.u.25">&#x00A0;</span>
1902 <div class="rfc-preamble">
1903 <div class="t-pair">
1904 <p xml:lang="en" class="t-l-en">
1905 If used with content, e.g.,
1906 </p>
1907 <p xml:lang="ja" class="t-l-ja">
1908 $BFbMF$"$j$G;H$&;~$O(B
1909 </p>
1910 </div>
1911 </div>
1912
1913 <div class="t-pair">
1914 <p xml:lang="en" class="t-l-en">
1915 <pre class="rfc-artwork" xml:space="preserve">
1916 conforming to &lt;xref target="refs.RFC2223"&gt;RFC 2223&lt;/xref&gt;.
1917 </pre>
1918 </p>
1919 <p xml:lang="ja" class="t-l-ja">
1920 <pre class="rfc-artwork" xml:space="preserve">
1921 &lt;xref target="refs.RFC2223"&gt;RFC 2223&lt;/xref&gt; $B$KE,9g$9$k(B
1922 </pre>
1923 </p>
1924 </div>
1925
1926 <div class="rfc-postamble">
1927 <div class="t-pair">
1928 <p xml:lang="en" class="t-l-en">
1929 then the XML application inserts an appropriate
1930 designation during processing,
1931 such as "RFC 2223[2]" or
1932 "&lt;a href="#refs.RFC2223"&gt;RFC 2223&lt;/a&gt;".
1933 Although the XML application decides what "an appropriate designation"
1934 might be,
1935 its choice is consistent throughout the processing of the document.
1936 </p>
1937 <p xml:lang="ja" class="t-l-ja">
1938 $B$NMM$K$J$j!"(B XML $B1~MQ$O(B <samp>$B!V(BRFC 2223[2]$B!W(B</samp> $B$d(B
1939 <samp>$B!V(B&lt;a href="#refs.RFC2223"&gt;RFC 2223&lt;/a&gt;$B!W(B</samp>
1940 $B$N$h$&$KE,@Z$J;X<($r=hM}$K$h$jA^F~$7$^$9!#!VE,@Z$J;X<(!W$NFbMF$O(B
1941 XML $B1~MQ$,7h$a$^$9$,!"A*Br$OEv3:J8=q$N=hM}$rDL$8$F8GDj$G$9!#(B
1942 </p>
1943 </div>
1944 </div>
1945 </div>
1946 </div>
1947
1948 <div class="rfc-section" id="rfc.section.2.3.1.5">
1949 <div class="t-pair t-heading" id="eref">
1950 <h4 xml:lang="en" class="t-l-en">2.3.1.5. The eref Element</h4>
1951 <h4 xml:lang="ja" class="t-l-ja">2.3.1.5.
1952 eref $BMWAG(B</h4>
1953 </div>
1954 <div class="rfc-figure">
1955 <span class="rfc-figure-id" id="rfc.figure.u.26">&#x00A0;</span>
1956 <div class="rfc-preamble">
1957 <div class="t-pair">
1958 <p xml:lang="en" class="t-l-en">
1959 The "eref" element is used to reference external documents.
1960 The mandatory "target" attribute is a
1961 <span class="rfc-xref">
1962 <a href="#URI" title="Uniform Resource Identifiers (URI): Generic Syntax">URI
1963 &#x00A0;<sup>[4]</sup>
1964 </a>
1965 </span>, e.g.,
1966 </p>
1967 <p xml:lang="ja" class="t-l-ja">
1968 "eref" $BMWAG$O!"30ItJ8=q$r;2>H$9$k$N$K;H$$$^$9!#I,?\$N(B
1969 "target" $BB0@-$O(B <a href="#URI" title="$BE}0l;q8;<1JL;R(B (URI): $B0lHL9=J8(B">URI
1970 &#x00A0;<sup>[4]</sup>
1971 </a>
1972 $B$G!"<!$NMM$K;H$$$^$9!#(B
1973 </p>
1974 </div>
1975 </div>
1976 <pre class="rfc-artwork" xml:space="preserve">
1977 &lt;eref target="http://metalab.unc.edu/xml/"&gt;Cafe con Leche&lt;/eref&gt;
1978 </pre>
1979 </div>
1980 <div class="rfc-figure">
1981 <span class="rfc-figure-id" id="rfc.figure.u.27">&#x00A0;</span>
1982 <div class="rfc-preamble">
1983 <div class="t-pair">
1984 <p xml:lang="en" class="t-l-en">
1985 Note that while the "target" attribute is always present,
1986 the "eref" element may be empty, e.g.,
1987 </p>
1988 <p xml:lang="ja" class="t-l-ja">
1989 "target" $BB0@-$O>o$KI,MW$G$"$j!"(B "eref" $BMWAG$O6u$G$"$jF@$k$3$H$KCm0U$7$F2<$5$$!#(B
1990 </p>
1991 </div>
1992 </div>
1993 <pre class="rfc-artwork" xml:space="preserve">
1994 &lt;eref target="http://invisible.net/" /&gt;
1995 </pre>
1996 <div class="rfc-postamble">
1997 <div class="t-pair">
1998 <p xml:lang="en" class="t-l-en">
1999 and the XML application inserts an appropriate designation during
2000 processing such as "[9]" or
2001 "&lt;a href="http://invisible.net/"&gt;http://invisible.net/&lt;/a&gt;".
2002 </p>
2003 <p xml:lang="ja" class="t-l-ja">
2004 XML $B1~MQ$O(B <samp>$B!V(B[9]$B!W(B</samp> $B$d(B
2005 <samp>$B!V(B&lt;a href="http://invisible.net/"&gt;http://invisible.net/&lt;/a&gt;$B!W(B</samp>
2006 $B$NMM$KE,@Z$J;X<($r=hM}$N2aDx$GA^F~$7$^$9!#(B
2007 </p>
2008 </div>
2009 </div>
2010 </div>
2011 </div>
2012 <div class="rfc-section" id="rfc.section.2.3.1.6">
2013 <div class="t-pair t-heading" id="iref">
2014 <h4 xml:lang="en" class="t-l-en">2.3.1.6. The iref Element</h4>
2015 <h4 xml:lang="ja" class="t-l-ja">2.3.1.6.
2016 iref $BMWAG(B</h4>
2017 </div>
2018 <div class="rfc-figure">
2019 <span class="rfc-figure-id" id="rfc.figure.u.28">&#x00A0;</span>
2020 <div class="rfc-preamble">
2021 <div class="t-pair">
2022 <p xml:lang="en" class="t-l-en">
2023 <span class="rfc-iref" id="rfc.iref.1">&#x00A0;</span>The "iref" element
2024 is used to add information to an index.
2025 The mandatory "item" attribute is the primary key the information is stored
2026 under,
2027 whilst the optional "subitem" attribute is the secondary key, e.g.,
2028 </p>
2029 <p xml:lang="ja" class="t-l-ja">
2030 <span class="rfc-iref" id="rfc.iref.2">&#x00A0;</span>"iref"
2031 $BMWAG$O:w0z$K>pJs$rDI2C$9$k$N$K;H$$$^$9!#I,?\$NB0@-(B "item"
2032 $B$O>pJs$,J]4I$5$l$k<g80$G!">JN,2DG=$J(B "subitem" $BB0@-$OI{80$G$9!#(B
2033 </p>
2034 </div>
2035 </div>
2036
2037 <div class="t-pair">
2038 <p xml:lang="en" class="t-l-en">
2039 <pre class="rfc-artwork" xml:space="preserve">
2040 &lt;iref item="indexing" subitem="how to" /&gt;
2041 </pre>
2042 </p>
2043 <p xml:lang="ja" class="t-l-ja">
2044 <pre class="rfc-artwork" xml:space="preserve">
2045 &lt;iref item="$B:w0zIU$1(B" subitem="$BJ}K!(B" /&gt;
2046 </pre>
2047 </p>
2048 </div>
2049
2050 </div>
2051 <div class="rfc-t" id="rfc.section.2.3.1.6.p.2">
2052 <div class="t-pair">
2053 <p xml:lang="en" class="t-l-en">
2054 Finally, note that the "iref" element is always empty $B!=!=(B it never
2055 contains any text.
2056 </p>
2057 <p xml:lang="ja" class="t-l-ja">
2058 $B:G8e$K!"(B "iref"
2059 $BMWAG$O>o$K6u$G$"$k!=!=$I$s$JJ8;zNs$b4^$^$J$$$H$$$&$3$H$KCm0U$7$F2<$5$$!#(B
2060 </p>
2061 </div>
2062 </div>
2063 </div>
2064 <div class="rfc-section" id="rfc.section.2.3.1.7">
2065 <div class="t-pair t-heading">
2066 <h4 xml:lang="en" class="t-l-en">2.3.1.7. The vspace Element</h4>
2067 <h4 xml:lang="ja" class="t-l-ja">2.3.1.7.
2068 vspace $BMWAG(B</h4>
2069 </div>
2070 <div class="rfc-t" id="rfc.section.2.3.1.7.p.1">
2071 <div class="t-pair">
2072 <p xml:lang="en" class="t-l-en">
2073 The "vspace" element,
2074 which may occur only inside the "t" element,
2075 is used by the author to provide formatting guidance to the XML
2076 application.
2077 There is an attribute,
2078 "blankLines",
2079 that indicates the number of blank lines that should be inserted.
2080 A physical linebreak is specified by using the default value, "0".
2081 </p>
2082 <p xml:lang="ja" class="t-l-ja">
2083 "vspace" $BMWAG$O!"(B "t" $BMWAG$NCf$K$N$_8=$l$k$3$H$,=PMh$F!"Cx<T$,(B
2084 XML $B1~MQ$K@07A$N<j0z$-$rM?$($k$N$K;H$$$^$9!#(B "blankLines"
2085 $BB0@-$,$"$j!"A^F~$5$l$k$Y$-6uGr9T$N?t$r<($7$^$9!#J*M}2~9T$O4{DjCM$G$"$k(B
2086 "0" $B$r;H$C$FI=$7$^$9!#(B
2087 </p>
2088 </div>
2089 </div>
2090 <div class="rfc-figure">
2091 <span class="rfc-figure-id" id="rfc.figure.u.29">&#x00A0;</span>
2092 <div class="rfc-preamble">
2093 <div class="t-pair">
2094 <p xml:lang="en" class="t-l-en">
2095 In addition,
2096 the "vspace" element can be used to force a new physical paragraph
2097 within a list item, e.g.,
2098 </p>
2099 <p xml:lang="ja" class="t-l-ja">
2100 $B2C$($F!"(B "vspace" $BMWAG$O<!$KNc<($9$k$h$&$K!"?7$7$$7A<0CJMn$r0lMw9`L\Cf$K:n$j=P$9$N$K;H$&$3$H$,=PMh$^$9!#(B
2101 </p>
2102 </div>
2103 </div>
2104
2105 <div class="t-pair">
2106 <p xml:lang="en" class="t-l-en">
2107 <pre class="rfc-artwork" xml:space="preserve">
2108 &lt;list style="numbers"&gt;
2109 &lt;t&gt;This is list item.
2110 &lt;vspace blankLines="1" /&gt;
2111 This is part of the same list item,
2112 although when displayed, it appears
2113 as a separate physical paragraph.&lt;/t&gt;
2114 &lt;/list&gt;
2115 </pre>
2116 </p>
2117 <p xml:lang="ja" class="t-l-ja">
2118 <pre class="rfc-artwork" xml:space="preserve">
2119 &lt;list style="numbers"&gt;
2120 &lt;t&gt;$B$3$l$O0lMw$N9`L\$G$9!#(B
2121 &lt;vspace blankLines="1" /&gt;
2122 $B$3$l$OF1$80lMw9`L\$G$9!#(B
2123 $B$7$+$7I=<($N:]$K$OJL$N7A<0CJMn$K8+$($^$9!#(B&lt;/t&gt;
2124 &lt;/list&gt;
2125 </pre>
2126 </p>
2127 </div>
2128
2129 </div>
2130 <div class="rfc-t" id="rfc.section.2.3.1.7.p.3">
2131 <div class="t-pair">
2132 <p xml:lang="en" class="t-l-en">
2133 An XML application producing a text version of the document should
2134 exercise care when encountering a value for "blankLines" that causes a
2135 pagebreak $B!=!=(B
2136 in particular,
2137 if a "vspace" element causes a pagebreak,
2138 then no further blank lines should be inserted.
2139 This allows authors to "force" a pagebreak by using an arbitrarily
2140 large value, e.g., "blankLines='100'".
2141 </p>
2142 <p xml:lang="ja" class="t-l-ja">
2143 $BJ8=q$N(B text $BHG$r@8@.$9$k(B XML $B1~MQ$O!"2~JG$r5/$3$9$h$&$J(B
2144 "breakLines" $B$NCM$G$"$C$?;~$KCm0U$9$k$Y$-$G$9!#(B
2145 "vspace" $BMWAG$,2~JG$r5/$3$9;~$O!"$=$l0J>e6uGr9T$rA^F~$9$k$Y$-$G$O$"$j$^$;$s!#$3$l$K$h$j!"Cx<T$OG$0U$NBg$-$JCM!"Nc$($P(B
2146 <samp>$B!V(BblankLines='100'$B!W(B</samp> $B$G!V6/@)!W2~JG$5$;$k$3$H$,=PMh$^$9!#(B
2147 </p>
2148 </div>
2149 </div>
2150 <div class="rfc-t" id="rfc.section.2.3.1.7.p.4">
2151 <div class="t-pair">
2152 <p xml:lang="en" class="t-l-en">
2153 Finally, note that the "vspace" element is always empty $B!=!=(B it never
2154 contains any text.
2155 </p>
2156 <p xml:lang="ja" class="t-l-ja">
2157 $B:G8e$K!"(B "vspace" $BMWAG$O>o$K6u$G$"$k!=!=J8;zNs$r4^$^$J$$$H$$$&$3$H$KCm0U$7$F2<$5$$!#(B
2158 </p>
2159 </div>
2160 </div>
2161 </div>
2162 </div>
2163 </div>
2164 <div class="rfc-section" id="rfc.section.2.4">
2165 <div id="back_matter">
2166 <h2>2.4. Back matter</h2>
2167 </div>
2168 <div class="rfc-figure">
2169 <span class="rfc-figure-id" id="rfc.figure.u.30">&#x00A0;</span>
2170 <div class="rfc-preamble">
2171 <div class="t-pair">
2172 <p xml:lang="en" class="t-l-en">
2173 Finally,
2174 the "back" element is used for references and
2175 appendices:
2176 </p>
2177 <p xml:lang="ja" class="t-l-ja">
2178 $B:G8e$K!"(B "back" $BMWAG$O;29MJ88%$HImB0=q$K;H$$$^$9!#(B
2179 </p>
2180 </div>
2181 </div>
2182 <pre class="rfc-artwork" xml:space="preserve">
2183 ...
2184 &lt;/middle&gt;
2185 &lt;back&gt;
2186 &lt;references&gt;
2187 &lt;reference ...&gt;
2188 &lt;reference ...&gt;
2189 &lt;/references&gt;
2190 &lt;section ...&gt;
2191 &lt;section ...&gt;
2192 &lt;/back&gt;
2193 &lt;/rfc&gt;
2194 </pre>
2195 <div class="rfc-postamble">
2196 <div class="t-pair">
2197 <p xml:lang="en" class="t-l-en">
2198 The "back" element consists of an optional "references" element,
2199 and,
2200 one or more optional "section" elements.
2201 The "back" element itself is optional,
2202 if your document doesn't have any references or appendices,
2203 you don't have to include it.
2204 </p>
2205 <p xml:lang="ja" class="t-l-ja">
2206 "back" $BMWAG$O>JN,2DG=$J(B "references" $BMWAG$H!"(B1$B$D0J>e$N>JN,2DG=$J(B
2207 "section" $BMWAG$+$i@.$j$^$9!#(B "back" $BMWAG<+BN$O>JN,2DG=$G!"J8=q$K;29MJ88%$bImB0=q$b$J$$>l9g$O!"4^$a$kI,MW$O$"$j$^$;$s!#(B
2208 </p>
2209 </div>
2210 </div>
2211 </div>
2212 <div class="rfc-section" id="rfc.section.2.4.1">
2213 <div class="t-pair t-heading" id="references">
2214 <h3 xml:lang="en" class="t-l-en">2.4.1. The references Element</h3>
2215 <h3 xml:lang="ja" class="t-l-ja">2.4.1.
2216 references $BMWAG(B</h3>
2217 </div>
2218 <div class="rfc-t" id="rfc.section.2.4.1.p.1">
2219 <div class="t-pair">
2220 <p xml:lang="en" class="t-l-en">
2221 The "references" element contains the document's bibliography.
2222 It contains one or more "reference" elements.
2223 </p>
2224 <p xml:lang="ja" class="t-l-ja">
2225 "references" $BMWAG$OJ8=q$N;29MJ88%$+$i@.$j$^$9!#(B1$B$D0J>e$N(B
2226 "reference" $BMWAG$+$i@.$j$^$9!#(B
2227 </p>
2228 </div>
2229 </div>
2230 <div class="rfc-t" id="rfc.section.2.4.1.p.2">
2231 <div class="t-pair">
2232 <p xml:lang="en" class="t-l-en">
2233 Each "reference" element contains a "front" element and one or more
2234 optional "seriesInfo" elements.
2235 </p>
2236 <p xml:lang="ja" class="t-l-ja">
2237 $B3F(B "references" $BMWAG$O(B "front" $BMWAG$H(B1$B$D0J>e$N>JN,2DG=$J(B
2238 "seriesInfo" $BMWAG$+$i@.$j$^$9!#(B
2239 </p>
2240 </div>
2241 </div>
2242 <div class="rfc-t" id="rfc.section.2.4.1.p.3">
2243 <div class="t-pair">
2244 <p xml:lang="en" class="t-l-en">
2245 We've already discussed the "front" element back in
2246 <span class="rfc-xref">
2247 <a href="#front_matter" title="Front matter">
2248 section 2.2</a>
2249 </span>.
2250 </p>
2251 <p xml:lang="ja" class="t-l-ja">
2252 "front" $BMWAG$K$D$$$F$O(B <a href="#front_matter" title="">2.2$B@a(B</a>
2253 $B$G4{$KOC$7$^$7$?!#(B
2254 </p>
2255 </div>
2256 </div>
2257 <div class="rfc-t" id="rfc.section.2.4.1.p.4">
2258 <div class="t-pair">
2259 <p xml:lang="en" class="t-l-en">
2260 The "seriesInfo" element has two attributes,
2261 "name" and "value" that identify the document series and series entry,
2262 respectively.
2263 </p>
2264 <p xml:lang="ja" class="t-l-ja">
2265 "seriesInfo" $BMWAG$O(B "name", "value" $B$N(B2$B$D$NB0@-$r;}$A!"$=$l$>$lJ8=q7ONs$H7ONs9`L\$rFCDj$7$^$9!#(B
2266 </p>
2267 </div>
2268 </div>
2269 <div class="rfc-figure">
2270 <span class="rfc-figure-id" id="rfc.figure.u.31">&#x00A0;</span>
2271 <div class="rfc-preamble">
2272 <div class="t-pair">
2273 <p xml:lang="en" class="t-l-en">
2274 The "reference" element has an optional "anchor"
2275 attribute that is used for cross-referencing with
2276 <span class="rfc-xref">
2277 <a href="#xref" title="">the "xref" element</a>
2278 </span>, e.g.,
2279 </p>
2280 <p xml:lang="ja" class="t-l-ja">
2281 "reference" $BMWAG$O>JN,2DG=$J(B "anchor" $BB0@-$r;}$A!"(B
2282 $B<!$NMM$K;H$$!"(B <a href="#xref" title="">"xref" $BMWAG(B</a>$B$G8r:9;2>H$K;H$&$3$H$,=PMh$^$9!#(B
2283 </p>
2284 </div>
2285 </div>
2286 <pre class="rfc-artwork" xml:space="preserve">
2287 &lt;reference anchor="refs.RFC2200"&gt;
2288 &lt;front&gt;
2289 &lt;title&gt;Internet Official Protocol Standards&lt;/title&gt;
2290 &lt;author initials="J." surname="Postel"
2291 fullname="Jon Postel"&gt;
2292 &lt;organization abbrev="ISI"&gt;
2293 USC/Information Sciences Institute
2294 &lt;/organization&gt;
2295 &lt;/author&gt;
2296
2297 &lt;date month="June" year="1997" /&gt;
2298 &lt;/front&gt;
2299 &lt;seriesInfo name="RFC" value="2200" /&gt;
2300 &lt;seriesInfo name="STD" value="1" /&gt;
2301 &lt;/reference&gt;
2302 </pre>
2303 </div>
2304 <div class="rfc-t" id="rfc.section.2.4.1.p.6">
2305 <div class="t-pair">
2306 <p xml:lang="en" class="t-l-en">
2307 The "reference" element also has an optional "target"
2308 attribute that is used for external references
2309 (c.f., <span class="rfc-xref">
2310 <a href="#eref" title="The eref Element">
2311 section 2.3.1.5</a>
2312 </span>).
2313 The XML application,
2314 if producing an HTML version of the document will use the "target"
2315 attribute accordingly;
2316 however, if the "name" attribute of the "seriesInfo" element has the value
2317 "RFC",
2318 then the XML application should automatically provide an appropriate
2319 default for the "target" attribute
2320 (e.g., "http://example.com/rfcs/rfc2200.txt").
2321 </p>
2322 <p xml:lang="ja" class="t-l-ja">
2323 "reference" $BMWAG$K$O>JN,2DG=$J(B "target" $BB0@-$,$"$j!"30It;2>H$K;H$$$^$9!#(B
2324 (cf. <a href="#eref" title="eref $BMWAG(B">2.3.1.5$B@a(B</a>) XML $B1~MQ$OJ8=q$N(B HTML $BHG$r@8@.$9$k;~$K(B
2325 "target" $BB0@-$r;H$$$^$9!#$7$+$7!"(B "seriseInfo" $BMWAG$N(B "name"
2326 $BB0@-$,CM(B "RFC" $B$r;}$D>l9g!"(B XML $B1~MQ$O<+F0E*$KE,@Z$J(B "target"
2327 $BB0@-$N4{DjCM$rMQ0U$9$k$Y$-$G$9!#(B ($BNc$($P(B
2328 <samp>$B!V(Bhttp://example.com/rfcs/rfc2200.txt$B!W(B</samp>)
2329 </p>
2330 </div>
2331 </div>
2332 </div>
2333 <div class="rfc-section" id="rfc.section.2.4.2">
2334 <div class="t-pair t-heading">
2335 <h3 xml:lang="en" class="t-l-en">2.4.2. Appendices</h3>
2336 <h3 xml:lang="ja" class="t-l-ja">2.4.2.
2337 $BImB0=q(B</h3>
2338 </div>
2339 <div class="rfc-t" id="rfc.section.2.4.2.p.1">
2340 <div class="t-pair">
2341 <p xml:lang="en" class="t-l-en">
2342 To include appendices after the bibliography,
2343 simply add more "section" elements.
2344 (For an example,
2345 look at the example at the beginning of <span class="rfc-xref">
2346 <a href="#back_matter" title="Back matter">
2347 section 2.4</a>
2348 </span>.)
2349 </p>
2350 <p xml:lang="ja" class="t-l-ja">
2351 $B;29MJ88%$N8e$KImB0=q$r4^$a$k$K$O!"C1$K(B "section"
2352 $BMWAG$rDI2C$9$k$@$1$G$9!#(B ($BNc$H$7$F!"(B <a href="#back_matter" title="">2.4$B@a(B</a>
2353 $B$N$O$8$a$NNc$r8fMw2<$5$$!#(B)
2354 </p>
2355 </div>
2356 </div>
2357 </div>
2358 <div class="rfc-section" id="rfc.section.2.4.3">
2359 <div class="t-pair t-heading">
2360 <h3 xml:lang="en" class="t-l-en">2.4.3. Copyright Status</h3>
2361 <h3 xml:lang="ja" class="t-l-ja">2.4.3.
2362 $BCx:n8">uBV(B</h3>
2363 </div>
2364 <div class="rfc-t" id="rfc.section.2.4.3.p.1">
2365 <div class="t-pair">
2366 <p xml:lang="en" class="t-l-en">
2367 The copyright status for the document is not included in the
2368 document's markup $B!=!=(B this is automatically inserted by an XML
2369 application that produces either a text or HTML version of the document.
2370 </p>
2371 <p xml:lang="ja" class="t-l-ja">
2372 $BJ8=q$NCx:n8">uBV$OJ8=q$N%^!<%/IU$1$K$O4^$a$^$;$s!#(B
2373 $B$3$l$OJ8=q$N(B text $BHG$+(B HTML $BHG$r@8@.$9$k(B XML
2374 $B1~MQ$K$h$j<+F0E*$KA^F~$5$l$^$9!#(B
2375 </p>
2376 </div>
2377 </div>
2378 </div>
2379 </div>
2380 </div>
2381 <div class="rfc-section" id="rfc.section.3">
2382 <div class="t-pair t-heading">
2383 <h1 xml:lang="en" class="t-l-en">3. Processing the XML Source File</h1>
2384 <h1 xml:lang="ja" class="t-l-ja">3.
2385 XML $B8;%U%!%$%k$N=hM}(B</h1>
2386 </div>
2387 <div class="rfc-t" id="rfc.section.3.p.1">
2388 <div class="t-pair">
2389 <p xml:lang="en" class="t-l-en">
2390 This section concerns itself with applications that operate on
2391 an XML source file.
2392 A lot of XML tools are available,
2393 as are many lists of XML resources,
2394 e.g.,
2395 <a href="http://metalab.unc.edu/xml/" title="URI: &lt;http://metalab.unc.edu/xml/>">Cafe con Leche</a>.
2396 </p>
2397 <p xml:lang="ja" class="t-l-ja">
2398 $B$3$N@a$O(B XML $B8;%U%!%$%k$r=hM}$9$k1~MQ$K$D$$$F$G$9!#Bt;3$N(B
2399 XML $B9)6q$,MxMQ2DG=$G$9$7!"Bt;3$N(B XML $B;q8;$N0lMw$b!"Nc$($P(B
2400 <a href="http://metalab.unc.edu/xml/" title="URI: &lt;http://metalab.unc.edu/xml/>">Cafe con Leche</a>
2401 $B$K$"$j$^$9!#(B
2402 </p>
2403 </div>
2404 </div>
2405 <div class="rfc-t" id="rfc.section.3.p.2">
2406 <div class="t-pair">
2407 <p xml:lang="en" class="t-l-en">
2408 There are two kinds of XML tools: validating and non-validating.
2409 Both check that the source file conforms to the rules given in
2410 <span class="rfc-xref">
2411 <a href="#xml_basics" title="XML basics">
2412 section 2.1</a>
2413 </span>.
2414 However,
2415 in addition to making sure that the source file is well-formed,
2416 a validating tool also reads the DTD referenced by the source file
2417 to make sure that they match.
2418 There are a number of both validating and non-validating tools available.
2419 </p>
2420 <p xml:lang="ja" class="t-l-ja">
2421 XML $B9)6q$K$O(B2$B<oN`$"$j$^$9(B: $B8!>Z$9$k$b$N$H8!>Z$7$J$$$b$N$G$9!#N><T6&$K!"8;%U%!%$%k$,(B
2422 <a href="#xml_basics" title="XML $B$N4pAC(B">2.1$B@a(B</a> $B$K5s$2$?5,B'$KE,9g$9$k$+$O3NG'$7$^$9!#$7$+$7!"2C$($F8;%U%!%$%k$,@07A<0$G$"$k$+$r3NG'$9$k$?$a!"8!>Z9)6q$O8=%U%!%$%k$,;2>H$7$F$$$k(B
2423 DTD $B$bFI$s$G0lCW$7$F$$$k$+3NG'$7$^$9!#8!>Z!&Hs8!>Z9)6q6&$KB??tF~<j=PMh$^$9!#(B
2424 </p>
2425 </div>
2426 </div>
2427 <div class="rfc-section" id="rfc.section.3.1">
2428 <div class="t-pair t-heading">
2429 <h2 xml:lang="en" class="t-l-en">3.1. Editing</h2>
2430 <h2 xml:lang="ja" class="t-l-ja">3.1.
2431 $BJT=8(B</h2>
2432 </div>
2433 <div class="rfc-t" id="rfc.section.3.1.p.1">
2434 <div class="t-pair">
2435 <p xml:lang="en" class="t-l-en">
2436 There are several XML editors available.
2437 Ideally,
2438 you want an editor that validates.
2439 This has two advantages:
2440 </p>
2441 <p xml:lang="ja" class="t-l-ja">
2442 XML $B%(%G%#%?!<$O4v$D$+F~<j2DG=$G$9!#M}A[E*$K$O!"8!>Z=PMh$k%(%G%#%?!<$,NI$$$G$7$g$&!#$3$l$K$O(B2$B$D$NMxE@$,$"$j$^$9!#(B
2443 </p>
2444 </div>
2445
2446 <ul class="rfc-list-symbols text">
2447 <li>
2448 <div class="t-pair">
2449 <p xml:lang="en" class="t-l-en">
2450 the editor provides guidance in fleshing-out the document structure;
2451 and,
2452 </p>
2453 <p xml:lang="ja" class="t-l-ja">
2454 $B%(%G%#%?!<$,J8=q9=B$$KFyIU$1$9$k<j0z$-$r<($9(B
2455 </p>
2456 </div>
2457 </li>
2458 <li>
2459 <div class="t-pair">
2460 <p xml:lang="en" class="t-l-en">
2461 the editor validates that the source file matches the rules in the DTD.
2462 </p>
2463 <p xml:lang="ja" class="t-l-ja">
2464 $B%(%G%#%?!<$,8;%U%!%$%k$,(B DTD $B$N5,B'$H0lCW$7$F$$$k$+8!>Z$9$k(B
2465 </p>
2466 </div>
2467 </li>
2468 </ul>
2469 </div>
2470 <div class="rfc-figure">
2471 <span class="rfc-figure-id" id="rfc.figure.u.32">&#x00A0;</span>
2472 <div class="rfc-preamble">
2473 <div class="t-pair">
2474 <p xml:lang="en" class="t-l-en">
2475 There are two major modes in Emacs that support XML:
2476 <a href="http://www.mulberrytech.com/tdtd/" title="URI: &lt;http://www.mulberrytech.com/tdtd/>">tdtd</a> and
2477 <a href="http://www.inria.fr/koala/plh/sxml.html" title="URI: &lt;http://www.inria.fr/koala/plh/sxml.html>">psgml</a>.
2478 The latter mode allows you to validate the source file
2479 (by calling an external program).
2480 If you visit the source file in Emacs and the major mode isn't
2481 "SGML" or "XML",
2482 then usually all it takes is adding these lines to your ".emacs"
2483 file:
2484 </p>
2485 <p xml:lang="ja" class="t-l-ja">
2486 Emacs $B$G$O(B XML $B$KBP1~$7$?(B2$B$D$NBg%b!<%I!"(B
2487 <a href="http://www.mulberrytech.com/tdtd/" title="URI: &lt;http://www.mulberrytech.com/tdtd/>">tdtd</a> $B$H(B
2488 <a href="http://www.inria.fr/koala/plh/sxml.html" title="URI: &lt;http://www.inria.fr/koala/plh/sxml.html>">psgml</a>
2489 $B$,$"$j$^$9!#8e<T$N%b!<%I$G$O8;%U%!%$%k$r(B
2490 ($B30It%W%m%0%i%`$r8F$S=P$9$3$H$K$h$j(B) $B8!>Z$9$k$3$H$,=PMh$^$9!#8;%U%!%$%k$r(B
2491 Emacs $B$G$_$F!"Bg%b!<%I$,(B $B!V(BSGML$B!W(B $B$+(B $B!V(BXML$B!W(B
2492 $B$K$J$i$J$$>l9g!"DL>o$O(B ".emacs" $B%U%!%$%k$K<!$N9T(B
2493 </p>
2494 </div>
2495 </div>
2496 <pre class="rfc-artwork" xml:space="preserve">
2497 (setq auto-mode-alist
2498 (cons (cons "\\.xml$" 'sgml-mode) auto-mode-alist))
2499 </pre>
2500 <div class="rfc-postamble">
2501 <div class="t-pair">
2502 <p xml:lang="en" class="t-l-en">
2503 and then restarting Emacs.
2504 If this doesn't work,
2505 try one of the sources above.
2506 </p>
2507 <p xml:lang="ja" class="t-l-ja">
2508 $B$r2C$($F!"(B Emacs $B$r:F5/F0$7$^$9!#$3$l$G>e<j$/$$$+$J$1$l$P!">e5-$N>pJs8;$N$$$:$l$+$r;n$7$F$_$F2<$5$$!#(B
2509 </p>
2510 </div>
2511 </div>
2512 </div>
2513 <div class="rfc-t" id="rfc.section.3.1.p.3">
2514 <div class="t-pair">
2515 <p xml:lang="en" class="t-l-en">
2516 The author uses both sgml-mode in Emacs,
2517 and a commercial validating editor,
2518 <a href="http://www.t2000-usa.com/" title="URI: &lt;http://www.t2000-usa.com/>">Clip! version 1.5</a>,
2519 when editing source
2520 files.
2521 </p>
2522 <p xml:lang="ja" class="t-l-ja">
2523 $BCx<T$ON>(B sgml-mode $B$r(B Emacs $B$G;H$C$F$$$F!">&MQ8!>Z%(%G%#%?!<(B
2524 <a href="http://www.t2000-usa.com/" title="URI: &lt;http://www.t2000-usa.com/>">Clip! version 1.5</a>
2525 $B$r8;%U%!%$%k$rJT=8$9$k$N$K;H$C$F$$$^$9!#(B
2526 </p>
2527 </div>
2528 </div>
2529 <div class="rfc-section" id="rfc.section.3.1.1">
2530 <div class="t-pair t-heading">
2531 <h3 xml:lang="en" class="t-l-en">3.1.1. Checking</h3>
2532 <h3 xml:lang="ja" class="t-l-ja">3.1.1.
2533 $B3NG'(B</h3>
2534 </div>
2535 <div class="rfc-t" id="rfc.section.3.1.1.p.1">
2536 <div class="t-pair">
2537 <p xml:lang="en" class="t-l-en">
2538 If your editor doesn't validate,
2539 then you should run a program to validate the source file.
2540 </p>
2541 <p xml:lang="ja" class="t-l-ja">
2542 $B$*;H$$$N%(%G%#%?!<$,8!>Z$7$J$$$J$i!"8;%U%!%$%k$r8!>Z$9$k$N$K%W%m%0%i%`$rF0$+$9I,MW$,$"$j$^$9!#(B
2543 </p>
2544 </div>
2545 </div>
2546 <div class="rfc-t" id="rfc.section.3.1.1.p.2">
2547 <div class="t-pair">
2548 <p xml:lang="en" class="t-l-en">
2549 The author uses
2550 <a href="http://www.alphaworks.ibm.com/formula/xml/" title="URI: &lt;http://www.alphaworks.ibm.com/formula/xml/>">the
2551 AlphaWorks XML parser</a> for this purpose.
2552 It requires that your system have a Java virtual machine.
2553 In addition to Java,
2554 there are validating parsers written in C, Perl, Python, and Tcl.
2555 </p>
2556 <p xml:lang="ja" class="t-l-ja">
2557 $BCx<T$O(B
2558 <a href="http://www.alphaworks.ibm.com/formula/xml/" title="URI: &lt;http://www.alphaworks.ibm.com/formula/xml/>">the
2559 AlphaWorks XML parser</a> $B$r$3$NL\E*$K;H$C$F$$$^$9!#$3$l$K$O$*;H$$$N7OE}$K(B
2560 Java $B2>A[5!3#$,I,MW$G$9!#(B Java $B$K2C$(!"(B C, Perl, Python, Tcl
2561 $B$G=q$+$l$?8!>Z2r@O4o$,$"$j$^$9!#(B
2562 </p>
2563 </div>
2564 </div>
2565 </div>
2566 </div>
2567 <div class="rfc-section" id="rfc.section.3.2">
2568 <div class="t-pair t-heading" id="xml2rfc">
2569 <h2 xml:lang="en" class="t-l-en">3.2. Converting to Text Format</h2>
2570 <h2 xml:lang="ja" class="t-l-ja">3.2.
2571 text $B7A<0$KJQ49$9$k(B</h2>
2572 </div>
2573 <div class="rfc-t" id="rfc.section.3.2.p.1">
2574 <div class="t-pair">
2575 <p xml:lang="en" class="t-l-en">
2576 The author has written
2577 <a href="http://memory.palace.org/authoring/" title="URI: &lt;http://memory.palace.org/authoring/>">the xml2rfc tool</a>,
2578 which reads the source file and produces both a text and HTML version
2579 of the document.
2580 (This memo was produced using the xml2rfc tool.)
2581 Note that xml2rfc isn't a validating tool,
2582 so it's a good idea to use either a validating editor or run a stand-alone
2583 validating parser prior to using the tool.
2584 </p>
2585 <p xml:lang="ja" class="t-l-ja">
2586 $BCx<T$O8;%U%!%$%k$rFI$s$GJ8=q$N(B text $BHG$H(B HTML $BHG$NN><T$r@8@.$9$k(B
2587 <a href="http://memory.palace.org/authoring/" title="URI: &lt;http://memory.palace.org/authoring/>">xml2rfc
2588 $B9)6q(B</a>$B$r=q$-$^$7$?!#(B ($B$3$N%a%b$O(B xml2rfc $B9)6q$r;H$C$F@8@.$7$^$7$?!#(B)
2589 $B$J$*!"(B xml2rfc $B$O8!>Z9)6q$G$O$J$$$N$G!"8!>Z%(%G%#%?!<$dC1FH8!>Z2r@O4o$r$3$N9)6q$NA0$K;H$&$N$,NI$$$G$7$g$&!#(B
2590 </p>
2591 </div>
2592 </div>
2593 </div>
2594 <div class="rfc-section" id="rfc.section.3.3">
2595 <div class="t-pair t-heading">
2596 <h2 xml:lang="en" class="t-l-en">3.3. Converting to HTML Format</h2>
2597 <h2 xml:lang="ja" class="t-l-ja">3.3.
2598 HTML $B7A<0$KJQ49$9$k(B</h2>
2599 </div>
2600 <div class="rfc-t" id="rfc.section.3.3.p.1">
2601 <div class="t-pair">
2602 <p xml:lang="en" class="t-l-en">
2603 The XML Style Language (XSL) is used to describe transformations
2604 from the source file into some other structured file.
2605 So,
2606 ideally you should use an XSL-capable formatter to convert an XML source
2607 file to HTML.
2608 </p>
2609 <p xml:lang="ja" class="t-l-ja">
2610 XML $B%9%?%$%k8@8l(B (XSL) $B$r8;%U%!%$%k$+$iB>$N9=B$$N%U%!%$%k$KJQ7A$9$k$N$r5-=R$9$k$N$K;HMQ=PMh$^$9!#$G$9$+$i!"M}A[E*$K$O(B XSL $B$,;H$($k(B formatter
2611 $B$r;H$C$F(B XML $B8;%U%!%$%k$r(B HTML $B$KJQ49$9$k$Y$-$G$7$g$&!#(B
2612 </p>
2613 </div>
2614 </div>
2615 <div class="rfc-t" id="rfc.section.3.3.p.2">
2616 <div class="t-pair">
2617 <p xml:lang="en" class="t-l-en">
2618 However,
2619 as of this writing XSL is still in considerable flux.
2620 (Hence,
2621 no reference was included in this memo,
2622 as by the time you read this section,
2623 the reference would be outdated.)
2624 So,
2625 in the interim,
2626 the author uses the xml2rfc tool for this purpose,
2627 even though this tool doesn't provide much flexibility in its HTML layout.
2628 </p>
2629 <p xml:lang="ja" class="t-l-ja">
2630 $B$7$+$7$J$,$i!"$3$N(B XSL $B=q$-$O$^$@N.F0E*$H9M$($i$l$^$9!#(B
2631 ($B$=$l8N!"$3$N%a%b$K$O;2>H$O4^$a$^$;$s$G$7$?!#FI<T$,$3$N@a$rFI$`;~$K$O;2>H$O$b$&8E$$$b$N$K$J$C$F$$$k$G$7$g$&$+$i!#(B)
2632 $B$G$9$,!"$=$N4V!"Cx<T$O$3$NL\E*$K(B xml2rfc $B9)6q$r;H$$$^$9!#(B
2633 $B$3$N9)6q$O$=$l$[$I(B HTML $BG[CV$K=@Fp@-$r;}$C$F$$$J$$$N$G$9$,!#(B
2634 </p>
2635 </div>
2636 </div>
2637 <ins class="t-note t-l-ja" xml:lang="ja">
2638 <span class="t-note-title">$BLuCm(B:</span>
2639 <p class="rfc-t" id="rfc.section.3.3.p.1">rfc2629.xslt $B$O!"(B
2640 <a href="http://xml.resource.org/authoring/" title="URI: &lt;http://xml.resource.org/authoring/>">xml2rfc
2641 $B9)6q(B</a>$B$K4^$^$l$F$$$^$9!#$3$l$r;H$C$F9+$N(B XSLT formatter
2642 $B$G$b(B HTML $B$KJQ49=PMh$^$9!#(B</p>
2643 </ins>
2644 </div>
2645 <div class="rfc-section" id="rfc.section.3.4">
2646 <div class="t-pair t-heading">
2647 <h2 xml:lang="en" class="t-l-en">3.4. Viewing</h2>
2648 <h2 xml:lang="ja" class="t-l-ja">3.4.
2649 $BI=<((B</h2>
2650 </div>
2651 <div class="rfc-t" id="rfc.section.3.4.p.1">
2652 <div class="t-pair">
2653 <p xml:lang="en" class="t-l-en">
2654 Browsers that support either XSL or Cascading Style Sheets (CSS)
2655 are able to view the source file directly.
2656 </p>
2657 <p xml:lang="ja" class="t-l-ja">
2658 XSL $B$+(B Cascading Style Sheets (CSS)
2659 $B$KBP1~$7$?1\Mw4o$r8;%U%!%$%k$rD>@\8+$k$N$K;HMQ=PMh$^$9!#(B
2660 </p>
2661 </div>
2662 </div>
2663 <div class="rfc-t" id="rfc.section.3.4.p.2">
2664 <div class="t-pair">
2665 <p xml:lang="en" class="t-l-en">
2666 At present,
2667 the author doesn't use any of these browsers,
2668 instead converting source files to either text or HTML.
2669 </p>
2670 <p xml:lang="ja" class="t-l-ja">
2671 $B8=;~E@$G!"Cx<T$O$=$NMM$J1\Mw4o$r;H$C$F$*$i$:!"Be$o$j$K8;%U%!%$%k$r(B
2672 text $B$+(B HTML $B$KJQ49$7$F$$$^$9!#(B
2673 </p>
2674 </div>
2675 </div>
2676 </div>
2677 <div class="rfc-section" id="rfc.section.3.5">
2678 <div class="t-pair t-heading">
2679 <h2 xml:lang="en" class="t-l-en">3.5. Searching</h2>
2680 <h2 xml:lang="ja" class="t-l-ja">3.5.
2681 $B8!:w(B</h2>
2682 </div>
2683 <div class="rfc-t" id="rfc.section.3.5.p.1">
2684 <div class="t-pair">
2685 <p xml:lang="en" class="t-l-en">
2686 As with text editors,
2687 any text-oriented search tool (e.g., grep) can be used on the source file.
2688 However,
2689 there are search tools available that understand structured source.
2690 </p>
2691 <p xml:lang="ja" class="t-l-ja">
2692 text $B%(%G%#%?!<$H6&$K!"$I$s$J(B text $B;X8~8!:w9)6q(B ($BNc(B grep)
2693 $B$r$b8;%U%!%$%k$KBP$7$F;H$&$3$H$,=PMh$^$9!#$7$+$7!"9=B$2=$5$l$?8;$rM}2r$9$k8!:wF;6q$b$"$j$^$9!#(B
2694 </p>
2695 </div>
2696 </div>
2697 <div class="rfc-figure">
2698 <span class="rfc-figure-id" id="rfc.figure.u.33">&#x00A0;</span>
2699 <div class="rfc-preamble">
2700 <div class="t-pair">
2701 <p xml:lang="en" class="t-l-en">
2702 The author uses
2703 <a href="http://www.cs.helsinki.fi/~jjaakkol/sgrep.html" title="URI: &lt;http://www.cs.helsinki.fi/~jjaakkol/sgrep.html>">sgrep
2704 version 1.9</a>
2705 for this purpose,
2706 e.g.
2707 </p>
2708 <p xml:lang="ja" class="t-l-ja">
2709 $BCx<T$O(B
2710 <a href="http://www.cs.helsinki.fi/~jjaakkol/sgrep.html" title="URI: &lt;http://www.cs.helsinki.fi/~jjaakkol/sgrep.html>">sgrep
2711 version 1.9</a> $B$r$3$NL\E*$G<!$NMM$K;H$C$F$$$^$9!#(B
2712 </p>
2713 </div>
2714 </div>
2715 <pre class="rfc-artwork" xml:space="preserve">
2716 sgrep -g xml 'ELEMENTS("title") not in ELEMENTS("back")' \
2717 writing-rfcs.xml
2718 </pre>
2719 <div class="rfc-postamble">
2720 <div class="t-pair">
2721 <p xml:lang="en" class="t-l-en">
2722 which extracts the title element from the source file.
2723 </p>
2724 <p xml:lang="ja" class="t-l-ja">
2725 $B$3$l$O(B title $BMWAG$r8;%U%!%$%k$+$i<h$j=P$7$^$9!#(B
2726 </p>
2727 </div>
2728 </div>
2729 </div>
2730 </div>
2731 </div>
2732 <div class="rfc-section" id="rfc.section.4">
2733 <div class="t-pair t-heading">
2734 <h1 xml:lang="en" class="t-l-en">4. Security Considerations</h1>
2735 <h1 xml:lang="ja" class="t-l-ja">4.
2736 $B0BA4@-$K4X$7$F(B</h1>
2737 </div>
2738 <div class="rfc-figure">
2739 <span class="rfc-figure-id" id="rfc.figure.u.34">&#x00A0;</span>
2740 <div class="rfc-preamble">
2741 <div class="t-pair">
2742 <p xml:lang="en" class="t-l-en">
2743 This memo raises no security issues;
2744 however,
2745 according to <span class="rfc-xref">
2746 <a href="#refs.RFC2223" title="Instructions to RFC Authors">[2]</a>
2747 </span>,
2748 your document should contain a section near the end that discusses the
2749 security considerations of the protocol or procedures that are the
2750 main topic of your document, e.g.,
2751 </p>
2752 <p xml:lang="ja" class="t-l-ja">
2753 $B$3$N%a%b$O0BA4@-LdBj$r5/$3$7$^$;$s!#$7$+$7!"(B <a href="#refs.RFC2223" title="RFC $BCx<T$N<j0z$-(B">[2]</a>
2754 $B$K$h$k$H!"J8=q$O=*$o$j6a$/$K!"J8=q$N<gBj$G$"$k%W%m%H%3%k$d=hM}$N0BA4@-$K4X$7$F$N5DO@$N@a$r@_$1$k$Y$-$G$9!#Nc(B:
2755 </p>
2756 </div>
2757 </div>
2758
2759 <div class="t-pair">
2760 <p xml:lang="en" class="t-l-en">
2761 <pre class="rfc-artwork" xml:space="preserve">
2762 &lt;middle&gt;
2763 ...
2764 &lt;section title="Security Considerations"&gt;
2765 &lt;t&gt;This memo raises no security issues;
2766 however,
2767 according to &lt;xref target="refs.RFC2223" /&gt;,
2768 your document should contain a section near the end
2769 that discusses the security considerations of the
2770 protocol or procedures that are the main topic of your
2771 document.&lt;/t&gt;
2772 &lt;/section&gt;
2773 &lt;/middle&gt;
2774 </pre>
2775 </p>
2776 <p xml:lang="ja" class="t-l-ja">
2777 <pre class="rfc-artwork" xml:space="preserve">
2778 &lt;middle&gt;
2779 ...
2780 &lt;section title="$B0BA4@-$K4X$7$F(B"&gt;
2781 &lt;t&gt;$B$3$N%a%b$O0BA4@-LdBj$r5/$3$7$^$;$s!#$7$+$7!"(B
2782 &lt;xref target="refs.RFC2223" /&gt; $B$K$h$k$H!"(B
2783 $BJ8=q$O=*$o$j6a$/$K!"J8=q$N<gBj$G$"$k%W%m%H%3%k$d(B
2784 $B=hM}$N0BA4@-$K4X$7$F$N5DO@$N@a$r@_$1$k$Y$-$G$9!#(B&lt;/t&gt;
2785 &lt;/section&gt;
2786 &lt;/middle&gt;
2787 </pre>
2788 </p>
2789 </div>
2790
2791 </div>
2792 </div>
2793
2794 <div class="rfc-section" id="rfc.references.References">
2795 <div class="t-pair t-heading">
2796 <h1 xml:lang="en" class="t-l-en">References</h1>
2797 <h1 xml:lang="ja" class="t-l-ja">$B;29MJ88%(B</h1>
2798 </div>
2799 <dl>
2800 <dt id="XML">[1]</dt>
2801 <dd>$B!X(B<cite>
2802 <a href="http://www.w3.org/TR/1998/REC-xml-19980210" title="URI: &lt;http://www.w3.org/TR/1998/REC-xml-19980210>">Extensible Markup Language (XML) 1.0</a>
2803 </cite>$B!Y(B, W3C
2804 &#x00A0;XML
2805
2806 , <span class="t-pair">
2807 <span xml:lang="en" class="t-l-en">
2808 &#x00A0;February&#x00A0;
2809 1998.
2810 </span>, <span xml:lang="ja" class="t-l-ja">1998$BG/(B2$B7n!#(B
2811 </span>
2812 </span>
2813 </dd>
2814 <dt id="refs.RFC2223">[2]</dt>
2815 <dd>$B!X(B<cite>
2816 <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2223" title="URI: &lt;http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2223>">Instructions to RFC Authors</a>
2817 </cite>$B!Y(B, <span title="@fullname">Postel, J.</span>, <span title="@fullname">Reynolds, J.</span>, RFC
2818 &#x00A0;2223
2819
2820 , <span class="t-pair">
2821 <span xml:lang="en" class="t-l-en">
2822 &#x00A0;October&#x00A0;
2823 1997.
2824 </span>, <span xml:lang="ja" class="t-l-ja">1997$BG/(B10$B7n!#(B
2825 </span>
2826 </span>
2827 </dd>
2828 <dt id="refs.RFC2026">[3]</dt>
2829 <dd>$B!X(B<cite>
2830 <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026" title="URI: &lt;http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2026>">The Internet Standards Process $B!=!=(B Revision 3</a>
2831 </cite>$B!Y(B, <span title="@fullname">Bradner, S.O.</span>, RFC
2832 &#x00A0;2026, BCP
2833 &#x00A0;9
2834
2835 , <span class="t-pair">
2836 <span xml:lang="en" class="t-l-en">
2837 &#x00A0;October&#x00A0;
2838 1996.
2839 </span>, <span xml:lang="ja" class="t-l-ja">1996$BG/(B10$B7n!#(B
2840 </span>
2841 </span>
2842 </dd>
2843 <dt id="URI">[4]</dt>
2844 <dd>$B!X(B<cite>
2845 <a href="http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2396" title="URI: &lt;http://suika.fam.cx/uri-res/N2L?urn:ietf:rfc:2396>">Uniform Resource Identifiers (URI): Generic Syntax</a>
2846 </cite>$B!Y(B, <span title="@fullname">Berners-Lee, T.</span>, <span title="@fullname">Fielding, R.T.</span>, <span title="@fullname">Masinter, L.</span>, RFC
2847 &#x00A0;2396
2848
2849 , <span class="t-pair">
2850 <span xml:lang="en" class="t-l-en">
2851 &#x00A0;August&#x00A0;
2852 1998.
2853 </span>, <span xml:lang="ja" class="t-l-ja">1998$BG/(B8$B7n!#(B
2854 </span>
2855 </span>
2856 </dd>
2857 </dl>
2858 </div>
2859 <div class="rfc-section" id="rfc.section.A">
2860 <div class="t-pair t-heading" id="rfc">
2861 <h1 xml:lang="en" class="t-l-en">A. The rfc Element</h1>
2862 <h1 xml:lang="ja" class="t-l-ja">A.
2863 rfc $BMWAG(B</h1>
2864 </div>
2865 <div class="rfc-figure">
2866 <span class="rfc-figure-id" id="rfc.figure.u.35">&#x00A0;</span>
2867 <div class="rfc-preamble">
2868 <div class="t-pair">
2869 <p xml:lang="en" class="t-l-en">
2870 The "&lt;rfc&gt;" tag at the beginning of the file,
2871 with only <span class="rfc-xref">
2872 <a href="#ipr" title="">an "ipr" attribute</a>
2873 </span>,
2874 produces an Internet-Draft.
2875 However,
2876 when other attributes are added to this tag by the RFC editor,
2877 an RFC is produced, e.g.,
2878 </p>
2879 <p xml:lang="ja" class="t-l-ja">
2880 $B%U%!%$%k$N$O$8$a$N(B "&lt;rfc&gt;" $B%?%0$O!"(B
2881 <a href="#ipr" title="">"ipr" $BB0@-(B</a>$B$@$1$r;}$D$H!"(B Internet-Draft
2882 $B$r@8@.$7$^$9!#$7$+$7!"$3$N%?%0$K(B RFC $BJT=8<T$K$h$jB>$NB0@-$,(B
2883 $BIU2C$5$l$k$H!"(B RFC $B$,@8@.$5$l$^$9!#(B
2884 </p>
2885 </div>
2886 </div>
2887 <pre class="rfc-artwork" xml:space="preserve">
2888 &lt;rfc number="2200"
2889 obsoletes="2000, 1920, 1880, 1800, ..."
2890 category="std"
2891 seriesNo="1"&gt;
2892 </pre>
2893 <div class="rfc-postamble">
2894 <div class="t-pair">
2895 <p xml:lang="en" class="t-l-en">
2896 At a minimum,
2897 the "number" attribute should be present.
2898 </p>
2899 <p xml:lang="ja" class="t-l-ja">
2900 $B>/$J$/$F$b!"(B "number" $BB0@-$,$"$k$Y$-$G$9!#(B
2901 </p>
2902 </div>
2903 </div>
2904 </div>
2905 <div class="rfc-t" id="rfc.section.A.p.2">
2906 <div class="t-pair">
2907 <p xml:lang="en" class="t-l-en">
2908 The other attributes are:
2909 </p>
2910 <p xml:lang="ja" class="t-l-ja">
2911 $B$3$NB>$NB0@-$O!"(B
2912 </p>
2913 </div>
2914
2915 <ul class="rfc-list-symbols text">
2916 <li>
2917 <div class="t-pair">
2918 <p xml:lang="en" class="t-l-en">
2919 "obsoletes",
2920 having a comma-separated list of RFC numbers,
2921 that the document obsoletes;
2922 </p>
2923 <p xml:lang="ja" class="t-l-ja">
2924 "obsoleted" $B$O!"$=$NJ8=q$,GQ;_$9$kFIE@(B (comma) $B6h@Z$j$N(B RFC $BHV9f$N0lMw$G$9!#(B
2925 </p>
2926 </div>
2927 </li>
2928 <li>
2929 <div class="t-pair">
2930 <p xml:lang="en" class="t-l-en">
2931 "updates",
2932 having a comma-separated list of RFC numbers,
2933 that the document updates;
2934 </p>
2935 <p xml:lang="ja" class="t-l-ja">
2936 "updates" $B$O!"$=$NJ8=q$,99?7$9$kFIE@(B (comma) $B6h@Z$j$N(B RFC $BHV9f$N0lMw$G$9!#(B
2937 </p>
2938 </div>
2939 </li>
2940 <li>
2941 <div class="t-pair">
2942 <p xml:lang="en" class="t-l-en">
2943 "category",
2944 having one of these values:
2945 </p>
2946 <p xml:lang="ja" class="t-l-ja">
2947 "category" $B$O!"<!$NCM$N$$$:$l$+$r;}$A$^$9!#(B
2948 </p>
2949 </div>
2950
2951 <ol class="rfc-list-numbers text">
2952 <li>
2953 <div class="t-pair">
2954 <p xml:lang="en" class="t-l-en">"std", for a Standards-Track document;</p>
2955 <p xml:lang="ja" class="t-l-ja">"std" $B$OI8=`2=2aDxJ8=qMQ(B</p>
2956 </div>
2957 </li>
2958 <li>
2959 <div class="t-pair">
2960 <p xml:lang="en" class="t-l-en">"bcp", for a Best Current Practices document;</p>
2961 <p xml:lang="ja" class="t-l-ja">"bcp" $B$O8=>u:GA11?MQJ8=qMQ(B</p>
2962 </div>
2963 </li>
2964 <li>
2965 <div class="t-pair">
2966 <p xml:lang="en" class="t-l-en">"exp", for an Experimental Protocol document;</p>
2967 <p xml:lang="ja" class="t-l-ja">"exp" $B$O<B83%W%m%H%3%kJ8=qMQ(B</p>
2968 </div>
2969 </li>
2970 <li>
2971 <div class="t-pair">
2972 <p xml:lang="en" class="t-l-en">"historic", for a historic document; or,</p>
2973 <p xml:lang="ja" class="t-l-ja">"exp" $B$ONr;KE*J8=qMQ(B</p>
2974 </div>
2975 </li>
2976 <li>
2977 <div class="t-pair">
2978 <p xml:lang="en" class="t-l-en">"info", the default, for an Informational document.</p>
2979 <p xml:lang="ja" class="t-l-ja">"info" $B$O4{DjCM$G;29MJ8=qMQ(B</p>
2980 </div>
2981 </li>
2982 </ol>
2983 </li>
2984 <li>
2985 <div class="t-pair">
2986 <p xml:lang="en" class="t-l-en">
2987 "seriesNo",
2988 having the corresponding number in the STD (std), BCP (bcp), or FYI (info)
2989 series.
2990 </p>
2991 <p xml:lang="ja" class="t-l-ja">
2992 "seriesNo" $B$O!"(B STD (std), BCP (bcp), FYI (info) $B3F7ONs$G$NBP1~HV9f$rCM$K;}$A$^$9!#(B
2993 </p>
2994 </div>
2995 </li>
2996 </ul>
2997 </div>
2998 <div class="rfc-t" id="rfc.section.A.p.3">
2999 <div class="t-pair">
3000 <p xml:lang="en" class="t-l-en">
3001 Finally,
3002 a special entity, "&amp;rfc.number;", is available.
3003 Authors preparing an RFC should use this entity whenever they want to
3004 reference the number of the RFC within the document itself.
3005 In printed versions of the document,
3006 the appropriate substitution (or "XXXX") will occur.
3007 </p>
3008 <p xml:lang="ja" class="t-l-ja">
3009 $B:G8e$K!"FCJL$J<BBN(B "&amp;rfc.number;" $B$,;H$($^$9!#(B
3010 RFC $B$rMQ0U$9$kCx<T$O$3$N<BBN$rJ8=q<+?H$N(B
3011 RFC $BHV9f$r;2>H$7$?$$;~$K;H$&$Y$-$G$9!#J8=q$N0u:~HG$G$O!"E,@Z$JBeBX(B
3012 ($B$^$?$O(B "XXXX") $B$r;H$$$^$9!#(B
3013 </p>
3014 </div>
3015 <ins class="t-note t-l-ja" xml:lang="ja">
3016 (<span class="t-note-title">$BLuCm(B:</span>
3017 <div class="rfc-figure">
3018 <span class="rfc-figure-id" id="rfc.figure.u.36">&#x00A0;</span>
3019 <div class="rfc-preamble">$B<B:]$K;H$&;~$O!"(B</div>
3020 <pre class="rfc-artwork" xml:space="preserve">&lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd" [&lt;!ENTITY rfc.number "1234"&gt;]&gt;</pre>
3021 <div class="rfc-postamble">$B$N$h$&$K!"J8=q7?@k8@$GEv3:(B RFC
3022 $BHV9f$r<($9$3$H$K$J$k$G$7$g$&!#(B</div>
3023 </div>
3024 )
3025 </ins>
3026 </div>
3027 </div>
3028 <div class="rfc-section" id="rfc.section.B">
3029 <div id="rfc.dtd">
3030 <h1>B. The RFC DTD</h1>
3031 </div>
3032
3033 <ins class="t-note t-l-ja" xml:lang="ja">
3034 <span class="t-note-title">$BLuCm(B:</span>
3035 <p class="rfc-t" id="rfc.section.B.p.1">$B$3$N(B DTD $B$N%U%!%$%k(B rfc2629.dtd $B$O!"(B
3036 <a href="http://xml.resource.org/authoring/" title="URI: &lt;http://xml.resource.org/authoring/>">xml2rfc
3037 $B9)6q(B</a>$B$NCf$K$b4^$^$l$F$$$^$9!#(B</p>
3038 </ins>
3039
3040 <div class="rfc-figure">
3041 <span class="rfc-figure-id" id="rfc.figure.u.37">&#x00A0;</span>
3042
3043 <div class="t-pair">
3044 <p xml:lang="en" class="t-l-en">
3045 <pre class="rfc-artwork" xml:space="preserve">
3046 &lt;!--
3047 DTD for the RFC document series, draft of 99-01-30
3048 --&gt;
3049
3050
3051 &lt;!--
3052 Contents
3053
3054 DTD data types
3055
3056 The top-level
3057
3058 Front matter
3059
3060 The Body
3061
3062 Back matter
3063 --&gt;
3064
3065
3066 &lt;!--
3067 DTD data types:
3068
3069 entity description
3070 ====== ===============================================
3071 NUMBER [0-9]+
3072 NUMBERS a comma-separated list of NUMBER
3073
3074 DAY the day of the month, e.g., "1"
3075 MONTH the month of the year, e.g., "January"
3076 YEAR a four-digit year, e.g., "1999"
3077
3078 URI e.g., "http://invisible.net/"
3079
3080 ATEXT/CTEXT printable ASCII text (no line-terminators)
3081
3082 TEXT character data
3083 --&gt;
3084
3085
3086 &lt;!ENTITY % NUMBER "CDATA"&gt;
3087 &lt;!ENTITY % NUMBERS "CDATA"&gt;
3088
3089 &lt;!ENTITY % DAY "CDATA"&gt;
3090 &lt;!ENTITY % MONTH "CDATA"&gt;
3091 &lt;!ENTITY % YEAR "CDATA"&gt;
3092
3093 &lt;!ENTITY % URI "CDATA"&gt;
3094
3095 &lt;!ENTITY % ATEXT "CDATA"&gt;
3096 &lt;!ENTITY % CTEXT "#PCDATA"&gt;
3097
3098 &lt;!ENTITY % TEXT "#PCDATA"&gt;
3099
3100 &lt;!ENTITY rfc.number "2629"&gt;
3101
3102
3103 &lt;!--
3104 The top-level
3105 --&gt;
3106
3107
3108 &lt;!--
3109 attributes for the "rfc" element are supplied by the RFC
3110 editor. when preparing drafts, authors should leave them blank.
3111
3112 the "seriesNo" attribute is used if the category is, e.g., BCP.
3113 --&gt;
3114 &lt;!ELEMENT rfc (front,middle,back?)&gt;
3115 &lt;!ATTLIST rfc
3116 number %NUMBER; #IMPLIED
3117 obsoletes %NUMBERS; ""
3118 updates %NUMBERS; ""
3119 category (std|bcp|info|exp|historic)
3120 "info"
3121 seriesNo %NUMBER; #IMPLIED
3122 ipr (full2026|noDerivativeWorks2026|none)
3123 #IMPLIED
3124 docName %ATEXT; #IMPLIED&gt;
3125
3126 &lt;!--
3127 Front matter
3128 --&gt;
3129
3130
3131 &lt;!ELEMENT front (title,author+,date,area*,workgroup*,keyword*,
3132 abstract?,note*)&gt;
3133
3134 &lt;!-- the "abbrev" attribute is used for headers, etc. --&gt;
3135 &lt;!ELEMENT title (%CTEXT;)&gt;
3136 &lt;!ATTLIST title
3137 abbrev %ATEXT; #IMPLIED&gt;
3138
3139 &lt;!ELEMENT author (organization,address?)&gt;
3140 &lt;!ATTLIST author
3141 initials %ATEXT; #IMPLIED
3142 surname %ATEXT; #IMPLIED
3143 fullname %ATEXT; #IMPLIED&gt;
3144
3145 &lt;!ELEMENT organization
3146 (%CTEXT;)&gt;
3147 &lt;!ATTLIST organization
3148 abbrev %ATEXT; #IMPLIED&gt;
3149
3150 &lt;!ELEMENT address (postal?,phone?,facsimile?,email?,uri?)&gt;
3151
3152 &lt;!-- at most one of each the city, region, code, and country
3153 elements may be present --&gt;
3154 &lt;!ELEMENT postal (street+,(city|region|code|country)*)&gt;
3155 &lt;!ELEMENT street (%CTEXT;)&gt;
3156 &lt;!ELEMENT city (%CTEXT;)&gt;
3157 &lt;!ELEMENT region (%CTEXT;)&gt;
3158 &lt;!ELEMENT code (%CTEXT;)&gt;
3159 &lt;!ELEMENT country (%CTEXT;)&gt;
3160 &lt;!ELEMENT phone (%CTEXT;)&gt;
3161 &lt;!ELEMENT facsimile (%CTEXT;)&gt;
3162 &lt;!ELEMENT email (%CTEXT;)&gt;
3163 &lt;!ELEMENT uri (%CTEXT;)&gt;
3164
3165 &lt;!ELEMENT date EMPTY&gt;
3166 &lt;!ATTLIST date
3167 day %DAY; #IMPLIED
3168 month %MONTH; #REQUIRED
3169 year %YEAR; #REQUIRED&gt;
3170
3171 &lt;!-- meta-data... --&gt;
3172 &lt;!ELEMENT area (%CTEXT;)&gt;
3173 &lt;!ELEMENT workgroup (%CTEXT;)&gt;
3174 &lt;!ELEMENT keyword (%CTEXT;)&gt;
3175
3176 &lt;!ELEMENT abstract (t)+&gt;
3177 &lt;!ELEMENT note (t)+&gt;
3178 &lt;!ATTLIST note
3179 title %ATEXT; #REQUIRED&gt;
3180
3181
3182 &lt;!--
3183 The body
3184 --&gt;
3185
3186
3187 &lt;!ELEMENT middle (section)+&gt;
3188
3189 &lt;!ELEMENT section (t|figure|section)*&gt;
3190 &lt;!ATTLIST section
3191 anchor ID #IMPLIED
3192 title %ATEXT; #REQUIRED&gt;
3193
3194 &lt;!ELEMENT t (%TEXT;|list|figure|xref|eref|iref|vspace)*&gt;
3195 &lt;!ATTLIST t
3196 hangText %ATEXT; #IMPLIED&gt;
3197
3198 &lt;!-- the value of the style attribute is inherited from the closest
3199 parent --&gt;
3200 &lt;!ELEMENT list (t+)&gt;
3201 &lt;!ATTLIST list
3202 style (numbers|symbols|hanging|empty)
3203 "empty"&gt;
3204
3205 &lt;!ELEMENT xref (%CTEXT;)&gt;
3206 &lt;!ATTLIST xref
3207 target IDREF #REQUIRED
3208 pageno (true|false) "false"&gt;
3209
3210 &lt;!ELEMENT eref (%CTEXT;)&gt;
3211 &lt;!ATTLIST eref
3212 target %URI; #REQUIRED&gt;
3213
3214 &lt;!ELEMENT iref EMPTY&gt;
3215 &lt;!ATTLIST iref
3216 item %ATEXT; #REQUIRED
3217 subitem %ATEXT; ""&gt;
3218
3219 &lt;!ELEMENT vspace EMPTY&gt;
3220 &lt;!ATTLIST vspace
3221 blankLines %NUMBER; "0"&gt;
3222
3223 &lt;!ELEMENT figure (preamble?,artwork,postamble?)&gt;
3224 &lt;!ATTLIST figure
3225 anchor ID #IMPLIED
3226 title %ATEXT; ""&gt;
3227
3228 &lt;!ELEMENT preamble (%TEXT;|xref|eref|iref)*&gt;
3229 &lt;!ELEMENT artwork (%TEXT;)*&gt;
3230 &lt;!ATTLIST artwork
3231 xml:space (default|preserve) "preserve"&gt;
3232 &lt;!ELEMENT postamble (%TEXT;|xref|eref|iref)*&gt;
3233
3234
3235 &lt;!--
3236 Back matter
3237 --&gt;
3238
3239
3240 &lt;!-- sections, if present, are appendices --&gt;
3241 &lt;!ELEMENT back (references?,section*)&gt;
3242
3243 &lt;!ELEMENT references (reference+)&gt;
3244 &lt;!ELEMENT reference (front,seriesInfo*)&gt;
3245 &lt;!ATTLIST reference
3246 anchor ID #IMPLIED
3247 target %URI; #IMPLIED&gt;
3248 &lt;!ELEMENT seriesInfo EMPTY&gt;
3249 &lt;!ATTLIST seriesInfo
3250 name %ATEXT; #REQUIRED
3251 value %ATEXT; #REQUIRED&gt;
3252 </pre>
3253 </p>
3254 <p xml:lang="ja" class="t-l-ja">
3255 <pre class="rfc-artwork" xml:space="preserve">
3256 &lt;!--
3257 RFC $BJ8=q7ONsMQ(B DTD, 99-01-30 $B$N860F(B ($B$NCm<aItJ,OBLu(B)
3258 --&gt;
3259
3260
3261 &lt;!--
3262 $BFbMF(B
3263
3264 DTD $B%G!<%?7?(B
3265
3266 $B:G>e0L(B
3267
3268 Front matter
3269
3270 The Body
3271
3272 Back matter
3273 --&gt;
3274
3275
3276 &lt;!--
3277 DTD $B%G!<%?7?(B:
3278
3279 $B<BBN(B $B@bL@(B
3280 ====== ===============================================
3281 NUMBER [0-9]+
3282 NUMBERS $BFIE@(B(comma)$B6h@Z$j$N(B NUMBER
3283
3284 DAY $B7nCf$NF|!"Nc$($P(B "1"
3285 MONTH $BG/Cf$N7n!"Nc$($P(B "January" (1$B7n(B)
3286 YEAR 4$B7eG/9f!"Nc$($P(B "1999"
3287
3288 URI $BNc(B "http://invisible.net/"
3289
3290 ATEXT/CTEXT $B0u;z2DG=(B ASCII $BJ8;zNs(B ($B9T=*C<L5$7(B)
3291
3292 TEXT $BJ8;z%G!<%?(B
3293 --&gt;
3294
3295
3296 &lt;!ENTITY % NUMBER "CDATA"&gt;
3297 &lt;!ENTITY % NUMBERS "CDATA"&gt;
3298
3299 &lt;!ENTITY % DAY "CDATA"&gt;
3300 &lt;!ENTITY % MONTH "CDATA"&gt;
3301 &lt;!ENTITY % YEAR "CDATA"&gt;
3302
3303 &lt;!ENTITY % URI "CDATA"&gt;
3304
3305 &lt;!ENTITY % ATEXT "CDATA"&gt;
3306 &lt;!ENTITY % CTEXT "#PCDATA"&gt;
3307
3308 &lt;!ENTITY % TEXT "#PCDATA"&gt;
3309
3310 &lt;!ENTITY rfc.number "2629"&gt;
3311
3312
3313 &lt;!--
3314 $B:G>e0L(B
3315 --&gt;
3316
3317
3318 &lt;!--
3319 "rfc" $BMWAG$NB0@-$O(B RFC $BJT=8<T$K$h$jKd$a$i$l$^$9!#(B
3320 $B860F$rMQ0U$9$k:]$K$O!"Cx<T$O6uMs$K$7$F$*$/$Y$-$G$9!#(B
3321
3322 "seriesNo" $BB0@-$OJ,N`$,Nc$($P(B BCP $B$N;~$K;H$$$^$9!#(B
3323 --&gt;
3324 &lt;!ELEMENT rfc (front,middle,back?)&gt;
3325 &lt;!ATTLIST rfc
3326 number %NUMBER; #IMPLIED
3327 obsoletes %NUMBERS; ""
3328 updates %NUMBERS; ""
3329 category (std|bcp|info|exp|historic)
3330 "info"
3331 seriesNo %NUMBER; #IMPLIED
3332 ipr (full2026|noDerivativeWorks2026|none)
3333 #IMPLIED
3334 docName %ATEXT; #IMPLIED&gt;
3335
3336 &lt;!--
3337 Front matter
3338 --&gt;
3339
3340
3341 &lt;!ELEMENT front (title,author+,date,area*,workgroup*,keyword*,
3342 abstract?,note*)&gt;
3343
3344 &lt;!-- "abbrev" $BB0@-$OF,$H$+$K;H$$$^$9!#(B --&gt;
3345 &lt;!ELEMENT title (%CTEXT;)&gt;
3346 &lt;!ATTLIST title
3347 abbrev %ATEXT; #IMPLIED&gt;
3348
3349 &lt;!ELEMENT author (organization,address?)&gt;
3350 &lt;!ATTLIST author
3351 initials %ATEXT; #IMPLIED
3352 surname %ATEXT; #IMPLIED
3353 fullname %ATEXT; #IMPLIED&gt;
3354
3355 &lt;!ELEMENT organization
3356 (%CTEXT;)&gt;
3357 &lt;!ATTLIST organization
3358 abbrev %ATEXT; #IMPLIED&gt;
3359
3360 &lt;!ELEMENT address (postal?,phone?,facsimile?,email?,uri?)&gt;
3361
3362 &lt;!-- city, region, code, country $B3FMWAG$,$;$$$<$$(B1$B2s=P8=2DG=(B --&gt;
3363 &lt;!ELEMENT postal (street+,(city|region|code|country)*)&gt;
3364 &lt;!ELEMENT street (%CTEXT;)&gt;
3365 &lt;!ELEMENT city (%CTEXT;)&gt;
3366 &lt;!ELEMENT region (%CTEXT;)&gt;
3367 &lt;!ELEMENT code (%CTEXT;)&gt;
3368 &lt;!ELEMENT country (%CTEXT;)&gt;
3369 &lt;!ELEMENT phone (%CTEXT;)&gt;
3370 &lt;!ELEMENT facsimile (%CTEXT;)&gt;
3371 &lt;!ELEMENT email (%CTEXT;)&gt;
3372 &lt;!ELEMENT uri (%CTEXT;)&gt;
3373
3374 &lt;!ELEMENT date EMPTY&gt;
3375 &lt;!ATTLIST date
3376 day %DAY; #IMPLIED
3377 month %MONTH; #REQUIRED
3378 year %YEAR; #REQUIRED&gt;
3379
3380 &lt;!-- $B%a%?!&%G!<%?!&!&!&(B --&gt;
3381 &lt;!ELEMENT area (%CTEXT;)&gt;
3382 &lt;!ELEMENT workgroup (%CTEXT;)&gt;
3383 &lt;!ELEMENT keyword (%CTEXT;)&gt;
3384
3385 &lt;!ELEMENT abstract (t)+&gt;
3386 &lt;!ELEMENT note (t)+&gt;
3387 &lt;!ATTLIST note
3388 title %ATEXT; #REQUIRED&gt;
3389
3390
3391 &lt;!--
3392 $BK\BN(B
3393 --&gt;
3394
3395
3396 &lt;!ELEMENT middle (section)+&gt;
3397
3398 &lt;!ELEMENT section (t|figure|section)*&gt;
3399 &lt;!ATTLIST section
3400 anchor ID #IMPLIED
3401 title %ATEXT; #REQUIRED&gt;
3402
3403 &lt;!ELEMENT t (%TEXT;|list|figure|xref|eref|iref|vspace)*&gt;
3404 &lt;!ATTLIST t
3405 hangText %ATEXT; #IMPLIED&gt;
3406
3407 &lt;!-- style $BB0@-$NCM$OD>6a$N?F$+$i7Q>5$9$k(B --&gt;
3408 &lt;!ELEMENT list (t+)&gt;
3409 &lt;!ATTLIST list
3410 style (numbers|symbols|hanging|empty)
3411 "empty"&gt;
3412
3413 &lt;!ELEMENT xref (%CTEXT;)&gt;
3414 &lt;!ATTLIST xref
3415 target IDREF #REQUIRED
3416 pageno (true|false) "false"&gt;
3417
3418 &lt;!ELEMENT eref (%CTEXT;)&gt;
3419 &lt;!ATTLIST eref
3420 target %URI; #REQUIRED&gt;
3421
3422 &lt;!ELEMENT iref EMPTY&gt;
3423 &lt;!ATTLIST iref
3424 item %ATEXT; #REQUIRED
3425 subitem %ATEXT; ""&gt;
3426
3427 &lt;!ELEMENT vspace EMPTY&gt;
3428 &lt;!ATTLIST vspace
3429 blankLines %NUMBER; "0"&gt;
3430
3431 &lt;!ELEMENT figure (preamble?,artwork,postamble?)&gt;
3432 &lt;!ATTLIST figure
3433 anchor ID #IMPLIED
3434 title %ATEXT; ""&gt;
3435
3436 &lt;!ELEMENT preamble (%TEXT;|xref|eref|iref)*&gt;
3437 &lt;!ELEMENT artwork (%TEXT;)*&gt;
3438 &lt;!ATTLIST artwork
3439 xml:space (default|preserve) "preserve"&gt;
3440 &lt;!ELEMENT postamble (%TEXT;|xref|eref|iref)*&gt;
3441
3442
3443 &lt;!--
3444 Back matter
3445 --&gt;
3446
3447
3448 &lt;!-- sections $B$,$"$k>l9g!"$=$l$OImB0=q(B --&gt;
3449 &lt;!ELEMENT back (references?,section*)&gt;
3450
3451 &lt;!ELEMENT references (reference+)&gt;
3452 &lt;!ELEMENT reference (front,seriesInfo*)&gt;
3453 &lt;!ATTLIST reference
3454 anchor ID #IMPLIED
3455 target %URI; #IMPLIED&gt;
3456 &lt;!ELEMENT seriesInfo EMPTY&gt;
3457 &lt;!ATTLIST seriesInfo
3458 name %ATEXT; #REQUIRED
3459 value %ATEXT; #REQUIRED&gt;
3460 </pre>
3461 </p>
3462 </div>
3463
3464 </div>
3465 </div>
3466 <div class="rfc-section" id="rfc.section.C">
3467 <div class="t-pair t-heading">
3468 <h1 xml:lang="en" class="t-l-en">C. Acknowledgements</h1>
3469 <h1 xml:lang="ja" class="t-l-ja">C.
3470 $B<U<-(B</h1>
3471 </div>
3472 <div class="rfc-t" id="rfc.section.C.p.1">
3473 <div class="t-pair">
3474 <p xml:lang="en" class="t-l-en">The author gratefully acknowledges the contributions of:
3475 Alan Barrett,
3476 Brad Burdick,
3477 Brian Carpenter,
3478 Steve Deering,
3479 Patrik Faltstrom,
3480 Jim Gettys,
3481 Carl Malamud,
3482 Chris Newman,
3483 Kurt Starsinic,
3484 and,
3485 Frank Strauss.</p>
3486 <p xml:lang="ja" class="t-l-ja">$BCx<T$O<!$NJ}!9$N9W8%$K<U0U$rI=$7$^$9(B:
3487 Alan Barrett,
3488 Brad Burdick,
3489 Brian Carpenter,
3490 Steve Deering,
3491 Patrik Faltstrom,
3492 Jim Gettys,
3493 Carl Malamud,
3494 Chris Newman,
3495 Kurt Starsinic,
3496 Frank Strauss$B!#(B</p>
3497 </div>
3498 </div>
3499 </div>
3500 <div id="rfc-authors" class="rfc-section">
3501 <div id="rfc.authors" class="t-pair t-heading">
3502 <h1 xml:lang="en" class="t-l-en">Author's Address</h1>
3503 <h1 xml:lang="ja" class="t-l-ja">$BCx<T$NO"Mm@h(B</h1>
3504 </div>
3505 <ul class="rfc-author">
3506 <li class="rfc-author-fullname">Marshall T. Rose</li>
3507 <li class="rfc-organization">Invisible Worlds, Inc.</li>
3508 <li class="rfc-street">660 York Street</li>
3509 <li class="rfc-city">San Francisco</li>
3510 <li class="rfc-region">CA</li>
3511 <li class="rfc-code">94110</li>
3512 <li class="rfc-country">US</li>
3513 <li class="rfc-phone">$BEEOC(B: +1 415 695 3975</li>
3514 <li class="rfc-email">$BEE;R%a%$%k(B: &lt;<a href="mailto:mrose@not.invisible.net">mrose@not.invisible.net</a>&gt;</li>
3515 <li class="rfc-uri">URI: &lt;<a href="http://invisible.net/">http://invisible.net/</a>&gt;</li>
3516 </ul>
3517 </div>
3518 <div class="rfc-section" id="rfc.section.A">
3519 <div class="t-pair t-heading" id="rfc">
3520 <h1 xml:lang="en" class="t-l-en">A. The rfc Element</h1>
3521 <h1 xml:lang="ja" class="t-l-ja">A.
3522 rfc $BMWAG(B</h1>
3523 </div>
3524 <div class="rfc-figure">
3525 <span class="rfc-figure-id" id="rfc.figure.u.35">&#x00A0;</span>
3526 <div class="rfc-preamble">
3527 <div class="t-pair">
3528 <p xml:lang="en" class="t-l-en">
3529 The "&lt;rfc&gt;" tag at the beginning of the file,
3530 with only <span class="rfc-xref">
3531 <a href="#ipr" title="">an "ipr" attribute</a>
3532 </span>,
3533 produces an Internet-Draft.
3534 However,
3535 when other attributes are added to this tag by the RFC editor,
3536 an RFC is produced, e.g.,
3537 </p>
3538 <p xml:lang="ja" class="t-l-ja">
3539 $B%U%!%$%k$N$O$8$a$N(B "&lt;rfc&gt;" $B%?%0$O!"(B
3540 <a href="#ipr" title="">"ipr" $BB0@-(B</a>$B$@$1$r;}$D$H!"(B Internet-Draft
3541 $B$r@8@.$7$^$9!#$7$+$7!"$3$N%?%0$K(B RFC $BJT=8<T$K$h$jB>$NB0@-$,(B
3542 $BIU2C$5$l$k$H!"(B RFC $B$,@8@.$5$l$^$9!#(B
3543 </p>
3544 </div>
3545 </div>
3546 <pre class="rfc-artwork" xml:space="preserve">
3547 &lt;rfc number="2200"
3548 obsoletes="2000, 1920, 1880, 1800, ..."
3549 category="std"
3550 seriesNo="1"&gt;
3551 </pre>
3552 <div class="rfc-postamble">
3553 <div class="t-pair">
3554 <p xml:lang="en" class="t-l-en">
3555 At a minimum,
3556 the "number" attribute should be present.
3557 </p>
3558 <p xml:lang="ja" class="t-l-ja">
3559 $B>/$J$/$F$b!"(B "number" $BB0@-$,$"$k$Y$-$G$9!#(B
3560 </p>
3561 </div>
3562 </div>
3563 </div>
3564 <div class="rfc-t" id="rfc.section.A.p.2">
3565 <div class="t-pair">
3566 <p xml:lang="en" class="t-l-en">
3567 The other attributes are:
3568 </p>
3569 <p xml:lang="ja" class="t-l-ja">
3570 $B$3$NB>$NB0@-$O!"(B
3571 </p>
3572 </div>
3573
3574 <ul class="rfc-list-symbols text">
3575 <li>
3576 <div class="t-pair">
3577 <p xml:lang="en" class="t-l-en">
3578 "obsoletes",
3579 having a comma-separated list of RFC numbers,
3580 that the document obsoletes;
3581 </p>
3582 <p xml:lang="ja" class="t-l-ja">
3583 "obsoleted" $B$O!"$=$NJ8=q$,GQ;_$9$kFIE@(B (comma) $B6h@Z$j$N(B RFC $BHV9f$N0lMw$G$9!#(B
3584 </p>
3585 </div>
3586 </li>
3587 <li>
3588 <div class="t-pair">
3589 <p xml:lang="en" class="t-l-en">
3590 "updates",
3591 having a comma-separated list of RFC numbers,
3592 that the document updates;
3593 </p>
3594 <p xml:lang="ja" class="t-l-ja">
3595 "updates" $B$O!"$=$NJ8=q$,99?7$9$kFIE@(B (comma) $B6h@Z$j$N(B RFC $BHV9f$N0lMw$G$9!#(B
3596 </p>
3597 </div>
3598 </li>
3599 <li>
3600 <div class="t-pair">
3601 <p xml:lang="en" class="t-l-en">
3602 "category",
3603 having one of these values:
3604 </p>
3605 <p xml:lang="ja" class="t-l-ja">
3606 "category" $B$O!"<!$NCM$N$$$:$l$+$r;}$A$^$9!#(B
3607 </p>
3608 </div>
3609
3610 <ol class="rfc-list-numbers text">
3611 <li>
3612 <div class="t-pair">
3613 <p xml:lang="en" class="t-l-en">"std", for a Standards-Track document;</p>
3614 <p xml:lang="ja" class="t-l-ja">"std" $B$OI8=`2=2aDxJ8=qMQ(B</p>
3615 </div>
3616 </li>
3617 <li>
3618 <div class="t-pair">
3619 <p xml:lang="en" class="t-l-en">"bcp", for a Best Current Practices document;</p>
3620 <p xml:lang="ja" class="t-l-ja">"bcp" $B$O8=>u:GA11?MQJ8=qMQ(B</p>
3621 </div>
3622 </li>
3623 <li>
3624 <div class="t-pair">
3625 <p xml:lang="en" class="t-l-en">"exp", for an Experimental Protocol document;</p>
3626 <p xml:lang="ja" class="t-l-ja">"exp" $B$O<B83%W%m%H%3%kJ8=qMQ(B</p>
3627 </div>
3628 </li>
3629 <li>
3630 <div class="t-pair">
3631 <p xml:lang="en" class="t-l-en">"historic", for a historic document; or,</p>
3632 <p xml:lang="ja" class="t-l-ja">"exp" $B$ONr;KE*J8=qMQ(B</p>
3633 </div>
3634 </li>
3635 <li>
3636 <div class="t-pair">
3637 <p xml:lang="en" class="t-l-en">"info", the default, for an Informational document.</p>
3638 <p xml:lang="ja" class="t-l-ja">"info" $B$O4{DjCM$G;29MJ8=qMQ(B</p>
3639 </div>
3640 </li>
3641 </ol>
3642 </li>
3643 <li>
3644 <div class="t-pair">
3645 <p xml:lang="en" class="t-l-en">
3646 "seriesNo",
3647 having the corresponding number in the STD (std), BCP (bcp), or FYI (info)
3648 series.
3649 </p>
3650 <p xml:lang="ja" class="t-l-ja">
3651 "seriesNo" $B$O!"(B STD (std), BCP (bcp), FYI (info) $B3F7ONs$G$NBP1~HV9f$rCM$K;}$A$^$9!#(B
3652 </p>
3653 </div>
3654 </li>
3655 </ul>
3656 </div>
3657 <div class="rfc-t" id="rfc.section.A.p.3">
3658 <div class="t-pair">
3659 <p xml:lang="en" class="t-l-en">
3660 Finally,
3661 a special entity, "&amp;rfc.number;", is available.
3662 Authors preparing an RFC should use this entity whenever they want to
3663 reference the number of the RFC within the document itself.
3664 In printed versions of the document,
3665 the appropriate substitution (or "XXXX") will occur.
3666 </p>
3667 <p xml:lang="ja" class="t-l-ja">
3668 $B:G8e$K!"FCJL$J<BBN(B "&amp;rfc.number;" $B$,;H$($^$9!#(B
3669 RFC $B$rMQ0U$9$kCx<T$O$3$N<BBN$rJ8=q<+?H$N(B
3670 RFC $BHV9f$r;2>H$7$?$$;~$K;H$&$Y$-$G$9!#J8=q$N0u:~HG$G$O!"E,@Z$JBeBX(B
3671 ($B$^$?$O(B "XXXX") $B$r;H$$$^$9!#(B
3672 </p>
3673 </div>
3674 <ins class="t-note t-l-ja" xml:lang="ja">
3675 (<span class="t-note-title">$BLuCm(B:</span>
3676 <div class="rfc-figure">
3677 <span class="rfc-figure-id" id="rfc.figure.u.36">&#x00A0;</span>
3678 <div class="rfc-preamble">$B<B:]$K;H$&;~$O!"(B</div>
3679 <pre class="rfc-artwork" xml:space="preserve">&lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd" [&lt;!ENTITY rfc.number "1234"&gt;]&gt;</pre>
3680 <div class="rfc-postamble">$B$N$h$&$K!"J8=q7?@k8@$GEv3:(B RFC
3681 $BHV9f$r<($9$3$H$K$J$k$G$7$g$&!#(B</div>
3682 </div>
3683 )
3684 </ins>
3685 </div>
3686 </div>
3687 <div class="rfc-section" id="rfc.section.B">
3688 <div id="rfc.dtd">
3689 <h1>B. The RFC DTD</h1>
3690 </div>
3691
3692 <ins class="t-note t-l-ja" xml:lang="ja">
3693 <span class="t-note-title">$BLuCm(B:</span>
3694 <p class="rfc-t" id="rfc.section.B.p.1">$B$3$N(B DTD $B$N%U%!%$%k(B rfc2629.dtd $B$O!"(B
3695 <a href="http://xml.resource.org/authoring/" title="URI: &lt;http://xml.resource.org/authoring/>">xml2rfc
3696 $B9)6q(B</a>$B$NCf$K$b4^$^$l$F$$$^$9!#(B</p>
3697 </ins>
3698
3699 <div class="rfc-figure">
3700 <span class="rfc-figure-id" id="rfc.figure.u.37">&#x00A0;</span>
3701
3702 <div class="t-pair">
3703 <p xml:lang="en" class="t-l-en">
3704 <pre class="rfc-artwork" xml:space="preserve">
3705 &lt;!--
3706 DTD for the RFC document series, draft of 99-01-30
3707 --&gt;
3708
3709
3710 &lt;!--
3711 Contents
3712
3713 DTD data types
3714
3715 The top-level
3716
3717 Front matter
3718
3719 The Body
3720
3721 Back matter
3722 --&gt;
3723
3724
3725 &lt;!--
3726 DTD data types:
3727
3728 entity description
3729 ====== ===============================================
3730 NUMBER [0-9]+
3731 NUMBERS a comma-separated list of NUMBER
3732
3733 DAY the day of the month, e.g., "1"
3734 MONTH the month of the year, e.g., "January"
3735 YEAR a four-digit year, e.g., "1999"
3736
3737 URI e.g., "http://invisible.net/"
3738
3739 ATEXT/CTEXT printable ASCII text (no line-terminators)
3740
3741 TEXT character data
3742 --&gt;
3743
3744
3745 &lt;!ENTITY % NUMBER "CDATA"&gt;
3746 &lt;!ENTITY % NUMBERS "CDATA"&gt;
3747
3748 &lt;!ENTITY % DAY "CDATA"&gt;
3749 &lt;!ENTITY % MONTH "CDATA"&gt;
3750 &lt;!ENTITY % YEAR "CDATA"&gt;
3751
3752 &lt;!ENTITY % URI "CDATA"&gt;
3753
3754 &lt;!ENTITY % ATEXT "CDATA"&gt;
3755 &lt;!ENTITY % CTEXT "#PCDATA"&gt;
3756
3757 &lt;!ENTITY % TEXT "#PCDATA"&gt;
3758
3759 &lt;!ENTITY rfc.number "2629"&gt;
3760
3761
3762 &lt;!--
3763 The top-level
3764 --&gt;
3765
3766
3767 &lt;!--
3768 attributes for the "rfc" element are supplied by the RFC
3769 editor. when preparing drafts, authors should leave them blank.
3770
3771 the "seriesNo" attribute is used if the category is, e.g., BCP.
3772 --&gt;
3773 &lt;!ELEMENT rfc (front,middle,back?)&gt;
3774 &lt;!ATTLIST rfc
3775 number %NUMBER; #IMPLIED
3776 obsoletes %NUMBERS; ""
3777 updates %NUMBERS; ""
3778 category (std|bcp|info|exp|historic)
3779 "info"
3780 seriesNo %NUMBER; #IMPLIED
3781 ipr (full2026|noDerivativeWorks2026|none)
3782 #IMPLIED
3783 docName %ATEXT; #IMPLIED&gt;
3784
3785 &lt;!--
3786 Front matter
3787 --&gt;
3788
3789
3790 &lt;!ELEMENT front (title,author+,date,area*,workgroup*,keyword*,
3791 abstract?,note*)&gt;
3792
3793 &lt;!-- the "abbrev" attribute is used for headers, etc. --&gt;
3794 &lt;!ELEMENT title (%CTEXT;)&gt;
3795 &lt;!ATTLIST title
3796 abbrev %ATEXT; #IMPLIED&gt;
3797
3798 &lt;!ELEMENT author (organization,address?)&gt;
3799 &lt;!ATTLIST author
3800 initials %ATEXT; #IMPLIED
3801 surname %ATEXT; #IMPLIED
3802 fullname %ATEXT; #IMPLIED&gt;
3803
3804 &lt;!ELEMENT organization
3805 (%CTEXT;)&gt;
3806 &lt;!ATTLIST organization
3807 abbrev %ATEXT; #IMPLIED&gt;
3808
3809 &lt;!ELEMENT address (postal?,phone?,facsimile?,email?,uri?)&gt;
3810
3811 &lt;!-- at most one of each the city, region, code, and country
3812 elements may be present --&gt;
3813 &lt;!ELEMENT postal (street+,(city|region|code|country)*)&gt;
3814 &lt;!ELEMENT street (%CTEXT;)&gt;
3815 &lt;!ELEMENT city (%CTEXT;)&gt;
3816 &lt;!ELEMENT region (%CTEXT;)&gt;
3817 &lt;!ELEMENT code (%CTEXT;)&gt;
3818 &lt;!ELEMENT country (%CTEXT;)&gt;
3819 &lt;!ELEMENT phone (%CTEXT;)&gt;
3820 &lt;!ELEMENT facsimile (%CTEXT;)&gt;
3821 &lt;!ELEMENT email (%CTEXT;)&gt;
3822 &lt;!ELEMENT uri (%CTEXT;)&gt;
3823
3824 &lt;!ELEMENT date EMPTY&gt;
3825 &lt;!ATTLIST date
3826 day %DAY; #IMPLIED
3827 month %MONTH; #REQUIRED
3828 year %YEAR; #REQUIRED&gt;
3829
3830 &lt;!-- meta-data... --&gt;
3831 &lt;!ELEMENT area (%CTEXT;)&gt;
3832 &lt;!ELEMENT workgroup (%CTEXT;)&gt;
3833 &lt;!ELEMENT keyword (%CTEXT;)&gt;
3834
3835 &lt;!ELEMENT abstract (t)+&gt;
3836 &lt;!ELEMENT note (t)+&gt;
3837 &lt;!ATTLIST note
3838 title %ATEXT; #REQUIRED&gt;
3839
3840
3841 &lt;!--
3842 The body
3843 --&gt;
3844
3845
3846 &lt;!ELEMENT middle (section)+&gt;
3847
3848 &lt;!ELEMENT section (t|figure|section)*&gt;
3849 &lt;!ATTLIST section
3850 anchor ID #IMPLIED
3851 title %ATEXT; #REQUIRED&gt;
3852
3853 &lt;!ELEMENT t (%TEXT;|list|figure|xref|eref|iref|vspace)*&gt;
3854 &lt;!ATTLIST t
3855 hangText %ATEXT; #IMPLIED&gt;
3856
3857 &lt;!-- the value of the style attribute is inherited from the closest
3858 parent --&gt;
3859 &lt;!ELEMENT list (t+)&gt;
3860 &lt;!ATTLIST list
3861 style (numbers|symbols|hanging|empty)
3862 "empty"&gt;
3863
3864 &lt;!ELEMENT xref (%CTEXT;)&gt;
3865 &lt;!ATTLIST xref
3866 target IDREF #REQUIRED
3867 pageno (true|false) "false"&gt;
3868
3869 &lt;!ELEMENT eref (%CTEXT;)&gt;
3870 &lt;!ATTLIST eref
3871 target %URI; #REQUIRED&gt;
3872
3873 &lt;!ELEMENT iref EMPTY&gt;
3874 &lt;!ATTLIST iref
3875 item %ATEXT; #REQUIRED
3876 subitem %ATEXT; ""&gt;
3877
3878 &lt;!ELEMENT vspace EMPTY&gt;
3879 &lt;!ATTLIST vspace
3880 blankLines %NUMBER; "0"&gt;
3881
3882 &lt;!ELEMENT figure (preamble?,artwork,postamble?)&gt;
3883 &lt;!ATTLIST figure
3884 anchor ID #IMPLIED
3885 title %ATEXT; ""&gt;
3886
3887 &lt;!ELEMENT preamble (%TEXT;|xref|eref|iref)*&gt;
3888 &lt;!ELEMENT artwork (%TEXT;)*&gt;
3889 &lt;!ATTLIST artwork
3890 xml:space (default|preserve) "preserve"&gt;
3891 &lt;!ELEMENT postamble (%TEXT;|xref|eref|iref)*&gt;
3892
3893
3894 &lt;!--
3895 Back matter
3896 --&gt;
3897
3898
3899 &lt;!-- sections, if present, are appendices --&gt;
3900 &lt;!ELEMENT back (references?,section*)&gt;
3901
3902 &lt;!ELEMENT references (reference+)&gt;
3903 &lt;!ELEMENT reference (front,seriesInfo*)&gt;
3904 &lt;!ATTLIST reference
3905 anchor ID #IMPLIED
3906 target %URI; #IMPLIED&gt;
3907 &lt;!ELEMENT seriesInfo EMPTY&gt;
3908 &lt;!ATTLIST seriesInfo
3909 name %ATEXT; #REQUIRED
3910 value %ATEXT; #REQUIRED&gt;
3911 </pre>
3912 </p>
3913 <p xml:lang="ja" class="t-l-ja">
3914 <pre class="rfc-artwork" xml:space="preserve">
3915 &lt;!--
3916 RFC $BJ8=q7ONsMQ(B DTD, 99-01-30 $B$N860F(B ($B$NCm<aItJ,OBLu(B)
3917 --&gt;
3918
3919
3920 &lt;!--
3921 $BFbMF(B
3922
3923 DTD $B%G!<%?7?(B
3924
3925 $B:G>e0L(B
3926
3927 Front matter
3928
3929 The Body
3930
3931 Back matter
3932 --&gt;
3933
3934
3935 &lt;!--
3936 DTD $B%G!<%?7?(B:
3937
3938 $B<BBN(B $B@bL@(B
3939 ====== ===============================================
3940 NUMBER [0-9]+
3941 NUMBERS $BFIE@(B(comma)$B6h@Z$j$N(B NUMBER
3942
3943 DAY $B7nCf$NF|!"Nc$($P(B "1"
3944 MONTH $BG/Cf$N7n!"Nc$($P(B "January" (1$B7n(B)
3945 YEAR 4$B7eG/9f!"Nc$($P(B "1999"
3946
3947 URI $BNc(B "http://invisible.net/"
3948
3949 ATEXT/CTEXT $B0u;z2DG=(B ASCII $BJ8;zNs(B ($B9T=*C<L5$7(B)
3950
3951 TEXT $BJ8;z%G!<%?(B
3952 --&gt;
3953
3954
3955 &lt;!ENTITY % NUMBER "CDATA"&gt;
3956 &lt;!ENTITY % NUMBERS "CDATA"&gt;
3957
3958 &lt;!ENTITY % DAY "CDATA"&gt;
3959 &lt;!ENTITY % MONTH "CDATA"&gt;
3960 &lt;!ENTITY % YEAR "CDATA"&gt;
3961
3962 &lt;!ENTITY % URI "CDATA"&gt;
3963
3964 &lt;!ENTITY % ATEXT "CDATA"&gt;
3965 &lt;!ENTITY % CTEXT "#PCDATA"&gt;
3966
3967 &lt;!ENTITY % TEXT "#PCDATA"&gt;
3968
3969 &lt;!ENTITY rfc.number "2629"&gt;
3970
3971
3972 &lt;!--
3973 $B:G>e0L(B
3974 --&gt;
3975
3976
3977 &lt;!--
3978 "rfc" $BMWAG$NB0@-$O(B RFC $BJT=8<T$K$h$jKd$a$i$l$^$9!#(B
3979 $B860F$rMQ0U$9$k:]$K$O!"Cx<T$O6uMs$K$7$F$*$/$Y$-$G$9!#(B
3980
3981 "seriesNo" $BB0@-$OJ,N`$,Nc$($P(B BCP $B$N;~$K;H$$$^$9!#(B
3982 --&gt;
3983 &lt;!ELEMENT rfc (front,middle,back?)&gt;
3984 &lt;!ATTLIST rfc
3985 number %NUMBER; #IMPLIED
3986 obsoletes %NUMBERS; ""
3987 updates %NUMBERS; ""
3988 category (std|bcp|info|exp|historic)
3989 "info"
3990 seriesNo %NUMBER; #IMPLIED
3991 ipr (full2026|noDerivativeWorks2026|none)
3992 #IMPLIED
3993 docName %ATEXT; #IMPLIED&gt;
3994
3995 &lt;!--
3996 Front matter
3997 --&gt;
3998
3999
4000 &lt;!ELEMENT front (title,author+,date,area*,workgroup*,keyword*,
4001 abstract?,note*)&gt;
4002
4003 &lt;!-- "abbrev" $BB0@-$OF,$H$+$K;H$$$^$9!#(B --&gt;
4004 &lt;!ELEMENT title (%CTEXT;)&gt;
4005 &lt;!ATTLIST title
4006 abbrev %ATEXT; #IMPLIED&gt;
4007
4008 &lt;!ELEMENT author (organization,address?)&gt;
4009 &lt;!ATTLIST author
4010 initials %ATEXT; #IMPLIED
4011 surname %ATEXT; #IMPLIED
4012 fullname %ATEXT; #IMPLIED&gt;
4013
4014 &lt;!ELEMENT organization
4015 (%CTEXT;)&gt;
4016 &lt;!ATTLIST organization
4017 abbrev %ATEXT; #IMPLIED&gt;
4018
4019 &lt;!ELEMENT address (postal?,phone?,facsimile?,email?,uri?)&gt;
4020
4021 &lt;!-- city, region, code, country $B3FMWAG$,$;$$$<$$(B1$B2s=P8=2DG=(B --&gt;
4022 &lt;!ELEMENT postal (street+,(city|region|code|country)*)&gt;
4023 &lt;!ELEMENT street (%CTEXT;)&gt;
4024 &lt;!ELEMENT city (%CTEXT;)&gt;
4025 &lt;!ELEMENT region (%CTEXT;)&gt;
4026 &lt;!ELEMENT code (%CTEXT;)&gt;
4027 &lt;!ELEMENT country (%CTEXT;)&gt;
4028 &lt;!ELEMENT phone (%CTEXT;)&gt;
4029 &lt;!ELEMENT facsimile (%CTEXT;)&gt;
4030 &lt;!ELEMENT email (%CTEXT;)&gt;
4031 &lt;!ELEMENT uri (%CTEXT;)&gt;
4032
4033 &lt;!ELEMENT date EMPTY&gt;
4034 &lt;!ATTLIST date
4035 day %DAY; #IMPLIED
4036 month %MONTH; #REQUIRED
4037 year %YEAR; #REQUIRED&gt;
4038
4039 &lt;!-- $B%a%?!&%G!<%?!&!&!&(B --&gt;
4040 &lt;!ELEMENT area (%CTEXT;)&gt;
4041 &lt;!ELEMENT workgroup (%CTEXT;)&gt;
4042 &lt;!ELEMENT keyword (%CTEXT;)&gt;
4043
4044 &lt;!ELEMENT abstract (t)+&gt;
4045 &lt;!ELEMENT note (t)+&gt;
4046 &lt;!ATTLIST note
4047 title %ATEXT; #REQUIRED&gt;
4048
4049
4050 &lt;!--
4051 $BK\BN(B
4052 --&gt;
4053
4054
4055 &lt;!ELEMENT middle (section)+&gt;
4056
4057 &lt;!ELEMENT section (t|figure|section)*&gt;
4058 &lt;!ATTLIST section
4059 anchor ID #IMPLIED
4060 title %ATEXT; #REQUIRED&gt;
4061
4062 &lt;!ELEMENT t (%TEXT;|list|figure|xref|eref|iref|vspace)*&gt;
4063 &lt;!ATTLIST t
4064 hangText %ATEXT; #IMPLIED&gt;
4065
4066 &lt;!-- style $BB0@-$NCM$OD>6a$N?F$+$i7Q>5$9$k(B --&gt;
4067 &lt;!ELEMENT list (t+)&gt;
4068 &lt;!ATTLIST list
4069 style (numbers|symbols|hanging|empty)
4070 "empty"&gt;
4071
4072 &lt;!ELEMENT xref (%CTEXT;)&gt;
4073 &lt;!ATTLIST xref
4074 target IDREF #REQUIRED
4075 pageno (true|false) "false"&gt;
4076
4077 &lt;!ELEMENT eref (%CTEXT;)&gt;
4078 &lt;!ATTLIST eref
4079 target %URI; #REQUIRED&gt;
4080
4081 &lt;!ELEMENT iref EMPTY&gt;
4082 &lt;!ATTLIST iref
4083 item %ATEXT; #REQUIRED
4084 subitem %ATEXT; ""&gt;
4085
4086 &lt;!ELEMENT vspace EMPTY&gt;
4087 &lt;!ATTLIST vspace
4088 blankLines %NUMBER; "0"&gt;
4089
4090 &lt;!ELEMENT figure (preamble?,artwork,postamble?)&gt;
4091 &lt;!ATTLIST figure
4092 anchor ID #IMPLIED
4093 title %ATEXT; ""&gt;
4094
4095 &lt;!ELEMENT preamble (%TEXT;|xref|eref|iref)*&gt;
4096 &lt;!ELEMENT artwork (%TEXT;)*&gt;
4097 &lt;!ATTLIST artwork
4098 xml:space (default|preserve) "preserve"&gt;
4099 &lt;!ELEMENT postamble (%TEXT;|xref|eref|iref)*&gt;
4100
4101
4102 &lt;!--
4103 Back matter
4104 --&gt;
4105
4106
4107 &lt;!-- sections $B$,$"$k>l9g!"$=$l$OImB0=q(B --&gt;
4108 &lt;!ELEMENT back (references?,section*)&gt;
4109
4110 &lt;!ELEMENT references (reference+)&gt;
4111 &lt;!ELEMENT reference (front,seriesInfo*)&gt;
4112 &lt;!ATTLIST reference
4113 anchor ID #IMPLIED
4114 target %URI; #IMPLIED&gt;
4115 &lt;!ELEMENT seriesInfo EMPTY&gt;
4116 &lt;!ATTLIST seriesInfo
4117 name %ATEXT; #REQUIRED
4118 value %ATEXT; #REQUIRED&gt;
4119 </pre>
4120 </p>
4121 </div>
4122
4123 </div>
4124 </div>
4125 <div class="rfc-section" id="rfc.section.C">
4126 <div class="t-pair t-heading">
4127 <h1 xml:lang="en" class="t-l-en">C. Acknowledgements</h1>
4128 <h1 xml:lang="ja" class="t-l-ja">C.
4129 $B<U<-(B</h1>
4130 </div>
4131 <div class="rfc-t" id="rfc.section.C.p.1">
4132 <div class="t-pair">
4133 <p xml:lang="en" class="t-l-en">The author gratefully acknowledges the contributions of:
4134 Alan Barrett,
4135 Brad Burdick,
4136 Brian Carpenter,
4137 Steve Deering,
4138 Patrik Faltstrom,
4139 Jim Gettys,
4140 Carl Malamud,
4141 Chris Newman,
4142 Kurt Starsinic,
4143 and,
4144 Frank Strauss.</p>
4145 <p xml:lang="ja" class="t-l-ja">$BCx<T$O<!$NJ}!9$N9W8%$K<U0U$rI=$7$^$9(B:
4146 Alan Barrett,
4147 Brad Burdick,
4148 Brian Carpenter,
4149 Steve Deering,
4150 Patrik Faltstrom,
4151 Jim Gettys,
4152 Carl Malamud,
4153 Chris Newman,
4154 Kurt Starsinic,
4155 Frank Strauss$B!#(B</p>
4156 </div>
4157 </div>
4158 </div>
4159 <div id="rfc-copyright" class="rfc-section">
4160 <div class="t-pair" id="rfc.copyright">
4161 <h1 xml:lang="en" class="t-l-en">Full Copyright Statement</h1>
4162 <h1 xml:lang="ja" class="t-l-ja">$B40A4$JCx:n8"@<L@(B</h1>
4163 </div>
4164 <div class="t-pair">
4165 <p class="t-l-en t-hide-no" xml:lang="en">
4166 Copyright &#x00A9;
4167 <a href="http://www.isoc.org/">The Internet Society</a>
4168 (1999).
4169 All Rights Reserved.
4170 </p>
4171 <p class="t-l-ja" xml:lang="ja">
4172 $BCx:n8"(B &#x00A9;
4173 <a href="http://www.isoc.org/">The Internet Society</a>
4174 (1999)$B!#A48"N1J]!#(B
4175 </p>
4176 </div>
4177 <div class="rfc-t">
4178 <div class="t-pair">
4179 <p class="t-l-en t-hide-no" xml:lang="en">
4180 This document and translations of it may be copied
4181 and furnished
4182 to others, and derivative works that comment on or otherwise
4183 explain it or assist in its implementation may be prepared,
4184 copied, published and distributed, in whole or in part,
4185 without restriction of any kind, provided that the
4186 above copyright notice
4187 and this paragraph are included on all such copies and
4188 derivative works. However, this document itself may
4189 not be modified in any way, such as by removing the
4190 copyright notice or references to the Internet Society
4191 or other Internet organizations, except as
4192 needed for the purpose of developing Internet standards
4193 in which case the procedures for copyrights defined in
4194 the Internet Standards process must be followed, or as
4195 required to translate it into languages other than English.
4196 </p>
4197 <p class="t-l-ja" xml:lang="ja">
4198 $B$3$NJ8=q$H$=$NK]Lu$OJ#<L$7B><T$KDs6!$7$F$bNI$/!"$^$?$3$l$K$D$$$FCm<a$r2C$($k$+$b$7$/$O@bL@$9$k!"$"$k$$$O$=$N<BAu$r=u$1$kGI@8E*:n6H$O!"$=$NA4It$^$?$O0lIt$r!">e5-$NCx:n8"I=<(5Z$S$3$N@a$rA4$F$NJ#<LJ*5Z$SGI@8E*:n6H$K4^$`8B$j$K$*$$$F!"0l@Z$N@)8BL5$7$K!"MQ0U!&J#<L!&=PHG!&G[I[$7$FNI$$!#$7$+$7!"$3$NJ8=q<+BN$O!"Cx:n8"I=<($"$k$$$O(B
4199 Internet Society $BKt$OB>$N(B Internet
4200 $BAH?%$X$N8@5Z$r<h$j=|$/$J$I!"$$$+$J$kJ}K!$K$;$hJQ99$7$F$O$J$i$J$$!#C"$7!"(B
4201 Internet $BI8=`2=2aDx$GDj5A$5$l$?Cx:n8"$N$?$a$N<jB3$-$K=>$$(B
4202 Internet $BI8=`$r3+H/$9$kL\E*$KI,MW$J>l9g!"$"$k$$$O1Q8l0J30$N8@8l$KK]Lu$9$k$N$KI,MW$J>l9g$r=|$/!#(B
4203 </p>
4204 </div>
4205 </div>
4206 <div class="rfc-t">
4207 <div class="t-pair">
4208 <p class="t-l-en t-hide-no" xml:lang="en">
4209 The limited permissions granted above are perpetual and will
4210 not be revoked by the Internet Society or its successors or
4211 assigns.
4212 </p>
4213 <p class="t-l-ja" xml:lang="ja">
4214 $B>e5-$GG'$a$?$3$N@)8BIU$-5vBz$O915WE*$J$b$N$G$"$j!"(B
4215 Internet Society $B$b$7$/$O$=$N8e7Q<T$b$7$/$O$=$N>yEO<T$K$h$jGK4~$5$l$k$3$H$O$J$$!#(B
4216 </p>
4217 </div>
4218 </div>
4219 <div class="rfc-t">
4220 <div class="t-pair">
4221 <p class="t-l-en t-hide-no" xml:lang="en">
4222 This document and the information contained herein is provided
4223 on an $B!H(B<strong>AS IS</strong>$B!I(B basis and
4224 <strong>THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
4225 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
4226 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
4227 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
4228 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR
4229 A PARTICULAR PURPOSE</strong>.
4230 </p>
4231 <p class="t-l-ja" xml:lang="ja">
4232 $B$3$NJ8=q5Z$S$3$3$K4^$^$l$k>pJs$O!V(B<strong>$B8=>uM-;Q(B</strong>$B!W$GDs6!$5$l!"(B
4233 <strong>Internet Society $B$*$h$S(B
4234 Internet Engineering Task Force (Internet $B5;=QFCJLD4::0Q0w2q(B)
4235 $B$O$3$3$K4^$^$l$k>pJs$N;HMQ$,$$$+$J$k8"Mx$r$b?/32$7$J$$$H$$$&J]>Z$^$?$O;T>l@-$"$k$$$OFCDjL\E*$X$NE,Ev@-$K$D$$$F$N0EL[E*J]>Z$r4^$a$F$3$l$K8BDj$5$l$J$$!"L@<($"$k$$$O0E<($K$h$k!"0l@Z$NJ]>Z$rH]G'$9$k(B</strong>$B!#(B
4236 </p>
4237 </div>
4238 </div>
4239 <ins class="t-note t-l-ja" xml:lang="ja">
4240 <p class="rfc-t">
4241 (<span class="t-note-title">$BLuCm(B:</span>
4242 $B@5<0$JCx:n8"@<L@$O1Q8l$N86J8$N$_$G$"$j!"Lu<T$O0l@Z$NJ]>Z(B
4243 ($BK]LuJ8$,86J8$H87L)$K0lCW$7$F$$$k$+$r4^$`$,!"$3$l$K8BDj$5$l$J$$!#(B)
4244 $B$r$7$J$$!#(B<a href="#rfc-t-copyright">$BLuJ8$K$D$$$F$NCx:n8"@<L@(B</a>$B$b;2>H$;$h!#(B)
4245 </p>
4246 </ins>
4247 </div>
4248 <div id="rfc-acknowledgement-editor" class="rfc-section">
4249 <div class="t-heading t-pair">
4250 <h1 xml:lang="en" class="t-l-en">Acknowledgement</h1>
4251 <h1 xml:lang="ja" class="t-l-ja">$B<U<-(B</h1>
4252 </div>
4253 <div class="rfc-t">
4254 <div class="t-pair">
4255 <p class="t-l-en" xml:lang="en">
4256 Funding for the
4257 <a href="http://www.rfceditor.org/">RFC editor</a>
4258 function is currently provided by the
4259 <a href="http://www.isoc.org/">Internet Society</a>.
4260 </p>
4261 <p class="t-l-ja" xml:lang="ja">
4262 <a href="http://www.rfceditor.org/" xml:lang="en">RFC
4263 $BJT=8<T(B</a>$B6HL3$N;q6b1g=u$O8=:_(B
4264 <a href="http://www.isoc.org/">Internet Society</a>
4265 $B$K$h$j9T$o$l$F$$$^$9!#(B
4266 </p>
4267 </div>
4268 </div>
4269 </div>
4270 <ins id="rfc-translators-note" class="t-note t-l-ja" xml:lang="ja">
4271 <div class="rfc-section">
4272 <div id="ja.note.mydtd">
4273 <h1>$B$3$NK]LuJ8$N7A<0$K$D$$$F(B</h1>
4274 </div>
4275 <p class="rfc-t" id="rfc.section.1.p.1">$B$3$NJ8=q(B ($B$N86K\(B) $B$O!"(B RFC 2629
4276 $B$GDj5A$5$l$?7A<0$K!"K]LuJ8MQ$NMWAG$r(B XML
4277 $BL>A06u4V$r;H$C$FDI2C$7$FMQ$$$F$$$^$9!#>\$7$/$O!"(B
4278
4279 &lt;<a href="http://suika.fam.cx/~wakaba/lang/rfc/translate/">http://suika.fam.cx/~wakaba/lang/rfc/translate/</a>&gt;
4280
4281 $B$r8fMw2<$5$$!#(B</p>
4282 </div>
4283 <div class="rfc-section" id="t-change">
4284 <h1>$BK]Lu$NJQ99MzNr(B</h1>
4285 <dl>
4286 <dt>2002-04-30 <a href="mailto:w@suika.fam.cx" title="$BEE;R%a%$%k(B: &lt;w@suika.fam.cx>">$B$o$+$P(B</a>
4287 </dt>
4288 <dd>
4289 <ul>
4290 <li>$BK]Lu40N;!#(B</li>
4291 </ul>
4292 </dd>
4293 <dt>2002-05-03 <a href="mailto:w@suika.fam.cx" title="$BEE;R%a%$%k(B: &lt;w@suika.fam.cx>">$B$o$+$P(B</a>
4294 </dt>
4295 <dd>
4296 <ul>
4297 <li>$BLuCm$r4v$D$+DI2C!#K]LuJQ99MzNr$N>O$r?7@_!#(B</li>
4298 </ul>
4299 </dd>
4300 </dl>
4301 </div>
4302 <div class="rfc-section" id="rfc-t-copyright">
4303 <h1>$BLuJ8$K$D$$$F$NCx:n8"@<L@(B</h1>
4304 <ul>
4305 <li>Copyright &#x00A9; $B$o$+$P(B (2002)$B!#A48"J]N1!#(B</li>
4306 </ul>
4307 <p>
4308 <a href="#rfc-copyright">$B86J8$NCx:n8"@<L@(B</a>$B$,!"LuJ8$K$D$$$F$bF1MM$KE,MQ$5$l$^$9!#(B</p>
4309 <p>$B$^$?!"2~Lu$=$NB>$N86J8$NCx:n8"@<L@$KH?$7$J$$HO0O$K$*$1$k2~JQ$O!"0l@Z$N5v2DL5$/9T$C$F9=$$$^$;$s!#(B</p>
4310 </div>
4311 </ins>
4312 </body>
4313 </html>

admin@suikawiki.org
ViewVC Help
Powered by ViewVC 1.1.24