WD-HTTP-in-RDF-20080908.1
86.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
<title>HTTP Vocabulary in RDF</title>
<style type="text/css">
.schema {
color: black;
background-color: #ccddcc;
}
.example {
margin: 1em 2em 1em 2em;
color: #000;
background-color: #fff;
padding: 0.5em;
border: 1px dotted #e63232;
}
.note {
background-color: #adff2f;
}
.keyword {
font-weight: bold;
font-style: italic;
}
pre {
border: 1px dotted #000;
color: #000;
background-color: #f4f3e7;
font-size: 110%;
}
table {
margin: 1ex 2%;
width: 90%;
border: solid 1px #000;
border-collapse: collapse;
}
thead,tfoot,tbody,tr {
margin: 0;
padding: 0;
}
th,td {
margin: 0;
padding: 0.2em 1em;
border: solid 1px #000;
}
abbr,acronym {
font-weight: inherit;
font-style: normal;
border-bottom-width: 1px;
border-bottom-style: dotted;
border-bottom-color: inherit;
}
</style>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
</head>
<body>
<div class="head" id="head"><a href="http://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72" /></a>
<h1><a id="title" name="title"><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Vocabulary in <acronym title="Resource Description Framework">RDF</acronym></a></h1>
<h2><a id="w3c-doctype" name="w3c-doctype"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 8 September 2008</a></h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908">http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908</a></dd>
<dt>Latest version:</dt>
<dd><a href="http://www.w3.org/TR/HTTP-in-RDF/">http://www.w3.org/TR/HTTP-in-RDF/</a></dd>
<dt>Previous version:</dt>
<dd><a href="http://www.w3.org/TR/2007/WD-HTTP-in-RDF-20070323/">http://www.w3.org/TR/2007/WD-HTTP-in-RDF-20070323/</a></dd>
<dt>Editors:</dt>
<dd>Johannes Koch, Fraunhofer Institute for Applied Information Technology (<acronym title="Fraunhofer Institute for Applied Information Technology">FIT</acronym>)</dd>
<dd>Carlos A Velasco, Fraunhofer Institute for Applied Information Technology (<acronym title="Fraunhofer Institute for Applied Information Technology">FIT</acronym>)</dd>
<dd>Shadi Abou-Zahra, <acronym title="World Wide Web Consortium">W3C</acronym>/<acronym title="Web Accessibility Initiative">WAI</acronym></dd>
</dl>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2008 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
</div>
<hr />
<h2><a id="abstract" name="abstract">Abstract</a></h2>
<p>The identification of resources on the Web by <acronym title="Uniform Resource Identifier">URI</acronym> alone may not be sufficient, as other factors such as <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the <a href="http://www.w3.org/WAI/intro/earl.php">W3C Evaluation And Report Language (EARL)</a>. This document provides a representation of the HTTP vocabulary in <acronym title="Resource Description Framework">RDF</acronym>, to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by <acronym title="Request for Comments">RFC</acronym> 2616, as well as additional HTTP headers registered by <acronym title="Internet Assigned Numbers Authority">IANA</acronym>. These terms can also be used to record <acronym title="Secure Hyper Text Transfer Protocol">HTTPS</acronym> exchanges.</p>
<h2><a id="status" name="status">Status of this document</a></h2>
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
<p>This Working Draft of the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Vocabulary in <acronym title="Resource Description Framework">RDF</acronym> document was published on 8 September 2008 by the <a href="http://www.w3.org/WAI/ER/">Evaluation and Repair Tools Working Group (ERT WG)</a>. It is an update of the previous <a href="http://www.w3.org/TR/2007/WD-HTTP-in-RDF-20070323/">HTTP Vocabulary in RDF Working Draft of 23 March 2007</a>, and addresses the comments received since (see history of <a href="#changes">document changes</a>). This document is part of the <a href="http://www.w3.org/WAI/intro/earl.php">W3C Evaluation And Report Language (EARL)</a>. It is expected to be the last working draft before publication as a W3C Working Group Note.</p>
<p>The RDF terms defined by this document can be used to extend the <a href="http://www.w3.org/TR/EARL10-Schema/">Evaluation And Report Language (EARL) 1.0 Schema</a>, but can also be used separately to record an HTTP exchange between a client and a server for any purpose. The Working Group encourages feedback about the approach, as well as about the completeness and maturity of this document by developers and researchers who have interest in a representation of the HTTP vocabulary in RDF format. Feedback from the <a href="http://www.w3.org/QA/IG/">W3C Quality Assurance Interest Group</a>, the <a href="http://www.w3.org/2001/sw/interest/">W3C Semantic Web Interest Group</a>, and the <a href="http://www.w3.org/2007/powder/">Protocol for Web Description Resources Working Group</a> is particularly welcome. Please send comments on this document by 29 September 2008 to the public mailing list of the working group <a href="mailto:public-wai-ert@w3.org">public-wai-ert@w3.org</a>. The <a href="http://lists.w3.org/Archives/Public/public-wai-ert/">archives of the working group mailing list</a> are publicly available.</p>
<p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
<p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. The group does not expect this document to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/32094/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p>
<hr />
<div id="toc">
<h2><a accesskey="c" id="contents" name="contents">Table of Contents</a></h2>
<ol>
<li><a href="#introduction">Introduction</a>
<ul>
<li><a href="#namespaces">1.1. Namespaces</a></li>
<li><a href="#namingConventions">1.2. Naming Conventions</a></li>
<li><a href="#use-cases">1.3. Use Cases</a></li>
<li><a href="#limitations">1.4. Limitations</a></li>
</ul>
</li>
<li><a href="#classesProperties">Classes and Properties</a>
<ul>
<li><a href="#connectionClass">2.1. Connection Class</a></li>
<li><a href="#messageClass">2.2. Message Class</a>
<ul>
<li><a href="#bodyProperty">2.2.1. Body Property</a></li>
</ul>
</li>
<li><a href="#requestClass">2.3. Request Class</a>
<ul>
<li><a href="#requestURIProperty">2.3.1. Request <acronym title="Uniform Resource Identifier">URI</acronym> Property</a></li>
</ul>
</li>
<li><a href="#responseClass">2.4. Response Class</a></li>
<li><a href="#messageHeaderClass">2.5. MessageHeader Class</a></li>
<li><a href="#headerElementClass">2.6. HeaderElement Class</a></li>
<li><a href="#paramClass">2.7. Param Class</a></li>
</ul>
</li>
<li><a href="#predefined">Predefined Values</a>
<ul>
<li><a href="#methods">3.1. Request Methods</a></li>
<li><a href="#statusCodes">3.2. Status Codes</a></li>
<li><a href="#statusCodeGroups">3.3. Status Code Groups</a></li>
<li><a href="#headerNames">3.4. Header Names</a></li>
</ul>
</li>
</ol>
<h3><a id="appendices" name="appendices"></a>Appendices</h3>
<ol type="A">
<li><a href="#schema">Schema in <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym></a></li>
<li><a href="#terms">Vocabulary Terms</a></li>
<li><a href="#example">Practical Example</a></li>
<li><a href="#references">References</a></li>
<li><a href="#changes">Document Changes</a></li>
</ol>
</div>
<!-- end toc -->
<hr />
<h2><a id="introduction" name="introduction">1. Introduction</a></h2>
<p>This document defines a representation of the Hyper Text Transfer Protocol (HTTP) using the Resource Description Framework (RDF). It defines a collection of RDF classes and properties that represent the HTTP vocabulary as defined by the HTTP specification. These RDF terms can be used to record HTTP or HTTPS request and response messages in RDF format, such as by automated Web accessibility evaluation tools that want to describe Web resources, including the various headers exchanged between the client and server during content negotiation. More usage examples for these terms are described in section <a href="#use-cases">1.3. Use Cases</a>.</p>
<p>This document is not intended to be a clarification or extension of the different concepts of the HTTP specification. The HTTP specification is defined by a series of Request for Comments (RFC) publications and other documentation, including <a href="#ref-rfc2616">RFC 2616</a> and <a href="#ref-rfc4229">RFC 4229</a>. These are listed in <a href="#references">Appendix D: References</a>. This document is also not intended to be an introduction to RDF, the reader is referred to the RDF Primer and RDF specifications [<a href="#ref-rdf">RDF</a>] for this purpose.</p>
<h3><a id="namespaces" name="namespaces">1.1. Namespaces</a></h3>
<p>The <acronym title="Resource Description Framework">RDF</acronym> representation of the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> vocabulary defined by this document uses the namespace <code>http://www.w3.org/2006/http#</code>. The prefix <code>http</code> is used throughout this document to denote this namespace. <a href="#tab-ns1">Table 1</a> presents the namespaces used by this document (<code>rdfs</code> and <code>owl</code> namespaces are normally only used in the schema); and <a href="#tab-ns2">Table 2</a> presentes additional RDF data used by this document. The prefix notation presents the typical conventions used in the Web and in this document to denote a given namespace, and can be freely modified.</p>
<table id="tab-ns1">
<caption>Table 1: namespaces used by this document.</caption>
<tr>
<th>Namespace prefix</th>
<th>Namespace URI</th>
<th>Description</th>
</tr>
<tr>
<td><code>http</code></td>
<td><code>http://www.w3.org/2006/http#</code></td>
<td>Core HTTP vocabulary in RDF terms.</td>
</tr>
<tr>
<td scope="row"><code>cnt</code></td>
<td><code>http://www.w3.org/2007/content#</code></td>
<td>Default namespace for Representing Content in RDF <a href="#ref-content-in-rdf">[Content in RDF]</a>.</td>
</tr>
<tr>
<td scope="row"><code>dc</code></td>
<td><code>http://purl.org/dc/elements/1.1/</code></td>
<td>Dublin Core Metadata Element Set namespace.</td>
</tr>
<tr>
<td scope="row"><code>rdf</code></td>
<td><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></td>
<td>Default <acronym title="Resource Description Framework">RDF</acronym> namespace [<a href="#ref-rdf">RDF</a>].</td>
</tr>
<tr>
<td scope="row"><code>rdfs</code></td>
<td><code>http://www.w3.org/2000/01/rdf-schema#</code></td>
<td>Default <acronym title="Resource Description Framework">RDF</acronym> schema namespace [<a href="#ref-rdf">RDF</a>].</td>
</tr>
<tr>
<td scope="row"><code>owl</code></td>
<td><code>http://www.w3.org/2002/07/owl#</code></td>
<td>Default <acronym title="Web Ontology Language">OWL</acronym> namespace [<a href="#ref-owl">OWL</a>].</td>
</tr>
</table>
<table id="tab-ns2">
<caption>Table 2: RDF data used by this document.</caption>
<tr>
<th>Namespace prefix</th>
<th>Namespace URI</th>
<th>Description</th>
</tr>
<tr>
<td><code>http-header</code></td>
<td><code>http://www.w3.org/2006/http-header#</code></td>
<td>Additional HTTP headers.</td>
</tr>
<tr>
<td><code>http-methods</code></td>
<td><code>http://www.w3.org/2006/http-methods#</code></td>
<td>HTTP methods for requests.</td>
</tr>
<tr>
<td><code>http-statusCodes</code></td>
<td><code>http://www.w3.org/2006/http-statusCodes#</code></td>
<td>HTTP status codes for responses.</td>
</tr>
</table>
<h3><a id="namingConventions" name="namingConventions">1.2. Naming Conventions</a></h3>
<p>By default, the vocabulary introduced by this document uses names starting with upper-case letters for classes and names starting with lower-case letters for properties. The keywords <strong>must</strong>, <strong>required</strong>, <strong>recommended</strong>, <strong>should</strong>, <strong>may</strong>, and <strong>optional</strong> are used in accordance with <a href="#ref-rfc2119">[RFC2119]</a>.</p>
<h3><a id="use-cases" name="use-cases">1.3. Use Cases</a></h3>
<p>The following (non-exhaustive) list of use cases aims to highlight some of the different usages of the terms provided by this document:</p>
<dl>
<dt><a id="use-case1" name="use-case1">Reporting Test Results</a></dt>
<dd>When Web resources are tested, for example for accessibility or other quality assurance testing, it may be significant to record the exact headers exchanged between the server and the client during the testing. Without a record of the exchanged headers, it may not be possible to re-identify the exact resource (or representation of the resource) that has been tested. The terms provided by this document allow quality assurance tools to record the HTTP exchange between a client and a server, for example to record the POST parameters or the headers used during content negotiation. The terms provided by this document can be used in combination with the <acronym title="World Wide Web Consortium">W3C</acronym> Evaluation And Report Language (EARL) <a href="#ref-earl">[EARL]</a>.</dd>
<dt><a id="use-case2" name="use-case2">Precising Conformance Claims</a></dt>
<dd>Conformance claims that are made about a Web resource or group of Web resource, are sometimes only applicable under certain constraints. For example, conformance of a Web site to the W3C Web Content Accessibility Guidelines (WCAG) <a href="#ref-wcag">[WCAG]</a>, may only be applicable for a certain language of the Web site that is using language negotiation. When provding machine-readable conformance claims, for example using the W3C Protocol for Describing Web Resources (POWDER): Description Resources <a href="#ref-powder-dr">[POWDER-DR]</a>, it is important to precise any such constraints that may apply. <span class="note">[Editor Note: the Working Group is exploring the relationship to POWDER]</span>.</dd>
<dt><a id="use-case3" name="use-case3">Debugging Web Applications</a></dt>
<dd>Web applications using client-side scripting such as AJAX may exchange additional HTTP messages with the server without using a different URI. In order to debug such Web applications, it must be possible to reconstruct the exact history of the states through which the Web application passed. Web authoring tools that are designed to develop and debug Web applications could use the terms provided by this document to record the exact HTTP messages exchanged bewteen a client and a server. This information could be provided to the developer as a log to help debug errors in the Web application..</dd>
<dt><a id="use-case4" name="use-case4">Indexing Information Resources</a></dt>
<dd>When indexing RDF information resources that are available through the HTTP protocol (also called "scuttering" in Semantic Web parlance), it is often useful to record information about the HTTP request and response messages that were exchanged, along with the data for later use. In some instances, different representations of the RDF information may be retrieved from the server depending on the HTTP headers and paramters exchanged. The terms provided by this document can be used to supplement the collected data with the HTTP messages as part of a comprehensive indexing repository.</dd>
</dl>
<h3><a id="limitations" name="limitations">1.4. Limitations</a></h3>
<p>There are also notable schema limitations with regards to security and privacy since the content recorded by this vocabulary could potentially contain sensitive information. For example authentication information in <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> headers or other information (login user name, passwords, etc.) within the body of the message. Since the schema of this document is limited to terms defined by the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> vocabulary, security and privacy considerations need to be made at the application level. For example, certain parts of the data may be restricted to appropriate user permissions or obfuscated.</p>
<h2><a id="classesProperties" name="classesProperties">2. Classes and Properties</a></h2>
<p>This section defines <acronym title="Resource Description Framework">RDF</acronym> terms for the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 1.1 specification according to [<a href="#ref-rfc2616"><acronym title="Request for Comments">RFC</acronym> 2616</a>].</p>
<h3><a id="connectionClass" name="connectionClass">2.1. Connection Class</a></h3>
<p>A resource of type <code>Connection</code> represents a connection that is used for the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> transfer. The following properties may appear in nodes of type <code>Connection</code>:</p>
<dl>
<dt><code>connectionAuthority</code></dt>
<dd>Property representing the connected authority (server host and port) as a Literal.</dd>
<dt><code>requests</code></dt>
<dd>Property representing the HTTP requests sent via the connection as a Collection of <code>Request</code> resources.</dd>
</dl>
<div class="example">
<p><strong>Example 2.1:</strong> A <code>Connection</code> resource.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xml:base="http://www.example.org/connection#">
<http:Connection rdf:ID="conn">
<http:connectionAuthority>www.example.org:80</http:connectionAuthority>
<http:requests rdf:parseType="Collection">
<http:Request rdf:ID="req0"/>
<http:Request rdf:ID="req1"/>
</http:requests>
</http:Connection>
</rdf:RDF></pre>
</div>
<h3><a id="messageClass" name="messageClass">2.2. Message Class</a></h3>
<p>A resource of type <code>Message</code> represents an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> message. The following properties may appear in resources of type <code>Message</code>:</p>
<dl>
<dt><code>httpVersion</code></dt>
<dd>Property representing the HTTP version number as a Literal (the format is <em>'digit.digit'</em>).</dd>
<dt><code>dc:date</code></dt>
<dd>Property representing a date as a Literal (see the usage of this property in <a href="#dateReq">requests</a> and <a href="#dateResp">responses</a>).</dd>
<dt><code>headers</code></dt>
<dd>Property representing the HTTP headers sent with the message as a Collection of <code>MessageHeader</code> resources.</dd>
<dt><code>body</code></dt>
<dd>Property pointing to a resource representing the message body (see <a href="#bodyProperty">2.2.1 Body Property</a>).</dd>
</dl>
<div class="example">
<p><strong>Example 2.2:</strong> A <code>Message</code> resource.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xml:base="http://example.org/message#">
<http:Message rdf:ID="mess0">
<http:httpVersion>1.1</http:httpVersion>
<dc:date>2007-09-13</dc:date>
<http:headers rdf:parseType="Collection">
<http:MessageHeader rdf:ID="mh0"/>
<http:MessageHeader rdf:ID="mh1"/>
</http:headers>
<http:body>
<cnt:Content rdf:ID="cont0"/>
</http:body>
</http:Message>
</rdf:RDF></pre>
</div>
<p>There are two subclasses from the <code>Message</code> class: <a href="#requestClass"><code>Request</code></a> and <a href="#responseClass"><code>Response</code></a>.</p>
<h4><a id="bodyProperty" name="bodyProperty">2.2.1. Body Property</a></h4>
<p>The <code>body</code> property represents an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> entity body as defined in [<a href="#ref-rfc2616"><acronym title="Request for Comments">RFC</acronym> 2616</a>]. It can appear in resources of both type <code>Request</code> or <code>Response</code>. The object for this property must be a resource of the type <code>cnt:Content</code> or a subclass thereof. <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> bodies are series of bytes. Thus it is always possible to point to a <code>cnt:Base64Content</code> resource. If the body is textual content, you can also point to a <code>cnt:TextContent</code> resource. If the body is XML content, you can also point to a <code>cnt:XMLContent</code> resource (see <a href="#ref-content-in-rdf">[Content in RDF]</a> for more information on content representations in RDF).</p>
<p><strong>Note:</strong> for multiple representations of the same entity body, an RDF container must be used to describe the relationship. For example the <code>rdf:Bag</code> container may be useful if all representations are equivalent, or in other cases <code>rdf:Alt</code> may be useful if there is a prefered representation with alternatives.</p>
<div class="example">
<p><strong>Example 2.2.1:</strong> Multiple representations of the same entity body.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xml:base="http://example.org/message#">
<http:Message rdf:ID="mess0">
<http:body>
<rdf:Alt>
<rdf:li>
<cnt:XMLContent rdf:ID="cont0"/>
<rdf:li>
<rdf:li>
<cnt:TextContent rdf:ID="cont0-alt1"/>
<rdf:li>
<rdf:li>
<cnt:Base64Content rdf:ID="cont0-alt2"/>
<rdf:li>
</rdf:Alt>
</http:body>
</http:Message>
</rdf:RDF></pre>
</div>
<h3><a id="requestClass" name="requestClass">2.3. Request Class</a></h3>
<p>The <code>Request</code> class is a subclass of the <a href="#messageClass"><code>Message</code> class</a>. A resource of this type represents an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> request. Additional to the properties mentioned in <a href="#messageClass">2.2 Message Class</a>, the following properties may appear in resources of type <code>Request</code>:</p>
<dl>
<dt><code>methodName</code></dt>
<dd>Property representing the method name as a Literal.</dd>
<dt><code>method</code></dt>
<dd>Property poining to a <code>Method</code> resource representing the HTTP method (optional, see <a href="#methods">3.1. Methods</a>).</dd>
<dt><code>requestURI</code></dt>
<dd>Property (or one of its sub-properties) representing the request <acronym title="Uniform Resource Identifier">URI</acronym> (see also <a href="#requestURIProperty">2.3.1 Request <acronym title="Uniform Resource Identifier">URI</acronym> Property</a>).</dd>
<dt><code>response</code></dt>
<dd>Property pointing to a <code>Response</code> resource representing the response resulting from this request (see <a href="#responseClass">2.4. Response Class</a>).</dd>
</dl>
<p><a id="dateReq" name="dateReq">The <code>dc:date</code> property</a> when used in a <code>Request</code> resource represents the date the request was <strong>sent</strong> by the client.</p>
<div class="example">
<p><strong>Example 2.3:</strong> A <code>Request</code> resource.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xml:base="http://example.org/reqs#">
<http:Request rdf:ID="reqs0">
<http:abs_path>/</http:abs_path>
<http:methodName>GET</http:methodName>
<http:method rdf:resource="http://www.w3.org/2008/http-methods#GET"/>
<http:response rdf:resource="#resp0"/>
<dc:date>2007-09-13</dc:date>
<http:httpVersion>1.1</http:httpVersion>
<http:headers rdf:parseType="Collection">
<http:MessageHeader rdf:about="#mh0"/>
<http:MessageHeader rdf:about="#mh1"/>
</http:headers>
</http:Request>
<http:MessageHeader rdf:ID="mh0"/>
<http:MessageHeader rdf:ID="mh1"/>
</rdf:RDF></pre>
</div>
<h4><a id="requestURIProperty" name="requestURIProperty">2.3.1. Request <acronym title="Uniform Resource Identifier">URI</acronym> Property</a></h4>
<p>The <code>requestURI</code> property represents the request <acronym title="Uniform Resource Identifier">URI</acronym> as specified in section 5.1.2 of [<a href="#ref-rfc2616"><acronym title="Request for Comments">RFC</acronym> 2616</a>]. The value of the property is either the constant value <code>http:asterisk</code> or a Literal value of the absolute <acronym title="Uniform Resource Identifier">URI</acronym>, the absolute path, or an authority. This vocabulary defines the following sub-properties to reference these values:</p>
<dl>
<dt><code>absoluteURI</code></dt>
<dd>Property to be used when the request URI is an absolute URI.</dd>
<dt><code>abs_path</code></dt>
<dd>Property to be used when the request URI is an absolute path.</dd>
<dt><code>authority</code></dt>
<dd>Property to be used when the request URI is an authority.</dd>
</dl>
<div class="example">
<p><strong>Example 2.4:</strong> The use of the <code>requestURI</code> property and its sub-properties.</p>
<pre><http:Request>
<http:methodName>OPTIONS</http:methodName>
<http:requestURI rdf:resource="http://www.w3.org/2006/http#asterisk"/>
...
</http:Request></pre><pre><http:Request>
<http:methodName>GET</http:methodName>
<http:absoluteURI>http://www.example.org:80/foo/bar</http:absoluteURI>
...
</http:Request></pre><pre><http:Request>
<http:methodName>GET</http:methodName>
<http:abs_path>/foo/bar</http:abs_path>
...
</http:Request></pre><pre><http:Request>
<http:methodName>CONNECT</http:methodName>
<http:authority>www.example.org:80</http:authority>
...
</http:Request></pre>
</div>
<h3><a id="responseClass" name="responseClass">2.4. Response Class</a></h3>
<p>The <code>Response</code> class is a subclass of the <a href="#messageClass"><code>Message</code> class</a>. A resource of this type represents an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> response as defined in [<a href="#ref-rfc2616"><acronym title="Request for Comments">RFC</acronym> 2616</a>]. Additional to the properties mentioned in <a href="#messageClass">2.2 Message Class</a>, the following properties may appear in resources of type <code>Response</code>:</p>
<dl>
<dt><code>statusCodeNumber</code></dt>
<dd>Property representing the status code sent by the server as a Literal.</dd>
<dt><code>statusCode</code></dt>
<dd>Property pointing to a <code>StatusCode</code> resource representing the status code (optional, see <a href="#statusCodes">3.2. Status Codes</a>).</dd>
<dt><code>reasonPhrase</code></dt>
<dd>Property representing the reason phrase sent by the server as a Literal.</dd>
</dl>
<p><a id="dateResp" name="dateResp">The <code>dc:date</code> property</a> when used in a <code>Response</code> resource represents the date the response was <strong>received</strong> by the client.</p>
<div class="example">
<p><strong>Example 2.5:</strong> A <code>Response</code> resource.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cnt="http://www.w3.org/2007/content#"
xml:base="http://example.org/resp#">
<http:Response rdf:ID="resp0">
<http:httpVersion>1.1</http:httpVersion>
<dc:date>2008-01-11</dc:date>
<http:statusCodeNumber>200</http:statusCodeNumber>
<http:statusCode rdf:resource="http://www.w3.org/2008/http-statusCodes#statusCode200"/>
<http:headers rdf:parseType="Collection">
<http:MessageHeader rdf:about="#mh0"/>
<http:MessageHeader rdf:about="#mh1"/>
</http:headers>
<http:body>
<cnt:Content rdf:ID="cont0"/>
</http:body>
</http:Response>
<http:MessageHeader rdf:ID="mh1"/>
<http:MessageHeader rdf:ID="mh0"/>
</rdf:RDF></pre>
</div>
<h3><a id="messageHeaderClass" name="messageHeaderClass">2.5. MessageHeader Class</a></h3><p>A resource of type <code>MessageHeader</code> represents an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> header. The following properties may appear in resources of type <code>MessageHeader</code>:</p>
<dl>
<dt><code>fieldName</code></dt>
<dd>Property representing the header name as a Literal.</dd>
<dt><code>headerName</code></dt>
<dd>Property pointing to a <code>HeaderName</code> resource representing the header name (optional, see <a href="#headerNames">3.4. Header Names</a>).</dd>
<dt><code>fieldValue</code></dt>
<dd>Property representing the header value as a Literal.</dd>
<dt><code>headerElements</code></dt>
<dd>Property representing the header value as a Collection of <a href="#headerElementClass"><code>HeaderElement</code></a> resources (optional).</dd>
</dl>
<div class="example">
<p><strong>Example 2.6:</strong> A <code>MessageHeader</code> resource.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xml:base="http://example.org/mh#">
<http:MessageHeader rdf:ID="mh0">
<http:fieldValue>text/html, image/png, image/gif;q=0.8</http:fieldValue>
<http:fieldName>Accept</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#accept"/>
<http:headerElements rdf:parseType="Collection">
<http:HeaderElement rdf:about="#he0"/>
<http:HeaderElement rdf:about="#he1"/>
<http:HeaderElement rdf:about="#he2"/>
</http:headerElements>
</http:MessageHeader>
<http:HeaderElement rdf:ID="he0"/>
<http:HeaderElement rdf:ID="he2"/>
<http:HeaderElement rdf:ID="he1"/>
</rdf:RDF></pre>
</div>
<h3><a id="headerElementClass" name="headerElementClass">2.6. HeaderElement Class</a></h3>
<p>A resource of type <code>HeaderElement</code> represents an element in a header value. The following properties may appear in resources of type <code>HeaderElement</code>:</p>
<dl>
<dt><code>elementName</code></dt>
<dd>Property representing the header element name as a Literal.</dd>
<dt><code>elementValue</code></dt>
<dd>Property representing the header element value as a Literal (optional).</dd>
<dt><code>params</code></dt>
<dd>Property representing header element parameters as a Collection of <a href="#paramClass"><code>Param</code></a> resources (optional).</dd>
</dl>
<div class="example">
<p><strong>Example 2.7:</strong> A <code>HeaderElement</code> resource.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xml:base="http://example.org/he#">
<http:HeaderElement rdf:ID="he0">
<http:elementName>image/gif</http:elementName>
<http:params rdf:parseType="Collection">
<http:Param rdf:ID="param0"/>
</http:params>
</http:HeaderElement>
</rdf:RDF></pre>
</div>
<h3><a id="paramClass" name="paramClass">2.7. Param Class</a></h3>
<p>A resource of type <code>Param</code> represents an element in a header value parameter. The following properties may appear in resources of type <code>Param</code>:</p>
<dl>
<dt><code>paramName</code></dt>
<dd>Property representing the parameter name as a Literal.</dd>
<dt><code>paramValue</code></dt>
<dd>Property representing the parameter value as a Literal.</dd>
</dl>
<div class="example">
<p><strong>Example 2.8:</strong> A <code>Param</code> resource.</p>
<pre><rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xml:base="http://example.org/param#">
<http:Param rdf:ID="param0">
<http:paramName>q</http:paramName>
<http:paramValue>0.8</http:paramValue>
</http:Param>
</rdf:RDF></pre>
</div>
<h2><a id="predefined" name="predefined">3. Predefined Values</a></h2>
<p>This section defines <acronym title="Resource Description Framework">RDF</acronym> terms for the predefined resources representing values used in <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 1.1 specification according to [<a href="#ref-rfc2616"><acronym title="Request for Comments">RFC</acronym> 2616</a>] or other specifications. A comprehensive example of using these predefined values together with the classes and properties provided in the previous section can be found in <a href="#example">Appendix C: Practical Example</a>.</p>
<h3><a id="methods" name="methods">3.1. Request Methods</a></h3>
<p>The <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 1.1 specification defines eight methods: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT. The resource at <code>http://www.w3.org/2006/http-methods</code> provides <code>Method</code> resources for each of these to be used as objects for the <code>method</code> property. A resource of type <code>Method</code> represents the name of a method used with <acronym title="Hyper Text Transfer Protocol">HTTP</acronym>.</p>
<h3><a id="statusCodes" name="statusCodes">3.2. Status Codes</a></h3>
<p><a href="#ref-status-codes">[HTTP Status Codes]</a> is a registry for status codes too be used in <acronym title="Hyper Text Transfer Protocol">HTTP</acronym>. The resource at <code>http://www.w3.org/2006/http-statusCodes</code> provides <code>StatusCode</code> resources for each of these to be used as objects for the <code>statusCode</code> property. A resource of type <code>StatusCode</code> represents a status code.</p>
<h3><a id="statusCodeGroups" name="statusCodeGroups">3.3. Status Code Groups</a></h3>
<p>Status codes in <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> may be grouped. The resource at <code>http://www.w3.org/2006/http-statusCodes</code> provides <code>StatusCodeGroup</code> resources for some groupings of status codes. A resource of type <code>StatusCodeGroup</code> represents a group of status codes.</p>
<h3><a id="headerNames" name="headerNames">3.4. Header Names</a></h3>
<p>Header names to be used in <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> are registered by the <acronym title="Internet Assigned Numbers Authority">IANA</acronym> (see <a href="#ref-rfc4229">[RFC4229]</a>, <a href="#ref-permheaders">[Permanent Headers]</a>, and <a href="#ref-provheaders">[Provisional Headers]</a>). The resource at <code>http://www.w3.org/2006/http-header</code> provides <code>HeaderName</code> resources for each of these to be used as objects for the <code>headerName</code> property. A resource of type <code>HeaderName</code> represents the name of a header used with <acronym title="Hyper Text Transfer Protocol">HTTP</acronym>.</p>
<h2><a id="schema" name="schema">Appendix A: Schema in <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym></a></h2>
<pre><?xml version="1.0"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xml:base="http://www.w3.org/2006/http">
<rdf:Description rdf:about="#">
<rdfs:comment xml:lang="en">A namespace for describing HTTP messages (http://www.w3.org/Protocols/rfc2616/rfc2616.html)</rdfs:comment>
</rdf:Description>
<owl:Ontology rdf:about="">
<owl:imports rdf:resource="http://purl.org/dc/dcam/"/>
<owl:imports rdf:resource="http://purl.org/dc/elements/1.1/"/>
</owl:Ontology>
<!-- Classes -->
<rdfs:Class rdf:about="#Connection">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#requests"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#connectionAuthority"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:comment xml:lang="en">The connection</rdfs:comment>
<rdfs:label xml:lang="en">Connection</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#HeaderElement">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#params"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#elementValue"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#elementName"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">The header element</rdfs:comment>
<rdfs:label xml:lang="en">Header element</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#HeaderName">
<rdfs:comment xml:lang="en">The header name</rdfs:comment>
<rdfs:label xml:lang="en">Header name</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#Message">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#body"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#headers"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="http://purl.org/dc/elements/1.1/date"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#httpVersion"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:comment xml:lang="en">The HTTP message</rdfs:comment>
<rdfs:label xml:lang="en">Message</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#MessageHeader">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#headerElements"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#fieldValue"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#headerName"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#fieldName"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">The message header</rdfs:comment>
<rdfs:label xml:lang="en">Message header</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#Method">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:comment xml:lang="en">The HTTP method</rdfs:comment>
<rdfs:label xml:lang="en">Method</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#Param">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#paramValue"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#paramName"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">The field value parameter</rdfs:comment>
<rdfs:label xml:lang="en">Parameter</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#Request">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#response"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#requestURI"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#method"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#methodName"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
>1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:subClassOf rdf:resource="#Message"/>
<rdfs:comment xml:lang="en">The request</rdfs:comment>
<rdfs:label xml:lang="en">Request</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#Response">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#reasonPhrase"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#statusCode"/>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:isDefinedBy>
<rdf:Description rdf:about="http://www.rfc-editor.org/rfc/rfc2616.txt">
<dc:identifier>http://www.rfc-editor.org/rfc/rfc2616.txt</dc:identifier>
<dc:title xml:lang="en">Hypertext Transfer Protocol -- HTTP/1.1</dc:title>
</rdf:Description>
</rdfs:isDefinedBy>
<rdfs:subClassOf rdf:resource="#Message"/>
<rdfs:comment xml:lang="en">The response</rdfs:comment>
<rdfs:label xml:lang="en">Response</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#StatusCode">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:comment xml:lang="en">The status code</rdfs:comment>
<rdfs:label xml:lang="en">Status code</rdfs:label>
</rdfs:Class>
<rdfs:Class rdf:about="#StatusCodeGroup">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:comment xml:lang="en">The tatus code group</rdfs:comment>
<rdfs:label xml:lang="en">Status code group</rdfs:label>
</rdfs:Class>
<!-- Properties -->
<rdf:Property rdf:about="#absoluteURI">
<rdfs:subPropertyOf rdf:resource="#requestURI"/>
<rdfs:comment xml:lang="en">The absolute request URI</rdfs:comment>
<rdfs:label xml:lang="en">Absolute URI</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#abs_path">
<rdfs:subPropertyOf rdf:resource="#requestURI"/>
<rdfs:comment xml:lang="en">The absolute path sort of request URI</rdfs:comment>
<rdfs:label xml:lang="en">Absolute path</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#authority">
<rdfs:subPropertyOf rdf:resource="#requestURI"/>
<rdfs:comment xml:lang="en">The authority sort of request URI</rdfs:comment>
<rdfs:label xml:lang="en">Authority</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#body">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:domain rdf:resource="#Message"/>
<rdfs:comment xml:lang="en">The message body; cnt:Content or rdf:Alt/rdf:Bag of cnt:Content</rdfs:comment>
<rdfs:label xml:lang="en">Body</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#connectionAuthority">
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#Connection"/>
<rdfs:comment xml:lang="en">The connection authority</rdfs:comment>
<rdfs:label xml:lang="en">Connection authority</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#elementName">
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#HeaderElement"/>
<rdfs:comment xml:lang="en">The header element name</rdfs:comment>
<rdfs:label xml:lang="en">Element name</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#elementValue">
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#HeaderElement"/>
<rdfs:comment xml:lang="en">The header element value</rdfs:comment>
<rdfs:label xml:lang="en">Element value</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#fieldName">
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#MessageHeader"/>
<rdfs:comment xml:lang="en">The field name; literal header name</rdfs:comment>
<rdfs:label xml:lang="en">Field name</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#fieldValue">
<rdfs:domain rdf:resource="#MessageHeader"/>
<rdfs:comment xml:lang="en">The field value; rdfs:Literal or http:HeaderElement</rdfs:comment>
<rdfs:label xml:lang="en">Field value</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#headerElements">
<rdfs:domain rdf:resource="#MessageHeader"/>
<rdfs:comment xml:lang="en">The header elements; (RDF collection of) http:HeaderElement</rdfs:comment>
<rdfs:label xml:lang="en">Header elements</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#headerName">
<rdfs:range rdf:resource="#HeaderName"/>
<rdfs:domain rdf:resource="#MessageHeader"/>
<rdfs:comment xml:lang="en">The header name; interpreted field name</rdfs:comment>
<rdfs:label xml:lang="en">Header name</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#headers">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:domain rdf:resource="#Message"/>
<rdfs:comment xml:lang="en">The headers; (RDF collection of) http:MessageHeader</rdfs:comment>
<rdfs:label xml:lang="en">Headers</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#httpVersion">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#Message"/>
<rdfs:comment xml:lang="en">The HTTP version</rdfs:comment>
<rdfs:label xml:lang="en">HTTP version</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#method">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:range rdf:resource="#Method"/>
<rdfs:domain rdf:resource="#Request"/>
<rdfs:comment xml:lang="en">The HTTP method</rdfs:comment>
<rdfs:label xml:lang="en">Method</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#methodName">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#Request"/>
<rdfs:comment xml:lang="en">The HTTP method name</rdfs:comment>
<rdfs:label xml:lang="en">Method name</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#paramName">
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#Param"/>
<rdfs:comment xml:lang="en">The header parameter name</rdfs:comment>
<rdfs:label xml:lang="en">Header parameter name</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#paramValue">
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#Param"/>
<rdfs:comment xml:lang="en">The header parameter value</rdfs:comment>
<rdfs:label xml:lang="en">Header parameter value</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#params">
<rdfs:domain rdf:resource="#HeaderElement"/>
<rdfs:comment xml:lang="en">The header parameters; (RDF collection of) http:Param</rdfs:comment>
<rdfs:label xml:lang="en">Header parameters</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#reasonPhrase">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#Response"/>
<rdfs:comment xml:lang="en">The reason phrase (status text)</rdfs:comment>
<rdfs:label xml:lang="en">Reason phrase</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#requests">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:domain rdf:resource="#Connection"/>
<rdfs:comment xml:lang="en">The HTTP requests; (RDF collection of) http:Request</rdfs:comment>
<rdfs:label xml:lang="en">Requests</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#requestURI">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:domain rdf:resource="#Request"/>
<rdfs:comment xml:lang="en">The request URI; rdfs:Literal or http://www.w3.org/2006/http#asterisk</rdfs:comment>
<rdfs:label xml:lang="en">Request URI</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#response">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:range rdf:resource="#Response"/>
<rdfs:domain rdf:resource="#Request"/>
<rdfs:comment xml:lang="en">The HTTP response</rdfs:comment>
<rdfs:label xml:lang="en">Response</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#statusCode">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:range rdf:resource="#StatusCode"/>
<rdfs:domain rdf:resource="#Response"/>
<rdfs:comment xml:lang="en">The HTTP status code</rdfs:comment>
<rdfs:label xml:lang="en">Status code</rdfs:label>
</rdf:Property>
<rdf:Property rdf:about="#statusCodeNumber">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
<rdfs:domain rdf:resource="#Response"/>
<rdfs:comment xml:lang="en">The HTTP status code number; rdfs:Literal (typed: 3digit)</rdfs:comment>
<rdfs:label xml:lang="en">Status code</rdfs:label>
</rdf:Property>
<rdf:Description rdf:about="#asterisk">
<rdfs:isDefinedBy rdf:resource="http://www.rfc-editor.org/rfc/rfc2616.txt"/>
<dc:description xml:lang="en">The asterisk as a request URI</dc:description>
<dc:title xml:lang="en">Asterisk</dc:title>
</rdf:Description>
</rdf:RDF></pre>
<h2><a id="terms" name="terms">Appendix B: Vocabulary Terms</a></h2>
<p>The following terms are defined by this specification:</p>
<h3><a id="terms-classes" name="terms-classes">Classes</a></h3>
<table>
<caption>Classes in the HTTP namespace</caption>
<thead>
<tr>
<th scope="col">Class name</th>
<th scope="col">Label</th>
<th scope="col">Allowable types</th>
<th scope="col">Required properties</th>
<th scope="col">Optional properties</th>
</tr>
</thead>
<tbody>
<tr id="terms-classes-Connection">
<td scope="row"><code>http:Connection</code></td>
<td>Connection</td>
<td></td>
<td><a href="#terms-properties-connectionAuthority"><code>http:connectionAuthority</code></a></td>
<td><a href="#terms-properties-requests"><code>http:requests</code></a></td>
</tr>
<tr id="terms-classes-HeaderElement">
<td scope="row"><code>http:HeaderElement</code></td>
<td>Header Element</td>
<td></td>
<td><a href="#terms-properties-elementName"><code>http:elementName</code></a></td>
<td><a href="#terms-properties-elementValue"><code>http:elementValue</code></a>, <a href="#terms-properties-params"><code>http:params</code></a></td>
</tr>
<tr id="terms-classes-HeaderName">
<td scope="row"><code>http:HeaderName</code></td>
<td>Header Name</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr id="terms-classes-Message">
<td scope="row"><code>http:Message</code></td>
<td>Message</td>
<td><a href="#terms-classes-Request">http:Request</a>, <a href="#terms-classes-Response">http:Response</a></td>
<td><a href="#terms-properties-httpVersion"><code>http:httpVersion</code></a></td>
<td><code>dc:date</code>, <a href="#terms-properties-body"><code>http:body</code></a>, <a href="#terms-properties-headers"><code>http:headers</code></a></td>
</tr>
<tr id="terms-classes-MessageHeader">
<td scope="row"><code>http:MessageHeader</code></td>
<td>Message header</td>
<td></td>
<td><a href="#terms-properties-fieldName"><code>http:fieldName</code></a>, <a href="#terms-properties-fieldValue"><code>http:fieldValue</code></a></td>
<td><a href="#terms-properties-headerName"><code>http:headerName</code></a>, <a href="#terms-properties-headerElements"><code>http:headerElements</code></a></td>
</tr>
<tr id="terms-classes-Method">
<td scope="row"><code>http:Method</code></td>
<td>Method</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr id="terms-classes-Param">
<td scope="row"><code>http:Param</code></td>
<td>Parameter</td>
<td></td>
<td><a href="#terms-properties-paramName"><code>http:paramName</code></a>, <a href="#terms-properties-paramValue"><code>http:paramValue</code></a></td>
<td></td>
</tr>
<tr id="terms-classes-Request">
<td scope="row"><code>http:Request</code></td>
<td>Request</td>
<td></td>
<td><a href="#terms-properties-methodName"><code>http:methodName</code></a>, <a href="#terms-properties-requestURI"><code>http:requestURI</code></a></td>
<td><a href="#terms-properties-method"><code>http:method</code></a>, <a href="#terms-properties-response"><code>http:response</code></a></td>
</tr>
<tr id="terms-classes-Response">
<td scope="row"><code>http:Response</code></td>
<td>Response</td>
<td></td>
<td><a href="#terms-properties-statusCodeNumber"><code>http:statusCodeNumber</code></a>, <a href="#terms-properties-reasonPhrase"><code>http:reasonPhrase</code></a></td>
<td><a href="#terms-properties-statusCode"><code>http:statusCode</code></a></td>
</tr>
<tr id="terms-classes-StatusCode">
<td scope="row"><code>http:StatusCode</code></td>
<td>Status Code</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr id="terms-classes-StatusCodeGroup">
<td scope="row"><code>http:StatusCodeGroup</code></td>
<td>Status Code Group</td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>
<h3><a id="terms-properties" name="terms-properties">Properties</a></h3>
<table>
<caption>Properties in the HTTP namespace</caption>
<thead>
<tr>
<th scope="col">Property name</th>
<th scope="col">Label</th>
<th scope="col">Domain</th>
<th scope="col">Range</th>
<th>Restriction</th>
</tr>
</thead>
<tbody>
<tr id="terms-properties-body">
<td scope="row"><code>http:body</code></td>
<td>Entity body</td>
<td><a href="#terms-classes-Message"><code>http:Message</code></a></td>
<td><code>cnt:Content</code></td>
<td></td>
</tr>
<tr id="terms-properties-connectionAuthority">
<td scope="row"><code>http:connectionAuthority</code></td>
<td>Connection authority</td>
<td><a href="#terms-classes-Connection"><code>http:Connection</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Connection</code></td>
</tr>
<tr id="terms-properties-elementName">
<td scope="row"><code>http:elementName</code></td>
<td>Header element name</td>
<td><a href="#terms-classes-HeaderElement"><code>http:HeaderElement</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:HeaderElement</code></td>
</tr>
<tr id="terms-properties-elementValue">
<td scope="row"><code>http:elementValue</code></td>
<td>Header element value</td>
<td><a href="#terms-classes-HeaderElement"><code>http:HeaderElement</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:HeaderElement</code></td>
</tr>
<tr id="terms-properties-fieldName">
<td scope="row"><code>http:fieldName</code></td>
<td>Field name</td>
<td><a href="#terms-classes-MessageHeader"><code>http:MessageHeader</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:MessageHeader</code></td>
</tr>
<tr id="terms-properties-fieldValue">
<td scope="row"><code>http:fieldValue</code></td>
<td>Field value</td>
<td><a href="#terms-classes-MessageHeader"><code>http:MessageHeader</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:MessageHeader</code></td>
</tr>
<tr id="terms-properties-headerElements">
<td scope="row"><code>http:headerElements</code></td>
<td>Header elements</td>
<td><a href="#terms-classes-MessageHeader"><code>http:MessageHeader</code></a></td>
<td>Collection of <a href="#terms-classes-HeaderElement"><code>http:HeaderElement</code></a></td>
<td>At most one per <code>http:MessageHeader</code></td>
</tr>
<tr id="terms-properties-headerName">
<td scope="row"><code>http:headerName</code></td>
<td>Header name</td>
<td><a href="#terms-classes-MessageHeader"><code>http:MessageHeader</code></a></td>
<td><a href="#terms-classes-HeaderName"><code>http:HeaderName</code></a></td>
<td>At most one per <code>http:MessageHeader</code></td>
</tr>
<tr id="terms-properties-headers">
<td scope="row"><code>http:headers</code></td>
<td>Headers</td>
<td><a href="#terms-classes-Message"><code>http:Message</code></a></td>
<td>Collection of <a href="#terms-classes-MessageHeader"><code>http:MessageHeader</code></a></td>
<td>At most one per <code>http:Message</code></td>
</tr>
<tr id="terms-properties-httpVersion">
<td scope="row"><code>http:httpVersion</code></td>
<td>HTTP Version</td>
<td><a href="#terms-classes-Message"><code>http:Message</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Message</code></td>
</tr>
<tr id="terms-properties-method">
<td scope="row"><code>http:method</code></td>
<td>Header name</td>
<td><a href="#terms-classes-Request"><code>http:Request</code></a></td>
<td><a href="#terms-classes-Method"><code>http:Method</code></a></td>
<td>At most one per <code>http:Request</code></td>
</tr>
<tr id="terms-properties-methodName">
<td scope="row"><code>http:methodName</code></td>
<td>Field name</td>
<td><a href="#terms-classes-Request"><code>http:Request</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Request</code></td>
</tr>
<tr id="terms-properties-paramName">
<td scope="row"><code>http:paramName</code></td>
<td>Parameter name</td>
<td><a href="#terms-classes-Param"><code>http:Param</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Param</code></td>
</tr>
<tr id="terms-properties-params">
<td scope="row"><code>http:params</code></td>
<td>Parameters</td>
<td><a href="#terms-classes-HeaderElement"><code>http:HeaderElement</code></a></td>
<td>Collection of <a href="#terms-classes-Param"><code>http:Param</code></a></td>
<td>At most one per <code>http:HeaderElement</code></td>
</tr>
<tr id="terms-properties-paramValue">
<td scope="row"><code>http:paramValue</code></td>
<td>Parameter value</td>
<td><a href="#terms-classes-Param"><code>http:Param</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Param</code></td>
</tr>
<tr id="terms-properties-reasonPhrase">
<td scope="row"><code>http:reasonPhrase</code></td>
<td>Reason phrase</td>
<td><a href="#terms-classes-Response"><code>http:Response</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Response</code></td>
</tr>
<tr id="terms-properties-requests">
<td scope="row"><code>http:requests</code></td>
<td>Requests</td>
<td><a href="#terms-classes-Connection"><code>http:Connection</code></a></td>
<td>Collection of <a href="#terms-classes-Request"><code>http:Request</code></a></td>
<td>At most one per <code>http:Connection</code></td>
</tr>
<tr id="terms-properties-requestURI">
<td scope="row"><code>http:requestURI</code></td>
<td>Request URI</td>
<td><a href="#terms-classes-Request"><code>http:Request</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Request</code></td>
</tr>
<tr id="terms-properties-response">
<td scope="row"><code>http:response</code></td>
<td>Response</td>
<td><a href="#terms-classes-Request"><code>http:Request</code></a></td>
<td><a href="#terms-classes-Response"><code>http:Response</code></a></td>
<td>At most one per <code>http:Request</code></td>
</tr>
<tr id="terms-properties-statusCode">
<td scope="row"><code>http:statusCode</code></td>
<td>Status code</td>
<td><a href="#terms-classes-Response"><code>http:Response</code></a></td>
<td><a href="#terms-classes-StatusCode"><code>http:StatusCode</code></a></td>
<td>At most one per <code>http:Response</code></td>
</tr>
<tr id="terms-properties-statusCodeNumber">
<td scope="row"><code>http:statusCodeNumber</code></td>
<td>Status code number</td>
<td><a href="#terms-classes-Response"><code>http:Response</code></a></td>
<td>RDF Literal</td>
<td>Exactly one per <code>http:Response</code></td>
</tr>
</tbody>
</table>
<h3><a id="terms-values" name="terms-values">Values</a></h3>
<table>
<caption>Values in the HTTP namespace</caption>
<thead>
<tr>
<th scope="col">Value Name</th>
<th scope="col">Label</th>
<th scope="col">Used in</th>
<th scope="col">Description</th>
</tr>
</thead>
<tbody>
<tr id="terms-values-asterisk">
<td scope="row"><code>http:asterisk</code></td>
<td>Asterisk</td>
<td><a href="#terms-properties-requestURI"><code>http:requestURI</code></a></td>
<td>An asterisk used as request URI</td>
</tr>
</tbody>
</table>
<h2><a id="example" name="example">Appendix C: Practical Example</a></h2>
<p>The following example shows an <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym> representation of an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> request and response pair.</p>
<h3><a id="scenario" name="scenario">Scenario Description</a></h3>
<p>A client sends two requests to a server at <code>www.example.org</code> port 80 via <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 1.1 GET. With each request, it sends request headers. The first request is for a resource in the document root (<code>/</code>), the second for a resource at <code>/image</code>. While handling the second request the server performs content negotiation respecting the request's <code>Accept</code> header and so sends a PNG image. This is indicated by the response's <code>Vary</code> header.</p>
<h3><a id="code" name="code">Resulting <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym></a></h3>
<pre><?xml version="1.0" encoding="utf-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#"
xmlns:cnt="http://www.w3.org/2007/content#">
<http:Connection rdf:ID="conn">
<http:connectionAuthority>www.example.org:80</http:connectionAuthority>
<http:requests rdf:parseType="Collection">
<http:Request rdf:about="#req0"/>
<http:Request rdf:about="#req1"/>
</http:requests>
</http:Connection>
<http:Request rdf:about="#req0">
<http:httpVersion>1.1</http:httpVersion>
<http:methodName>GET</http:methodName>
<http:method rdf:resource="http://www.w3.org/2008/http-methods#GET"/>@@@TBD@@@
<http:abs_path>/</http:abs_path>
<http:headers rdf:parseType="Collection">
<http:MessageHeader>
<http:fieldName>Host</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#host"/>@@@TBD@@@
<http:fieldValue>www.example.org</http:fieldValue>
</http:MessageHeader>
<http:MessageHeader>
<http:fieldName>User-Agent</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#user-agent"/>@@@TBD@@@
<http:fieldValue>My User Agent</http:fieldValue>
</http:MessageHeader>
<http:MessageHeader>
<http:fieldName>Accept</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#accept"/>@@@TBD@@@
<http:fieldValue>text/html, image/png, image/gif;q=0.8</http:fieldValue>
<http:headerElements rdf:parseType="Collection">
<http:HeaderElement>
<http:elementName>text/html</http:elementName>
</http:HeaderElement>
<http:HeaderElement>
<http:elementName>image/png</http:elementName>
</http:HeaderElement>
<http:HeaderElement>
<http:elementName>image/gif</http:elementName>
<http:params rdf:parseType="Collection">
<http:Param>
<http:paramName>q</http:paramName>
<http:paramValue>0.8</http:paramValue>
</http:Param>
</http:params>
</http:HeaderElement>
</http:headerElements>
</http:MessageHeader>
</http:headers>
<http:response rdf:resource="#resp0"/>
</http:Request>
<http:Request rdf:about="#req1">
<http:httpVersion>1.1</http:httpVersion>
<http:methodName>GET</http:methodName>
<http:method rdf:resource="http://www.w3.org/2008/http-methods#GET"/>@@@TBD@@@
<http:abs_path>/image</http:abs_path>
<http:headers rdf:parseType="Collection">
<http:MessageHeader>
<http:fieldName>Host</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#host"/>@@@TBD@@@
<http:fieldValue>www.example.org</http:fieldValue>
</http:MessageHeader>
<http:MessageHeader>
<http:fieldName>User-Agent</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#user-agent"/>@@@TBD@@@
<http:fieldValue>My User Agent</http:fieldValue>
</http:MessageHeader>
<http:MessageHeader>
<http:fieldName>Accept</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#accept"/>@@@TBD@@@
<http:fieldValue>image/png, image/gif;q=0.8</http:fieldValue>
<http:headerElements rdf:parseType="Collection">
<http:HeaderElement>
<http:elementName>image/png</http:elementName>
</http:HeaderElement>
<http:HeaderElement>
<http:elementName>image/gif</http:elementName>
<http:params rdf:parseType="Collection">
<http:Param>
<http:paramName>q</http:paramName>
<http:paramValue>0.8</http:paramValue>
</http:Param>
</http:params>
</http:HeaderElement>
</http:headerElements>
</http:MessageHeader>
</http:headers>
<http:response rdf:resource="#resp1"/>
</http:Request>
<http:Response rdf:ID="resp0">
<http:httpVersion>1.1</http:httpVersion>
<http:statusCodeNumber>200</http:statusCodeNumber>
<http:statusCode rdf:resource="http://www.w3.org/2008/http-statusCodes#200"/>@@@TBD@@@
<http:reasonPhrase>OK</http:reasonPhrase>
<http:headers rdf:parseType="Collection">
<http:MessageHeader>
<http:fieldName>Date</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#date"/>@@@TBD@@@
<http:fieldValue>.......</http:fieldValue>
</http:MessageHeader>
<http:MessageHeader>
<http:fieldName>Content-Type</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#content-type"/>@@@TBD@@@
<http:fieldValue>text/html; charset=utf-8</http:fieldValue>
<http:headerElements rdf:parseType="Collection">
<http:HeaderElement>
<http:elementName>text/html</http:elementName>
<http:params rdf:parseType="Collection">
<http:Param>
<http:paramName>charset</http:paramName>
<http:paramValue>utf-8</http:paramValue>
</http:Param>
</http:params>
</http:HeaderElement>
</http:headerElements>
</http:MessageHeader>
</http:headers>
<http:body>
<cnt:XMLContent>
<cnt:xmlLeadingMisc rdf:parseType="Literal"><!-- This is the start of the document -->
</cnt:xmlLeadingMisc>
<cnt:docTypeDecl>
<cnt:DocTypeDecl>
<cnt:dtdName>html</cnt:dtdName>
<cnt:publicId>-//W3C//DTD XHTML 1.0 Strict//EN</cnt:publicId>
<cnt:systemId rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</cnt:systemId>
</cnt:DocTypeDecl>
</cnt:docTypeDecl>
<cnt:xmlRest rdf:parseType="Literal"><html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<title>My document</title>
</head>
<body>
<p><!-- ...... --></p>
</body>
</html></cnt:xmlRest>
</cnt:XMLContent>
</http:body>
</http:Response>
<http:Response rdf:ID="resp1">
<http:httpVersion>1.1</http:httpVersion>
<http:statusCodeNumber>200</http:statusCodeNumber>
<http:statusCode rdf:resource="http://www.w3.org/2008/http-statusCodes#200"/>@@@TBD@@@
<http:reasonPhrase>OK</http:reasonPhrase>
<http:headers rdf:parseType="Collection">
<http:MessageHeader>
<http:fieldName>Date</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#date"/>@@@TBD@@@
<http:fieldValue>.......</http:fieldValue>
</http:MessageHeader>
<http:MessageHeader>
<http:fieldName>Content-Type</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#content-type"/>@@@TBD@@@
<http:fieldValue>image/png</http:fieldValue>
</http:MessageHeader>
<http:MessageHeader>
<http:fieldName>Vary</http:fieldName>
<http:headerName rdf:resource="http://www.w3.org/2008/http-header#vary"/>@@@TBD@@@
<http:fieldValue>accept</http:fieldValue>
<http:headerElements rdf:parseType="Collection">
<http:HeaderElement>
<http:elementName>accept</http:elementName>
</http:HeaderElement>
</http:headerElements>
</http:MessageHeader>
</http:headers>
<http:body>
<cnt:Base64Content>
<cnt:bytes rdf:datatype="http://www.w3.org/2001/XMLSchema#base64Binary">qouh3908t38hohfrf..........</cnt:bytes>
</cnt:Base64Content>
</http:body>
</http:Response>
</rdf:RDF></pre>
<h2><a id="references" name="references">Appendix D: References</a></h2>
<dl>
<dt><a id="ref-content-in-rdf" name="ref-content-in-rdf">[Content in RDF]</a></dt>
<dd><a href="http://www.w3.org/TR/Content-in-RDF/">Representing Content in RDF</a> - Johannes Koch, Carlos A Velasco (eds.). <acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 17 July 2008.</dd>
<dt><a id="ref-earl" name="ref-earl">[EARL]</a></dt>
<dd><a href="http://www.w3.org/WAI/intro/earl.php">Evaluation and Report Language (EARL) Overview</a> - <acronym title="World Wide Web Consortium">W3C</acronym></dd>
<dt><a id="ref-status-codes" name="ref-status-codes">[HTTP Status Codes]</a></dt>
<dd><a href="http://www.iana.org/assignments/http-status-codes">"HTTP Status Code Registry"</a> - <acronym title="Internet Assigned Numbers Authority">IANA</acronym>.</dd>
<dt><a id="ref-owl" name="ref-owl">[OWL]</a></dt>
<dd><a href="http://www.w3.org/2004/OWL/">Web Ontology Language (OWL) Overview</a> - <acronym title="World Wide Web Consortium">W3C</acronym></dd>
<dt><a id="ref-permheaders" name="ref-permheaders">[Permanent Headers]</a></dt>
<dd><a href="http://www.iana.org/assignments/message-headers/perm-headers.html">Permanent Message Header Field Names</a> - <acronym title="Internet Assigned Numbers Authority">IANA</acronym>.</dd>
<dt><a id="ref-provheaders" name="ref-provheaders">[Provisional Headers]</a></dt>
<dd><a href="http://www.iana.org/assignments/message-headers/prov-headers.html">Provisional Message Header Field Names</a> - <acronym title="Internet Assigned Numbers Authority">IANA</acronym>.</dd>
<dt><a id="ref-powder-dr" name="ref-powder-dr">[POWDER-DR]</a></dt>
<dd><a href="http://www.w3.org/TR/2008/WD-powder-dr-20080317/">Protocol for Web Description Resources (POWDER): Description Resources</a> - K. Smith, P. Archer, A. Perego (eds.). <acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 17 March 2008.</dd>
<dt><a id="ref-powder-gr" name="ref-powder-gr">[POWDER-GR]</a></dt>
<dd><a href="http://www.w3.org/TR/2008/WD-powder-grouping-20080324/">Protocol for Web Description Resources (POWDER): Grouping of Resources</a> - P. Archer, A. Perego, K. Smith (eds.). <acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 24 March 2008.</dd>
<dt><a id="ref-rdf" name="ref-rdf">[RDF]</a></dt>
<dd><a href="http://www.w3.org/RDF/">Resource Description Framework (RDF) Overview</a> - <acronym title="World Wide Web Consortium">W3C</acronym></dd>
<dt><a id="ref-rfc2119" name="ref-rfc2119">[<acronym title="Request For Comments">RFC</acronym>2119]</a></dt>
<dd>Request for Comments: 2119. <a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a> - <acronym title="Internet Engineering Task Force">IETF</acronym> March 1997.</dd>
<dt><a id="ref-rfc2616" name="ref-rfc2616">[RFC2616]</a></dt>
<dd><a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext Transfer Protocol -- HTTP/1.1</a> - R. Fielding, J. Gettys, J. Mogul, H. Frystyk Nielsen, L. Masinter, P. Leach and T. Berners-Lee. <acronym title="Internet Engineering Task Force">IETF</acronym> June 1999.</dd>
<dt><a id="ref-rfc4229" name="ref-rfc4229">[RFC4229]</a></dt>
<dd><a href="http://www.ietf.org/rfc/rfc4229.txt">HTTP Header Field Registrations</a> - M. Nottingham, J. Mogul. <acronym title="Internet Engineering Task Force">IETF</acronym> December 2005.</dd>
<dt><a id="ref-wcag" name="ref-wcag">[WCAG]</a></dt>
<dd><a href="http://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a> - <acronym title="World Wide Web Consortium">W3C</acronym>.</dd>
</dl>
<h2><a id="changes" name="changes">Appendix E: Document Changes</a></h2>
<p>Besides several editorial changes, the following is a list of substantial changes since the <a href="http://www.w3.org/TR/2007/WD-HTTP-in-RDF-20070323/">23 March, 2007 Working Draft</a>:</p>
<ul>
<li>split three RDF models for request methods, header names and status codes from the HTTP model to be updated separately from external registries</li>
<li>changed the http:request property to http:requests</li>
<li>introduced the http:Message class to be a base for the http:Request and http:Response class</li>
<li>changed the http:version property to http:httpVersion</li>
<li>added the dc:date property to the http:Message class</li>
<li>introduced the http:methodName (with object literal), http:method (with object resource from external RDF model for header names) properties and the http:Method class instead of different http:Request sub-classes</li>
<li>changed the multiple use of the http:header property to http:headers with an RDF collection</li>
<li>changed the http:responseCode property to http:statusCode (with object literal from external RDF model for status codes), and introduced the literal http:statusCodeNumber and http:reasonPhrase properties</li>
<li>changed the http:fieldName property to have a object literal</li>
<li>introduced the http:headerName property having an object resource (from the external RDF model for header names)</li>
</ul>
</body>
</html>