org.apache.jena.iri.impl.viol2java.xsl Maven / Gradle / Ivy
Must not have both fragment and section specified
Multiple texts must either all have components or none
Multiple texts must refer to different components
/*
* 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.
*/
/*
AUTOGENERATED FILE: DO NOT EDIT
*/
package com.hp.hpl.jena.iri;
import com.hp.hpl.jena.iri.impl.ViolationCodeInfo;
import com.hp.hpl.jena.iri.impl.ViolationCodeInfo.InSpec;
import com.hp.hpl.jena.iri.impl.ViolationCodeInfo.FromSpec_iri;
import com.hp.hpl.jena.iri.impl.ViolationCodeInfo.FromSpec_other;
import com.hp.hpl.jena.iri.impl.ViolationCodeInfo.FromSpec_scheme;
import com.hp.hpl.jena.iri.impl.ViolationCodeInfo.FromAlso;
import com.hp.hpl.jena.iri.impl.Specification;
import com.hp.hpl.jena.iri.impl.SchemeSpecification;
import com.hp.hpl.jena.iri.impl.Force;
/**
* Detailed description of problems detected.
* This interface lists the codes returned by
* {@link Violation#getViolationCode()}.
* Note: not all are errors, some merely reflect internal workings.
<p>The violations are evaluated against the following standards:
</p>
<dl>
</dl>
<p>Scheme specific checks are enabled. The syntax of the following schemes is fully supported:
</p>
<dl>
</dl>
<p>The syntax of the following schemes is partially supported:
</p>
<dl>
</dl>
<p>The names of the following registered schemes are known, but they are otherwise unsupported:
</p>
<dl>
</dl>
<p>Other relevant standards include:
</p>
<dl>
</dl>
*/
public interface ViolationCodes {
/**
This class is not part of the API.
*/
class Initialize implements IRIComponents, Force {
static {
Specification spec;
}
}
}
/**
*/
int = ;
Internal code. This is not an error or warning condition,
but is used to trigger more expensive processing.
<p>This violates the <a href=
"#ref- ">[ ]</a>
specification.</p>
<p>This violates the following specifications:
.
</p>
<p>This does not violate any of the supported IRI, URI or scheme specifications.</p>
<p>This violation has <a href="http://www.apps.ietf.org/rfc/rfc2119.html#sec-1">MUST</a> force.</p>
<p>The following are examples of IRIs that have this violation:</p>
<ul>
</ul>
<p>The following are examples of IRIs that do not have this violation:</p>
<ul>
</ul>
<p>Unimplemented.</p>
// TODO complete entry for
<p>This is specified in <a href="#ref- ">
[ ]</a>.</p>
<dl>
</dl>
See <a href="#ref- ">
[ ]</a>, specifically,
See
<dt>
</dt>
<dd>
</dd>
<dt>
For the component:
see
</dt>
<dd>
</dd>
<p>
</p>
<;<:
<pre> </pre>
<ol> </ol>
<ul> </ul>
<li> </li>
<em> </em>
<p>This violation has <a href="http://www.apps.ietf.org/rfc/rfc2119.html#sec-1">MUST</a> force.</p>
<p>This violation has <a href="http://www.apps.ietf.org/rfc/rfc2119.html#sec-1">SHOULD</a> force.
By default, this is treated as an error (for the relevant specs), but that behaviour can be modified by
{@link IRIFactory#shouldViolation}.
</p>
<p>This violation may indicate security issues, and the behaviour of a factory
implementing the relevant specs can be modified by
{@link IRIFactory#securityViolation}.
</p>
<p>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
{@link IRIFactory#dnsViolation}.
</p>
<br/>
This scheme requires the use of hostnames conforming to DNS syntax.
The IDNA compatibile processing of IRIs for this scheme is enabled if this scheme is enabled.
To disable this behaviour, this scheme has to be disabled using // TODO how to disable scheme
and DNS compatibile rules have to be disabled using {@link IRIFactory#dnsViolation}.
<p>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
{@link IRIFactory#mintingViolation}.
</p>
<li><<code> </code>></li>
\u
@see
<dt><a name="ref- ">[ ]</a>
RFC
</dt>
<dd><a href=" ">
(section )
</a>
</dd>
<dd>
Pertinent text from the specification includes:
<br />
<dl>
</dl>
</dd>
<dd>
<br/>
The following are examples of well-formed IRIs using this scheme:
<ul>
</ul>
<br/>
The following are examples of ill-formed IRIs using this scheme:
<ul>
</ul>
</dd>
The default port is .<br />
The component must be omitted.<br />
The component is required.<br />
<br/>TODO:
The component:
<ul>
<li>
is required to match the regular expression:
</li>
<li>
may use as sub-delimiters, and care must
be taken when percent escaping or unescaping these delimiters to not disrupt
the scheme specific syntax.
</li>
</ul>
The component
may use as sub-delimiters, and care must
be taken when percent escaping or unescaping these delimiters to not disrupt
the scheme specific syntax. <br/>
The component
is required to match the regular expression:
<br/>
<a href="
">section
<a>
<a href="
">here<a>
#
#sec-
http://www.ietf.org/rfc/rfc
.txt
http://www.apps.ietf.org/rfc/rfc
.html
<a href="#ref-
">[
]</a> (see
)
,
<a href="#ref-
">[
]</a>
,
new ViolationCodeInfo(
,
" ",
" ",
" ",
0 ,
new InSpec[]{
},
new String[]{
},
new String[]{
},
true||
false
);
new ViolationCodeInfo(
,
" ",
" ",
" ",
0 ,
new InSpec[]{
},
new String[]{
},
new String[]{
},
true||
false
);
spec =
new SchemeSpecification(
" ",
" ",
" ",
"
",
" ",
new String[]{
},
new String[]{
}
);
spec =
new Specification(
" ",
" ",
" ",
" ",
"
",
"
",
new String[]{
},
new String[]{
}
);
spec
.addDefinition(
"
",
"
",
"
"
);
spec.setDNS(true);
spec.port( );
spec.setPattern( ,
"
" );
spec.setReserved( ," ");
spec. (
IRIComponents.
);
new ViolationCodeInfo(
,
" ",
new String[]{
},
new String[]{
},
true||
false
);
new FromSpec_ (
" ",
,
" "
),
new FromSpec_ (
" ",
,
" ",
" ",
" "
),
new FromSpec_ (
" ",
-1
,
" ",
" ",
" "
),
new FromAlso(
" ",
" "
),
|Force.
";\":
;\n"+
":\;\\:
";\":
;\n"+
":\;\\:<;<:
"+
"
(
)
*
*
" ",
\n
\r
\u
<p>
</p>
"+
"</p><
>
</
>"+
"<p>
"+
"</p><
>
</
>"+
"<p>
"+
" <
>
</
> "+
"
© 2015 - 2025 Weber Informatics LLC | Privacy Policy