|
||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface ViolationCodes
Detailed description of problems detected.
This interface lists the codes returned by
Violation.getViolationCode()
.
Note: not all are errors, some merely reflect internal workings.
The violations are evaluated against the following standards:
foo/bar
>#frag
>//example.org/foo/bar#frag
>Scheme specific checks are enabled. The syntax of the following schemes is fully supported:
http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
IRIFactory.dnsViolation(boolean, boolean)
.
The default port is 80.http://www.example.org/foo/bar
>http://www.example.org:80/foo/bar
>http:foo/bar
>http://user@www.example.org/foo/bar
>http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
IRIFactory.dnsViolation(boolean, boolean)
.
The default port is 443.https://www.example.org/foo/bar
>https://www.example.org:443/foo/bar
>https:foo/bar
>https://user@www.example.org/foo/bar
>ftpurl = "ftp://" login [ "/" fpath [ ";type=" ftptype ]] fpath = fsegment *[ "/" fsegment ] fsegment = *[ uchar | "?" | ":" | "@" | "&" | "=" ] ftptype = "A" | "I" | "D" | "a" | "i" | "d"
login = [ user [ ":" password ] "@" ] hostport
safe = "$" | "-" | "_" | "." | "+" extra = "!" | "*" | "'" | "(" | ")" | "," escape = "%" hex hex unreserved = alpha | digit | safe | extra uchar = unreserved | escape
IRIFactory.dnsViolation(boolean, boolean)
.
The default port is 21.ftp://user@example.org/foo/bar;type=d
>ftp:///foo/bar
>ftp://user@example.org/foo/bar;type=z
>ftp://user@example.org/foo/b;ar;type=d
>newsurl = "news:" grouppart grouppart = "*" | group | article group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ] article = 1*[ uchar | ";" | "/" | "?" | ":" | "&" | "=" ] "@" host
safe = "$" | "-" | "_" | "." | "+" extra = "!" | "*" | "'" | "(" | ")" | "," escape = "%" hex hex unreserved = alpha | digit | safe | extra uchar = unreserved | escape
news:*
>news:group.it
>news:arb?itrary@news.example.org
>news:arbitrary@news.example.org
>news:arbitrary@news.exampl?.org
>news:arbitr?ary@news.exampl?.org
>news:///foo/bar
>news://user@example.org/foo
>nntpurl = "nntp://" hostport "/" group [ "/" digits ]
group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
IRIFactory.dnsViolation(boolean, boolean)
.
The default port is 119.nntp://example.org/foo4
>nntp://example.org/foo/4
>nntp://user@example.org/foo
>nntp:/foo
>nntp:///foo
>nntp://example.org/foo/4/3
>nntp://example.org/
>nntp://example.org/foo/
>nntp://example.org/*
>fileurl = "file://" [ host | "localhost" ] "/" fpath
fpath = fsegment *[ "/" fsegment ] fsegment = *[ uchar | "?" | ":" | "@" | "&" | "=" ]
safe = "$" | "-" | "_" | "." | "+" extra = "!" | "*" | "'" | "(" | ")" | "," escape = "%" hex hex unreserved = alpha | digit | safe | extra uchar = unreserved | escape
IRIFactory.dnsViolation(boolean, boolean)
.
The USER component must be omitted.file:///foo/b
>file:///foo/b?ar/yuk
>file://user@example.org/foo/bar
>file://eg:4029/foo/bar
>file:/foo/bar
>file://example.org
>file://foo/bar;t
>file://foo/~jjc
>The syntax of the following schemes is partially supported:
<URN> ::= "urn:" <NID> ":" <NSS>
<NID> ::= <let-num> [ 1,31<let-num-hyp> ] <let-num-hyp> ::= <upper> | <lower> | <number> | "-" <let-num> ::= <upper> | <lower> | <number>
<NSS> ::= 1*<URN chars> <URN chars> ::= <trans> | "%" <hex> <hex> <trans> ::= <upper> | <lower> | <number> | <other> | <reserved> <other> ::= "(" | ")" | "+" | "," | "-" | "." | ":" | "=" | "@" | ";" | "$" | "_" | "!" | "*" | "'"
urn:x-hp:foo?
>urn:urn-1:foo
>urn:x-hp:foo/bar
>urn:urn:foo
>urn://foo
>urn:foo:bar?query
>urn:foo:ff~
>The names of the following registered schemes are known, but they are otherwise unsupported:
Other relevant standards include:
Nested Class Summary | |
---|---|
static class |
ViolationCodes.Initialize
This class is not part of the API. |
Field Summary | |
---|---|
static int |
ACE_PREFIX
Internal code. |
static int |
BAD_BIDI_SUBCOMPONENT
There are restrictions on bidi characters in subcomponents of IRIs |
static int |
BAD_DOT_IN_IDN
// TODO complete entry for BAD_DOT_IN_IDN |
static int |
BAD_IDN
The Internationalized Domain Name check failed. |
static int |
BAD_IDN_UNASSIGNED_CHARS
Characters used in the IRI were unassigned in the version of Unicode known by this system. |
static int |
BIDI_FORMATTING_CHARACTER
A prohibited bi-directional control character was found. |
static int |
COMPATIBILITY_CHARACTER
TODO |
static int |
CONTROL_CHARACTER
Control characters are not allowed in URIs or RDF URI References. |
static int |
DEFAULT_PORT_SHOULD_BE_OMITTED
If the port is the default one for the scheme it should be omitted. |
static int |
DEPRECATED_UNICODE_CHARACTER
TODO |
static int |
DISCOURAGED_IRI_CHARACTER
Certain characters are discouraged in IRIs. |
static int |
DISCOURAGED_XML_CHARACTER
The character is discouraged in XML documents. |
static int |
DNS_LABEL_DASH_START_OR_END
A DNS name had a - at the beginning or end. |
static int |
DNS_LABEL_LENGTH_LIMIT
// TODO complete entry for DNS_LABEL_LENGTH_LIMIT |
static int |
DNS_LENGTH_LIMIT
// TODO complete entry for DNS_LENGTH_LIMIT |
static int |
DOUBLE_DASH_IN_REG_NAME
Internal code. |
static int |
DOUBLE_WHITESPACE
Either two or more consecutive whitespace characters, or leading or trailing whitespace. |
static int |
EMPTY_SCHEME
The scheme component is empty. |
static int |
HAS_PASSWORD
Including passwords in URIs is deprecated. |
static int |
ILLEGAL_CHARACTER
The character violates the grammar rules for URIs/IRIs. |
static int |
ILLEGAL_PERCENT_ENCODING
The host component a percent occurred without two following hexadecimal digits. |
static int |
IP_V4_OCTET_RANGE
A host entry consists of four numbers, but they are not in the range 0-255, or have leading zeros. |
static int |
IP_V6_OR_FUTURE_ADDRESS_SYNTAX
A syntax violation was detected in an IP V6 (or future) address. |
static int |
IPv6ADDRESS_SHOULD_BE_LOWERCASE
IP version 6 addresses should use lowercase hexadecimal |
static int |
LONE_SURROGATE
A unicode surrogate character that is not of a surrogate pair. |
static int |
LOWERCASE_PREFERRED
lowercase is preferred in this component |
static int |
MAYBE_NOT_NFC
Internal code. |
static int |
MAYBE_NOT_NFKC
Internal code. |
static int |
NON_INITIAL_DOT_SEGMENT
The path contains a segment /../ not at the beginning of a relative reference, or it contains a /./ These should be removed. |
static int |
NON_URI_CHARACTER
Internal code. |
static int |
NON_XML_CHARACTER
The character is not legal in XML. |
static int |
NOT_DNS_NAME
The host component did not meet the restrictions on DNS names. |
static int |
NOT_NFC
The IRI is not in Unicode Normal Form C. |
static int |
NOT_NFKC
The IRI is not in Unicode Normal Form KC. |
static int |
NOT_UTF8_ESCAPE
// TODO complete entry for NOT_UTF8_ESCAPE |
static int |
NOT_UTF8_ESCAPE_IN_HOST
// TODO complete entry for NOT_UTF8_ESCAPE_IN_HOST |
static int |
NOT_XML_SCHEMA_WHITESPACE
Whitespace characters match no grammar rules of URIs/IRIs. |
static int |
PERCENT
Internal code. |
static int |
PERCENT_20
Internal code. |
static int |
PERCENT_ENCODING_SHOULD_BE_UPPERCASE
Percent-escape sequences should use uppercase. |
static int |
PORT_SHOULD_NOT_BE_EMPTY
The colon introducing an empty port component should be omitted entirely, or a port number should be specified. |
static int |
PORT_SHOULD_NOT_BE_WELL_KNOWN
Ports under 1024 should be accessed using the appropriate scheme name. |
static int |
PORT_SHOULD_NOT_START_IN_ZERO
Leading zeros in the port number should be omitted. |
static int |
PRIVATE_USE_CHARACTER
TODO |
static int |
PROHIBITED_COMPONENT_PRESENT
A component that is prohibited by the scheme is present. |
static int |
QUERY_IN_LEGACY_SCHEME
// TODO complete entry for QUERY_IN_LEGACY_SCHEME |
static int |
REQUIRED_COMPONENT_MISSING
A component that is required by the scheme is missing. |
static int |
SCHEME_INCLUDES_DASH
Internal code. |
static int |
SCHEME_MUST_START_WITH_LETTER
The scheme component must start with a letter. |
static int |
SCHEME_PATTERN_MATCH_FAILED
The scheme specific syntax rules are violared. |
static int |
SCHEME_PREFERS_LOWERCASE
Some part of the scheme specific syntax prefers lowercase. |
static int |
SCHEME_REQUIRES_LOWERCASE
Some part of the scheme specific syntax requires lowercase. |
static int |
SUPERFLUOUS_ASCII_PERCENT_ENCODING
Percent-escape sequences should not be used unnecessarily. |
static int |
SUPERFLUOUS_NON_ASCII_PERCENT_ENCODING
Percent-escape sequences should not be used unnecessarily. |
static int |
UNASSIGNED_UNICODE_CHARACTER
The character code is not assigned in the version of Unicode implemented here. |
static int |
UNDEFINED_UNICODE_CHARACTER
TODO |
static int |
UNICODE_CONTROL_CHARACTER
TODO |
static int |
UNICODE_WHITESPACE
TODO |
static int |
UNREGISTERED_IANA_SCHEME
The scheme name does not have a "-" in it, but is not in the IANA registry. |
static int |
UNREGISTERED_NONIETF_SCHEME_TREE
The scheme name has a "-" in it, but it does not start in "x-" and the prefix is not known as the prefix of an alternative tree for URI schemes. |
static int |
UNWISE_CHARACTER
The character matches no grammar rules of URIs/IRIs. |
static int |
USE_PUNYCODE_NOT_PERCENTS
The host component used percent encoding, where punycode is preferred. |
static int |
WHITESPACE
A single whitespace character. |
Field Detail |
---|
static final int ILLEGAL_CHARACTER
This violates the following specifications: [URI] (see here), [IRI] (see section 2.2), [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
ht$tp://example.org/foo
>
static final int PERCENT_ENCODING_SHOULD_BE_UPPERCASE
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/foo%c3%80
>
static final int SUPERFLUOUS_NON_ASCII_PERCENT_ENCODING
The IRI specification only weakly suggests that Unicode characters should be used in preference to percent encodings.
This is specified in [IRI].
This violates the [IRI] specification.
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/foo%C3%A9r
>Unimplemented.
static final int SUPERFLUOUS_ASCII_PERCENT_ENCODING
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/foo%5Fb%61r
>Unimplemented.
static final int UNWISE_CHARACTER
Whitespace is dealt with separately.
This is specified in [IRI].
This violates the following specifications: [IRI], [URI] (see here).
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/fo|o
>http://example.org/fo<o
>http://example.org/fo>o
>http://example.org/fo"o
>http://example.org/fo`o
>
IRIFactory.allowUnwiseCharacters()
,
WHITESPACE
,
DOUBLE_WHITESPACE
,
Constant Field Valuesstatic final int CONTROL_CHARACTER
This is specified in [RDF].
This is specified in [IRI].
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
This violates the following specifications: [RDF], [IRI], [URI].
This violation has MUST force.
The following are examples of IRIs that have this violation:
http://example.org/foo
>http://example.org/fo?o
>http://example.org/fo o
>http://example.org/foo
>
static final int NON_XML_CHARACTER
This is specified in [XML].
This violates the following specifications: [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
http://example.org/foo
>
static final int DISCOURAGED_XML_CHARACTER
This is specified in [XML].
This violates the following specifications: [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/foo?
>
static final int NON_INITIAL_DOT_SEGMENT
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
This violation may indicate security issues, and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.securityViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/../foo
>http://example.org/foo/../foo
>http://example.org/foo/..
>http://example.org/foo/./foo
>http://example.org/./foo
>http://example.org/foo/.
>
static final int EMPTY_SCHEME
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
://example.org/foo
>
static final int SCHEME_MUST_START_WITH_LETTER
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
007://example.org/foo
>
static final int LOWERCASE_PREFERRED
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
HTTP://example.org/foo
>http://eXamPle.org/foo
>
static final int PORT_SHOULD_NOT_BE_EMPTY
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org:/foo
>
static final int DEFAULT_PORT_SHOULD_BE_OMITTED
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org:80/foo
>
static final int PORT_SHOULD_NOT_BE_WELL_KNOWN
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation may indicate security issues, and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.securityViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org:180/foo
>
static final int PORT_SHOULD_NOT_START_IN_ZERO
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org:08080/foo
>
static final int BIDI_FORMATTING_CHARACTER
This is specified in [IRI].
This violates the [IRI] specification.
This violation has MUST force.
The following are examples of IRIs that have this violation:
http://example.org/Andr?bar
>http://example.org/Andr?bar
>http://example.org/Andr?bar
>http://example.org/Andr?bar
>http://example.org/Andr?bar
>http://example.org/Andr?bar
>http://example.org/Andr?bar
>Unimplemented.
static final int WHITESPACE
This violates the following specifications: [URI], [IRI].
This violation has MUST force.
The following are examples of IRIs that have this violation:
http://example.org/ foo
>file:///Program Files
>
IRIFactory.allowUnwiseCharacters()
,
NOT_XML_SCHEMA_WHITESPACE
,
UNWISE_CHARACTER
,
DOUBLE_WHITESPACE
,
Constant Field Valuesstatic final int DOUBLE_WHITESPACE
This violates the following specifications: [URI], [IRI], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
http://example.org/ foo
>file:///Program Files
>file:///TabBar
> rel-with-initial-space
>
IRIFactory.allowUnwiseCharacters()
,
NOT_XML_SCHEMA_WHITESPACE
,
UNWISE_CHARACTER
,
WHITESPACE
,
Constant Field Valuesstatic final int NOT_XML_SCHEMA_WHITESPACE
This is specified in [Schema].
<xs:simpleType name="anyURI" id="anyURI"> [...] <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="anyURI.whiteSpace"/> </xs:restriction> </xs:simpleType>
This violates the following specifications: [URI], [IRI], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
file:///Tab Bar
>file:///Tab
Bar
>file:///Tab
Bar
>
IRIFactory.allowUnwiseCharacters()
,
DOUBLE_WHITESPACE
,
WHITESPACE
,
Constant Field Valuesstatic final int DOUBLE_DASH_IN_REG_NAME
static final int SCHEME_INCLUDES_DASH
static final int NON_URI_CHARACTER
static final int PERCENT_20
static final int PERCENT
static final int IP_V6_OR_FUTURE_ADDRESS_SYNTAX
This is specified in [URI].
IP-literal = "[" ( IPv6address / IPvFuture ) "]" IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" ) IPv6address = 6( h16 ":" ) ls32 / "::" 5( h16 ":" ) ls32 / [ h16 ] "::" 4( h16 ":" ) ls32 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32 / [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32 / [ *4( h16 ":" ) h16 ] "::" ls32 / [ *5( h16 ":" ) h16 ] "::" h16 / [ *6( h16 ":" ) h16 ] "::" ls32 = ( h16 ":" h16 ) / IPv4address ; least-significant 32 bits of address h16 = 1*4HEXDIG ; 16 bits of address represented in hexadecimal
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
http://[/
>ldap://[20015:db8::7]/c=GB?objectClass?one
>ldap://[2001:db8:::7]/c=GB?objectClass?one
>
static final int IPv6ADDRESS_SHOULD_BE_LOWERCASE
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
ldap://[2001:Db8::7]/c=GB?objectClass?one
>ldap://[2001:dB8::7]/c=GB?objectClass?one
>
static final int IP_V4_OCTET_RANGE
This is specified in [URI].
dec-octet = DIGIT ; 0-9 / %x31-39 DIGIT ; 10-99 / "1" 2DIGIT ; 100-199 / "2" %x30-34 DIGIT ; 200-249 / "25" %x30-35 ; 250-255
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
ldap://155.00.55.102/c=GB?objectClass?one
>ldap://20.256.20.20/c=GB?objectClass?one
>ldap://20.1000.20.20/c=GB?objectClass?one
>ldap://20.010.20.20/c=GB?objectClass?one
>
static final int NOT_DNS_NAME
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation is relevant for IRIs using DNS as the registry of hostnames.
The behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.dnsViolation(boolean, boolean)
.
This violation has MUST force.
The following are examples of IRIs that have this violation:
ldap://foo$/c=GB?objectClass?one
>http://foo.example.$org/
>
static final int USE_PUNYCODE_NOT_PERCENTS
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
This violation is relevant for IRIs using DNS as the registry of hostnames.
The behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.dnsViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
ftp://andr%C3%A9.example.org/
>
static final int ILLEGAL_PERCENT_ENCODING
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
ftp://andr%%A9.example.org/
>ftp://andr%.example.org/
>ftp://andre.example.org/%
>ftp://andre.example.org/%A
>ftp://andre.example.org/%A?
>ftp://andre.example.org/%A#
>
static final int ACE_PREFIX
static final int LONE_SURROGATE
This does not violate any of the supported IRI, URI or scheme specifications.
This violation has MUST force.
The following are examples of IRIs that have this violation:
http:/foo/p?
>
static final int DNS_LABEL_DASH_START_OR_END
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation is relevant for IRIs using DNS as the registry of hostnames.
The behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.dnsViolation(boolean, boolean)
.
This violation has MUST force.
The following are examples of IRIs that have this violation:
ldap://-foo/c=GB?objectClass?one
>http://foo.example.org-/
>http://foo.example.org--/
>http://--foo.example.org/
>http://-fo-o.example.org/
>
static final int BAD_IDN_UNASSIGNED_CHARS
This is specified in [URI].
This is specified in [IRI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://foo.example?.org/
>
static final int BAD_IDN
This is specified in [URI].
This is specified in [IRI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
http://--foo.example.org/
>http://xn--andr--ep-.example.org/
>http://xn--andr--ep.example.org/
>http://xn--a-bpad.example.org/
>http://xn.example.????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????/
>
static final int HAS_PASSWORD
This is specified in [URI].
This violates the following specifications: [URI], [IRI], [RDF], [XML], [XLink], [Schema].
This violation has MUST force.
This violation may indicate security issues, and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.securityViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://user:pass@example.org/
>
static final int DISCOURAGED_IRI_CHARACTER
Implementation is very partial. The amount of guidance as to which characters to discourage is insufficient.
This is specified in [IRI].
This violates the [IRI] specification.
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/?en-quad
>http://example.org/?medium-mathematical-space
>http://example?.org/
>http://example?.org/
>Unimplemented.
static final int BAD_BIDI_SUBCOMPONENT
This is specified in [IRI].
This violates the [IRI] specification.
This violation has SHOULD force.
By default, this is treated as an error (for the relevant specs), but that behaviour can be modified by
IRIFactory.shouldViolation(boolean, boolean)
.
Unimplemented.
static final int DNS_LENGTH_LIMIT
static final int DNS_LABEL_LENGTH_LIMIT
static final int NOT_UTF8_ESCAPE
static final int NOT_UTF8_ESCAPE_IN_HOST
static final int BAD_DOT_IN_IDN
static final int UNREGISTERED_IANA_SCHEME
This is specified in [URL_Registratrion].
This is specified in [URI].
<prefix>'-'<tree-specific identifier>For instance, the "foo" tree would allow creation of scheme names of the form: "foo-blahblah:" and "foo-bar:", where the tree prescribes an arbitrary USASCII string following the tree's unique prefix.
This violates the following specifications: [URI], [IRI], [XLink], [XML], [RDF], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
foo://example.org/bar
>
static final int UNREGISTERED_NONIETF_SCHEME_TREE
There is no standard provision for "x-" as a prefix for private use schemes. This is a feature of this implementation. As far as I am aware, no alternative trees have been registered.
This is specified in [URL_Registratrion].
<prefix>'-'<tree-specific identifier>For instance, the "foo" tree would allow creation of scheme names of the form: "foo-blahblah:" and "foo-bar:", where the tree prescribes an arbitrary USASCII string following the tree's unique prefix.
This violates the following specifications: [URI], [IRI], [XLink], [XML], [RDF], [Schema].
This violation has MUST force.
The following are examples of IRIs that have this violation:
foo-bar://example.org/bar
>
static final int NOT_NFC
This is specified in [IRI].
This violates the [IRI] specification.
This violation has SHOULD force.
By default, this is treated as an error (for the relevant specs), but that behaviour can be modified by
IRIFactory.shouldViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/#Andre?
>Unimplemented.
static final int NOT_NFKC
This is specified in [IRI].
This violates the [IRI] specification.
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
The following are examples of IRIs that have this violation:
http://example.org/#Andre?
>Unimplemented.
static final int DEPRECATED_UNICODE_CHARACTER
This violates the following specifications: [Unicode], [IRI].
This violation has MUST force.
static final int UNDEFINED_UNICODE_CHARACTER
This violates the following specifications: [Unicode], [IRI].
This violation has MUST force.
static final int PRIVATE_USE_CHARACTER
This violates the following specifications: [Unicode], [IRI].
This violation has MUST force.
static final int UNICODE_CONTROL_CHARACTER
This violates the following specifications: [Unicode], [IRI].
This violation has MUST force.
static final int UNASSIGNED_UNICODE_CHARACTER
This violates the following specifications: [Unicode], [IRI].
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
static final int MAYBE_NOT_NFC
static final int MAYBE_NOT_NFKC
static final int UNICODE_WHITESPACE
This violates the following specifications: [Unicode], [IRI].
This violation has MUST force.
static final int COMPATIBILITY_CHARACTER
This violates the following specifications: [Unicode], [IRI].
This violation has MUST force.
static final int REQUIRED_COMPONENT_MISSING
This does not violate any of the supported IRI, URI or scheme specifications.
This violation has MUST force.
static final int PROHIBITED_COMPONENT_PRESENT
This does not violate any of the supported IRI, URI or scheme specifications.
This violation has MUST force.
static final int SCHEME_REQUIRES_LOWERCASE
This does not violate any of the supported IRI, URI or scheme specifications.
This violation has MUST force.
static final int SCHEME_PREFERS_LOWERCASE
This does not violate any of the supported IRI, URI or scheme specifications.
This violation relates to creating your own IRIs, rather than
accepting and processing other peoples', and the behaviour of a factory
implementing the relevant specs can be modified by
IRIFactory.mintingViolation(boolean, boolean)
.
static final int SCHEME_PATTERN_MATCH_FAILED
This does not violate any of the supported IRI, URI or scheme specifications.
This violation has MUST force.
static final int QUERY_IN_LEGACY_SCHEME
|
||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |