/
violations.xml
1722 lines (1602 loc) · 97.6 KB
/
violations.xml
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
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE violations SYSTEM 'violations.dtd'>
<violations>
<specification id="RDF" href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Graph-URIref">
<name>
Resource Description Framework (RDF):
Concepts and Abstract Syntax
</name>
<section>RDF URI References</section>
<require component="SCHEME"><text>representing an <em>absolute URI</em> with optional fragment identifier</text></require>
<bad>foo/bar</bad>
<bad>#frag</bad>
<bad>//example.org/foo/bar#frag</bad>
</specification>
<specification id="URI" rfc="3986">
<name>Uniform Resource Identifier (URI): Generic Syntax</name>
</specification>
<specification id="Unicode" href="http://www.unicode.org/">
<name>Unicode</name>
</specification>
<specification id="IRI" rfc="3987">
<name>Internationalized Resource Identifiers (IRIs)</name>
</specification>
<specification id="XML" href="http://www.w3.org/TR/2004/REC-xml-20040204/#dt-sysid">
<name>Extensible Markup Language (XML) 1.0 (Third Edition)</name>
<section>system identifier</section>
<prohibit component="FRAGMENT"><text>TODO</text></prohibit>
</specification>
<specification id="XLink" href="http://www.w3.org/TR/2001/REC-xlink-20010627/#link-locators">
<name>XML Linking Language (XLink) Version 1.0</name>
<section>Locator Attribute (href)</section>
</specification>
<specification id="Schema" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI">
<name>XML Schema Part 2: Datatypes Second Edition</name>
<section>anyURI</section>
</specification>
<specification id="URL_Registratrion" type="other" rfc="2717">
<name>
Registration Procedures for URL
Scheme Names</name>
</specification>
<scheme id="http" type="scheme" rfc="2616">
<name>Hypertext Transfer Protocol -- HTTP/1.1</name>
<defn section="3.2.2">
<pre>
http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
</pre>
</defn>
<complete/>
<dns/>
<port>80</port>
<prohibit component="USER"/>
<require component="HOST"/>
<good>http://www.example.org/foo/bar</good>
<bad>http://www.example.org:80/foo/bar</bad>
<bad>http:foo/bar</bad>
<bad>http://user@www.example.org/foo/bar</bad>
</scheme>
<scheme id="https" type="scheme" rfc="2818">
<name>Hypertext Transfer Protocol Secure</name>
<defn section="2.4">
HTTP/TLS is differentiated from HTTP URIs by using the 'https' protocol identifier in place of the 'http' protocol identifier.
</defn>
<defn ref="http" section="3.2.2">
<pre>
http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
</pre>
</defn>
<complete/>
<dns/>
<port>443</port>
<prohibit component="USER"/>
<require component="HOST"/>
<good>https://www.example.org/foo/bar</good>
<bad>https://www.example.org:443/foo/bar</bad>
<bad>https:foo/bar</bad>
<bad>https://user@www.example.org/foo/bar</bad>
</scheme>
<scheme id="ftp" type="scheme" rfc="1738" section="3.2">
<name>File Transfer Protocol</name>
<defn section="5">
<pre>
ftpurl = "ftp://" login [ "/" fpath [ ";type=" ftptype ]]
fpath = fsegment *[ "/" fsegment ]
fsegment = *[ uchar | "?" | ":" | "@" | "&amp;" | "=" ]
ftptype = "A" | "I" | "D" | "a" | "i" | "d"
</pre>
<pre>
login = [ user [ ":" password ] "@" ] hostport
</pre>
<pre>
safe = "$" | "-" | "_" | "." | "+"
extra = "!" | "*" | "'" | "(" | ")" | ","
escape = "%" hex hex
unreserved = alpha | digit | safe | extra
uchar = unreserved | escape
</pre>
</defn>
<complete/>
<dns/>
<port>21</port>
<require component="HOST" section="5"><text>
<pre>
ftpurl = "ftp://" login [ "/" fpath [ ";type=" ftptype ]]
login = [ user [ ":" password ] "@" ] hostport
</pre></text>
</require>
<pattern component="PATHQUERY" reserved="~;">[^;~]*(;@{mustLowerCase(type)}=@{shouldLowerCase([aid])}|)</pattern>
<good>ftp://user@example.org/foo/bar;type=d</good>
<bad>ftp:///foo/bar</bad>
<!--
<bad>ftp://user@example.org/foo/bar?type=d</bad>
-->
<bad>ftp://user@example.org/foo/bar;type=z</bad>
<bad>ftp://user@example.org/foo/b;ar;type=d</bad>
</scheme>
<scheme id="mailto" type="scheme" rfc="2368">
<name>Electronic mail address</name>
<prohibit component="AUTHORITY"><text>
<pre>
mailtoURL = "mailto:" [ to ] [ headers ]
to = #mailbox
headers = "?" header *( "&amp;" header )
header = hname "=" hvalue
hname = *urlc
hvalue = *urlc
</pre></text></prohibit>
</scheme>
<scheme id="news" type="scheme" rfc="1738" section="3.6">
<name>USENET news</name>
<defn section="5">
<pre>
newsurl = "news:" grouppart
grouppart = "*" | group | article
group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
article = 1*[ uchar | ";" | "/" | "?" | ":" | "&amp;" | "=" ] "@" host
</pre>
<pre>
safe = "$" | "-" | "_" | "." | "+"
extra = "!" | "*" | "'" | "(" | ")" | ","
escape = "%" hex hex
unreserved = alpha | digit | safe | extra
uchar = unreserved | escape
</pre>
</defn>
<complete/>
<prohibit component="AUTHORITY" section="5"><text>
<pre>
newsurl = "news:" grouppart
grouppart = "*" | group | article
group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
article = 1*[ uchar | ";" | "/" | "?" | ":" | "&amp;" | "=" ] "@" host
</pre>
</text></prohibit>
<require component="PATH" section="5"><text>
<pre>
newsurl = "news:" grouppart
grouppart = "*" | group | article
group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
article = 1*[ uchar | ";" | "/" | "?" | ":" | "&amp;" | "=" ] "@" host
</pre>
</text></require>
<pattern component="PATHQUERY" reserved="~@">[^@]+@@{host}|[*]|[a-zA-Z][-a-zA-Z0-9.+_]*</pattern>
<good>news:*</good>
<good>news:group.it</good>
<good>news:arb?itrary@news.example.org</good>
<good>news:arbitrary@news.example.org</good>
<bad>news:arbitrary@news.exampl<unicode>00E7</unicode>.org</bad>
<bad>news:arbitr?ary@news.exampl<unicode>00E7</unicode>.org</bad>
<bad>news:///foo/bar</bad>
<bad>news://user@example.org/foo</bad>
</scheme>
<scheme id="nntp" type="scheme" rfc="1738" section="3.7">
<name>USENET news using NNTP access</name>
<defn section="5">
<pre>
nntpurl = "nntp://" hostport "/" group [ "/" digits ]
</pre>
<pre>
group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
</pre>
</defn>
<complete/>
<dns/>
<port>119</port>
<prohibit component="QUERY"/>
<prohibit component="USER"/>
<require component="HOST"/>
<pattern component="PATH">/[a-zA-Z][-a-zA-Z0-9.+_]*(/[0-9]+)?</pattern>
<bad>nntp://user@example.org/foo</bad>
<bad>nntp:/foo</bad>
<bad>nntp:///foo</bad>
<bad>nntp://example.org/foo/4/3</bad>
<bad>nntp://example.org/</bad>
<bad>nntp://example.org/foo/</bad>
<bad>nntp://example.org/*</bad>
<good>nntp://example.org/foo4</good>
<good>nntp://example.org/foo/4</good>
</scheme>
<scheme id="telnet" type="scheme" rfc="4248">
<name>Reference to interactive sessions</name>
</scheme>
<scheme id="wais" type="scheme" rfc="4156">
<name>Wide Area Information Servers</name>
</scheme>
<scheme id="file" type="scheme" rfc="1738" section="3.10">
<name>Host-specific file names</name>
<defn section="5">
<pre>
fileurl = "file://" [ host | "localhost" ] "/" fpath
</pre>
<pre>
fpath = fsegment *[ "/" fsegment ]
fsegment = *[ uchar | "?" | ":" | "@" | "&amp;" | "=" ]
</pre>
<pre>
safe = "$" | "-" | "_" | "." | "+"
extra = "!" | "*" | "'" | "(" | ")" | ","
escape = "%" hex hex
unreserved = alpha | digit | safe | extra
uchar = unreserved | escape
</pre>
</defn>
<complete/>
<dns/>
<prohibit component="USER" section="5"><text>
<pre>
fileurl = "file://" [ host | "localhost" ] "/" fpath
</pre></text></prohibit>
<prohibit component="PORT" section="5"><text>
<pre>
fileurl = "file://" [ host | "localhost" ] "/" fpath
</pre></text></prohibit>
<require component="PATH" section="5"><text>
<pre>
fileurl = "file://" [ host | "localhost" ] "/" fpath
</pre></text></require>
<require component="AUTHORITY" section="5"><text>
<pre>
fileurl = "file://" [ host | "localhost" ] "/" fpath
</pre></text></require>
<pattern component="PATHQUERY" reserved="~;" >[^;~]*</pattern>
<bad>file://user@example.org/foo/bar</bad>
<bad>file://eg:4029/foo/bar</bad>
<bad>file:/foo/bar</bad>
<bad>file://example.org</bad>
<bad>file://foo/bar;t</bad>
<bad>file://foo/~jjc</bad>
<good>file:///foo/b</good>
<good>file:///foo/b?ar/yuk</good>
</scheme>
<scheme id="prospero" type="scheme" rfc="4157">
<name>Prospero Directory Service</name>
</scheme>
<scheme id="gopher" type="scheme" rfc="4266">
<name>The gopher URI scheme</name>
</scheme>
<scheme id="z39.50s" type="scheme" rfc="2056">
<name>Z39.50 Session</name>
</scheme>
<scheme id="z39.50r" type="scheme" rfc="2056">
<name>Z39.50 Retrieval</name>
</scheme>
<scheme id="cid" type="scheme" rfc="2392">
<name>content identifier</name>
</scheme>
<scheme id="mid" type="scheme" rfc="2392">
<name>message identifier</name>
</scheme>
<scheme id="vemmi" type="scheme" rfc="2122">
<name>versatile multimedia interface</name>
</scheme>
<scheme id="service" type="scheme" rfc="2609">
<name>service location</name>
</scheme>
<scheme id="imap" type="scheme" rfc="2192">
<name>internet message access protocol</name>
</scheme>
<scheme id="nfs" type="scheme" rfc="2224">
<name>network file system protocol</name>
</scheme>
<scheme id="acap" type="scheme" rfc="2244">
<name>application configuration access protocol</name>
</scheme>
<scheme id="rtsp" type="scheme" rfc="2326">
<name>real time streaming protocol</name>
</scheme>
<scheme id="tip" type="scheme" rfc="2371">
<name>Transaction Internet Protocol</name>
</scheme>
<scheme id="pop" type="scheme" rfc="2384">
<name>Post Office Protocol v3</name>
</scheme>
<scheme id="data" type="scheme" rfc="2397">
<name>data</name>
</scheme>
<scheme id="dav" type="scheme" rfc="2518">
<name>dav</name>
</scheme>
<scheme id="opaquelocktoken" type="scheme" rfc="2518">
<name>opaquelocktoken</name>
</scheme>
<scheme id="sip" type="scheme" rfc="3261">
<name>session initiation protocol</name>
</scheme>
<scheme id="sips" type="scheme" rfc="3261">
<name>secure session intitiaion protocol</name>
</scheme>
<scheme id="tel" type="scheme" rfc="2806">
<name>telephone</name>
</scheme>
<scheme id="fax" type="scheme" rfc="2806">
<name>fax</name>
</scheme>
<scheme id="modem" type="scheme" rfc="2806">
<name>modem</name>
</scheme>
<scheme id="soap.beep" type="scheme" rfc="3288">
<name>soap.beep</name>
</scheme>
<scheme id="soap.beeps" type="scheme" rfc="3288">
<name>soap.beeps</name>
</scheme>
<scheme id="xmlrpc.beep" type="scheme" rfc="3529">
<name>xmlrpc.beep</name>
</scheme>
<scheme id="xmlrpc.beeps" type="scheme" rfc="3529">
<name>xmlrpc.beeps</name>
</scheme>
<scheme id="urn" type="scheme" rfc="2141">
<name>Uniform Resource Names</name>
<defn section="2">
All URNs have the following syntax (phrases enclosed in quotes are REQUIRED):
<pre>
<URN&gt; ::= "urn:" <NID&gt; ":" <NSS&gt;
</pre>
</defn>
<defn section="2.1">
<pre>
<NID&gt; ::= <let-num&gt; [ 1,31<let-num-hyp&gt; ]
<let-num-hyp&gt; ::= <upper&gt; | <lower&gt; | <number&gt; | "-"
<let-num&gt; ::= <upper&gt; | <lower&gt; | <number&gt;
</pre>
</defn>
<defn section="2.2">
<pre>
<NSS&gt; ::= 1*<URN chars&gt;
<URN chars&gt; ::= <trans&gt; | "%" <hex&gt; <hex&gt;
<trans&gt; ::= <upper&gt; | <lower&gt; | <number&gt; | <other&gt; | <reserved&gt;
<other&gt; ::= "(" | ")" | "+" | "," | "-" | "." |
":" | "=" | "@" | ";" | "$" |
"_" | "!" | "*" | "'"
</pre>
</defn>
<defn section="2.3.2">
RFC 1630 [2] reserves the characters "/", "?", and "#" for particular purposes.
The URN-WG has not yet debated the applicability and precise semantics of those
purposes as applied to URNs. Therefore, these characters are RESERVED for future
developments. Namespace developers SHOULD NOT use these characters in unencoded form,
but rather use the appropriate %-encoding for each character.
</defn>
<prohibit component="AUTHORITY">
<text section="2">
<pre>
<URN&gt; ::= "urn:" <NID&gt; ":" <NSS&gt;
</pre>
</text>
<text section="2.1">
<pre>
<NID&gt; ::= <let-num&gt; [ 1,31<let-num-hyp&gt; ]
</pre>
</text></prohibit>
<prohibit component="QUERY" section="2.3.2"/>
<require component="PATH">
<text section="2">
<pre>
<URN&gt; ::= "urn:" <NID&gt; ":" <NSS&gt;
</pre>
</text></require>
<pattern component="PATH" reserved="/~">(?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{1,31}:.*</pattern>
<pattern compoentent="QUERY">[+=].*</pattern>
<good>urn:x-hp:foo<unicode>00E9</unicode></good>
<bad>urn:x-hp:foo/bar</bad>
<bad>urn:urn:foo</bad>
<good>urn:urn-1:foo</good>
<bad>urn://foo</bad>
<bad>urn:foo:bar?query</bad>
<bad>urn:foo:ff~</bad>
<todo>case of NIS</todo>
<todo>
registry of URNs, implement something of the NSS with Namespace specific rules.
</todo>
<todo>
To avoid confusion with the "urn:" identifier, the NID "urn" is reserved and MUST NOT be used.
</todo>
<todo>e-mail about frags in URNs</todo>
<todo>
In addition, octet 0 (0 hex) should NEVER be used, in either unencoded or %-encoded form.
</todo>
</scheme>
<scheme id="go" type="scheme" rfc="3368">
<name>go</name>
</scheme>
<scheme id="h323" type="scheme" rfc="3508">
<name>H.323</name>
</scheme>
<scheme id="ipp" type="scheme" rfc="3510">
<name>Internet Printing Protocol</name>
</scheme>
<scheme id="tftp" type="scheme" rfc="3617">
<name>Trivial File Transfer Protocol</name>
</scheme>
<scheme id="mupdate" type="scheme" rfc="3656">
<name>Mailbox Update (MUPDATE) Protocol</name>
</scheme>
<scheme id="pres" type="scheme" rfc="3859">
<name>Presence</name>
</scheme>
<scheme id="im" type="scheme" rfc="3860">
<name>Instant Messaging</name>
</scheme>
<scheme id="mtqp" type="scheme" rfc="3887">
<name>Message Tracking Query Protocol</name>
</scheme>
<scheme id="iris.beep" type="scheme" rfc="3983">
<name>iris.beep</name>
</scheme>
<scheme id="dict" type="scheme" rfc="2229">
<name>dictionary service protocol</name>
</scheme>
<scheme id="snmp" type="scheme" rfc="4088">
<name>Simple Network Management Protocol</name>
</scheme>
<scheme id="crid" type="scheme" rfc="4078">
<name>TV-Anytime Content Reference Identifier</name>
</scheme>
<scheme id="tag" type="scheme" rfc="4151">
<name>tag</name>
</scheme>
<scheme id="afs" type="scheme" href="http://www.iana.org/assignments/uri-schemes">
<name>Andrew File System global file names</name>
</scheme>
<scheme id="tn3270" type="scheme" href="http://www.iana.org/assignments/uri-schemes">
<name>Interactive 3270 emulation sessions</name>
</scheme>
<scheme id="mailserver" type="scheme" href="http://www.iana.org/assignments/uri-schemes">
<name>Access to data available from mail servers</name>
</scheme>
<scheme id="dns" type="scheme" href="http://www.iana.org/assignments/uri-schemes">
<name>Domain Name System</name>
</scheme>
<scheme id="info" type="scheme" href="http://www.iana.org/assignments/uri-schemes">
<name>Information Assets with Identifiers in Public Namespaces</name>
</scheme>
<scheme id="ldap" type="scheme" href="http://www.iana.org/assignments/uri-schemes">
<name>Lightweight Directory Access Protocol</name>
</scheme>
<violation>
<name>ILLEGAL_CHARACTER</name>
<description>
The character violates the grammar rules for URIs/IRIs.
</description>
<also ref="URI" fragment="page-49"/>
<also ref="IRI" section="2.2"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>ht$tp://example.org/foo</bad>
</violation>
<!--
<violation>
<name>RELATIVE_URI</name>
<description>
The IRI is relative not absolute.
</description>
<spec ref="RDF">
<text>representing an <em>absolute URI</em> with optional fragment identifier</text>
</spec>
<bad>foo/bar</bad>
<bad>#frag</bad>
<bad>//example.org/foo/bar#frag</bad>
</violation>
-->
<violation>
<name>PERCENT_ENCODING_SHOULD_BE_UPPERCASE</name>
<minting/>
<description>
Percent-escape sequences should use uppercase.
</description>
<spec ref="URI">
<text section="2.1">
URI producers and normalizers should use <em>uppercase</em>
hexadecimal digits for all percent-encodings.
</text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org/foo%c3%80</bad>
</violation>
<violation>
<name>SUPERFLUOUS_NON_ASCII_PERCENT_ENCODING</name>
<unimplemented/>
<minting/>
<description>
Percent-escape sequences should not be used unnecessarily.
</description>
<spec ref="IRI">
<text section="3.2">
URI-to-IRI conversion removes percent-encodings
</text>
</spec>
<comment>The IRI specification only weakly suggests that
Unicode characters should be used in preference
to percent encodings.</comment>
<bad>http://example.org/foo%C3%A9r</bad>
</violation>
<violation>
<name>SUPERFLUOUS_ASCII_PERCENT_ENCODING</name>
<unimplemented/>
<minting/>
<description>
Percent-escape sequences should not be used unnecessarily.
</description>
<spec ref="URI">
<text section="2.3">
For consistency, percent-encoded octets in the
ranges of ALPHA
(%41-%5A and %61-%7A), DIGIT (%30-%39), hyphen
(%2D), period (%2E), underscore (%5F), or tilde
(%7E) should not be created by URI producers
</text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org/foo%5Fb%61r</bad>
</violation>
<violation>
<name>UNWISE_CHARACTER</name>
<minting/>
<description>
The character matches no grammar rules of URIs/IRIs.
These characters are permitted in RDF URI References,
XML system identifiers, and XML Schema anyURIs.
</description>
<comment>Whitespace is dealt with separately.</comment>
<see>IRIFactory#allowUnwiseCharacters</see>
<see>#WHITESPACE</see>
<see>#DOUBLE_WHITESPACE</see>
<spec ref="IRI">
<text fragment="page-13">
Systems accepting IRIs MAY also deal with the printable characters in US-ASCII
that are not allowed in URIs, namely "<", "&gt;", '"', space, "{", "}", "|", "\",
"^", and "`", in step 2 above. If these characters are found but are not converted,
then the conversion SHOULD fail.
</text>
</spec>
<also ref="URI" fragment="page-49"/>
<bad>http://example.org/fo|o</bad>
<bad>http://example.org/fo<o</bad>
<bad>http://example.org/fo&gt;o</bad>
<bad>http://example.org/fo"o</bad>
<bad>http://example.org/fo`o</bad>
</violation>
<violation>
<name>CONTROL_CHARACTER</name>
<description>
Control characters are not allowed in URIs or RDF URI References.
</description>
<spec ref="RDF">
<text>
A URI reference within an RDF graph (an RDF URI reference) is a Unicode string [UNICODE] that:
<ul>
<li>
does not contain any control characters ( #x00 - #x1F, #x7F-#x9F)
</li>
</ul>
</text>
</spec>
<spec ref="IRI">
<text>
<pre>
ucschar = %xA0-D7FF / %xF900-FDCF / %xFDF0-FFEF
/ %x10000-1FFFD / %x20000-2FFFD / %x30000-3FFFD
/ %x40000-4FFFD / %x50000-5FFFD / %x60000-6FFFD
/ %x70000-7FFFD / %x80000-8FFFD / %x90000-9FFFD
/ %xA0000-AFFFD / %xB0000-BFFFD / %xC0000-CFFFD
/ %xD0000-DFFFD / %xE1000-EFFFD
</pre>
</text>
</spec>
<also ref="URI"/>
<bad>http://example.org/fo<unicode>007F</unicode>o</bad>
<bad>http://example.org/fo<unicode>0085</unicode>o</bad>
<bad>http://example.org/fo<unicode>0009</unicode>o</bad>
<bad>http://example.org/fo<unicode>0001</unicode>o</bad>
</violation>
<violation>
<name>NON_XML_CHARACTER</name>
<description>
The character is not legal in XML.
</description>
<spec ref="XML">
<text fragment="NT-Char">
Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
</text>
</spec>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org/foo<unicode>0001</unicode></bad>
</violation>
<violation>
<name>DISCOURAGED_XML_CHARACTER</name>
<minting/>
<description>
The character is discouraged in XML documents.
</description>
<spec ref="XML">
<text fragment="char32">
Document authors are encouraged to avoid "compatibility characters", as defined in
section 6.8 of [Unicode] (see also D21 in section 3.6 of [Unicode3]). The characters
defined in the following ranges are also discouraged. They are either control
characters or permanently undefined Unicode characters: [#x7F-#x84], [#x86-#x9F],
[#xFDD0-#xFDDF],
</text>
</spec>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org/foo<unicode>0080</unicode></bad>
</violation>
<violation>
<name>NON_INITIAL_DOT_SEGMENT</name>
<minting/>
<security/>
<description>
The path contains a segment /../ not at the beginning
of a relative reference, or it contains a /./
These should be removed.
</description>
<spec ref="URI">
<text section="6.2.2.3">
The complete path segments "." and ".." are intended <em>only</em> for use within relative references
</text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org/../foo</bad>
<bad>http://example.org/foo/../foo</bad>
<bad>http://example.org/foo/..</bad>
<bad>http://example.org/foo/./foo</bad>
<bad>http://example.org/./foo</bad>
<bad>http://example.org/foo/.</bad>
</violation>
<violation>
<name>EMPTY_SCHEME</name>
<description>
The scheme component is empty.
</description>
<spec ref="URI">
<text section="3.1"> Scheme names consist of a sequence of characters <em>beginning
with a letter</em> and followed by any combination of letters,
digits, plus ("+"), period ("."), or hyphen ("-"). </text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>://example.org/foo</bad>
</violation>
<violation>
<name>SCHEME_MUST_START_WITH_LETTER</name>
<description>
The scheme component must start with a letter.
</description>
<spec ref="URI">
<text section="3.1"> Scheme names consist of a sequence of characters <em>beginning
with a letter</em> and followed by any combination of letters,
digits, plus ("+"), period ("."), or hyphen ("-"). </text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>007://example.org/foo</bad>
</violation>
<violation>
<name>LOWERCASE_PREFERRED</name>
<minting/>
<description>lowercase is preferred in this component</description>
<spec ref="URI">
<text section="3.1" component="SCHEME">An implementation should accept uppercase letters as equivalent to lowercase in scheme names (e.g., allow "HTTP" as well as "http") for the sake of robustness but should only produce lowercase scheme names for consistency. </text>
<text section="3.2.2" component="HOST">
Although host is case-insensitive, producers and normalizers should use <em>lowercase for registered names</em> and hexadecimal addresses for the sake of uniformity, while only using uppercase letters for percent-encodings.
</text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>HTTP://example.org/foo</bad>
<bad>http://eXamPle.org/foo</bad>
</violation>
<violation>
<name>PORT_SHOULD_NOT_BE_EMPTY</name>
<minting/>
<description>The colon introducing an empty port component should be omitted entirely,
or a port number should be specified.</description>
<spec ref="URI">
<text section="3.2.2">
URI producers and normalizers should omit the port component <em>and its ":" delimiter</em> if port is empty
</text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org:/foo</bad>
</violation>
<violation>
<name>DEFAULT_PORT_SHOULD_BE_OMITTED</name>
<minting/>
<description>If the port is the default one for the scheme it should be omitted.
</description>
<spec ref="URI">
<text section="3.2.2">
URI producers and normalizers should omit the port component and its ":" delimiter if port is empty or if its value would be the <em>same as that of the scheme's default.</em>
</text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org:80/foo</bad>
</violation>
<violation>
<name>PORT_SHOULD_NOT_BE_WELL_KNOWN</name>
<security/>
<description>
Ports under 1024 should be accessed
using the appropriate scheme name.
</description>
<spec ref="URI">
<text section="7.2">
Applications should prevent dereference of a URI that specifies a TCP port number within the "well-known port" range <em>(0 - 1023)</em> unless the protocol being used to dereference that URI is compatible with the protocol expected on that well-known port.
</text>
</spec>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org:180/foo</bad>
</violation>
<violation>
<name>PORT_SHOULD_NOT_START_IN_ZERO</name>
<minting/>
<description>Leading zeros in the port number should be omitted.
This is an added feature of this implementation,
not mandated by any standard.
</description>
<also ref="URI"/>
<also ref="IRI"/>
<also ref="RDF"/>
<also ref="XML"/>
<also ref="XLink"/>
<also ref="Schema"/>
<bad>http://example.org:08080/foo</bad>
</violation>
<!--
<violation><name>IRI_CHARACTER</name>
<description>
Non-ASCII characters are not permitted in URIs.
</description>
<spec ref="URI">
<text section="1.3">
This specification uses the Augmented Backus-Naur Form (ABNF) notation of [RFC2234], including the following core ABNF syntax rules defined by that specification: ALPHA (letters), CR (carriage return), DIGIT (decimal digits), DQUOTE (double quote), HEXDIG (hexadecimal digits), LF (line feed), and SP (space).
</text>
<text section="2">
The ABNF notation defines its terminal values to be non-negative integers (codepoints) based on the US-ASCII coded character set [ASCII].
</text>
</spec>
<bad>http://example.org/André</bad>
</violation>
-->
<violation>
<name>BIDI_FORMATTING_CHARACTER</name>
<unimplemented/>
<description>A prohibited bi-directional control character was found.</description>
<spec ref="IRI">
<text section="4.1">
IRIs MUST NOT contain bidirectional formatting characters (LRM, RLM, LRE, RLE, LRO, RLO, and PDF).
</text>
</spec>
<bad>http://example.org/Andr<unicode>202A</unicode>bar</bad>
<bad>http://example.org/Andr<unicode>202B</unicode>bar</bad>
<bad>http://example.org/Andr<unicode>202C</unicode>bar</bad>
<bad>http://example.org/Andr<unicode>202D</unicode>bar</bad>
<bad>http://example.org/Andr<unicode>202E</unicode>bar</bad>
<bad>http://example.org/Andr<unicode>200E</unicode>bar</bad>
<bad>http://example.org/Andr<unicode>200F</unicode>bar</bad>
</violation>
<violation>
<name>WHITESPACE</name>
<description>
A single whitespace character.
These match no grammar rules of URIs/IRIs.
These characters are permitted in RDF URI References,
XML system identifiers, and XML Schema anyURIs.
</description>
<see>IRIFactory#allowUnwiseCharacters</see>
<see>#NOT_XML_SCHEMA_WHITESPACE</see>
<see>#UNWISE_CHARACTER</see>
<see>#DOUBLE_WHITESPACE</see>
<also ref="URI"/>
<also ref="IRI"/>
<bad>http://example.org/ foo</bad>
<bad>file:///Program Files</bad>
</violation>
<violation>
<name>DOUBLE_WHITESPACE</name>
<description>
Either two or more consecutive whitespace characters, or leading or trailing whitespace.
These match no grammar rules of URIs/IRIs.
These characters are permitted in RDF URI References,
XML system identifiers, but not XML Schema anyURIs.
</description>
<see>IRIFactory#allowUnwiseCharacters</see>
<see>#NOT_XML_SCHEMA_WHITESPACE</see>
<see>#UNWISE_CHARACTER</see>
<see>#WHITESPACE</see>
<also ref="URI"/>
<also ref="IRI"/>
<also ref="Schema"/>
<bad>http://example.org/ foo</bad>
<bad>file:///Program Files</bad>
<bad>file:///TabBar </bad>
<bad> rel-with-initial-space</bad>
</violation>
<violation>
<name>NOT_XML_SCHEMA_WHITESPACE</name>
<description>
Whitespace characters
match no grammar rules of URIs/IRIs.
These characters are permitted in RDF URI References,
and XML system identifiers.
However, tab and new line characters, and consecutive space characters
cannot occur in XML Schema anyURIs.
</description>
<see>IRIFactory#allowUnwiseCharacters</see>
<see>#DOUBLE_WHITESPACE</see>
<see>#WHITESPACE</see>
<also ref="URI"/>
<also ref="IRI"/>
<spec ref="Schema">
<text fragment="schema">
<pre>
<xs:simpleType name="anyURI" id="anyURI"&gt;
[...]
<xs:restriction base="xs:anySimpleType"&gt;
<xs:whiteSpace fixed="true" value="collapse" id="anyURI.whiteSpace"/&gt;
</xs:restriction&gt;
</xs:simpleType&gt;
</pre>
</text>
</spec>
<bad>file:///Tab<unicode>0009</unicode>Bar</bad>
<bad>file:///Tab<unicode>000A</unicode>Bar</bad>
<bad>file:///Tab<unicode>000D</unicode>Bar</bad>
</violation>
<violation>
<name>DOUBLE_DASH_IN_REG_NAME</name>
<internal/>
<bad>http://foo--bar//</bad>
</violation>
<violation>
<name>SCHEME_INCLUDES_DASH</name>
<internal/>
<bad>ht-tp://foo.bar//</bad>
<bad>-http://foo.bar//</bad>
<bad>http-://foo.bar//</bad>
</violation>
<violation>
<name>NON_URI_CHARACTER</name>
<internal/>
<bad>http://foo-bar//̳a</bad>
<bad>http://foo-b̳ar//</bad>
</violation>
<violation>
<name>PERCENT_20</name>
<internal/>