public class JenaParameters extends Object
These parameters should not be regarded as a stable part of the API. If we find them being used significantly that probably means they should be moved to being model-specific rather than global.
Modifier and Type | Field and Description |
---|---|
static boolean |
disableBNodeUIDGeneration
If this flag is true (default is false) then bNodes are assigned a
simple count local to this JVM.
|
static boolean |
enableEagerLiteralValidation
Set this flag to true to cause typed literals to be
validated as they are created.
|
static boolean |
enableFilteringOfHiddenInfNodes
Set this flag to true (default) to hide certain internal nodes from the output
of inference graphs.
|
static boolean |
enableOWLRuleOverOWLRuleWarnings
If this flag is true (default) then attmempts to build an OWL inference
graph over another OWL inference graph will log a warning message.
|
static boolean |
enablePlainLiteralSameAsString
Set this flag to true to allow language-free, plain literals and xsd:strings
containing the same character sequence to test as sameAs.
|
static boolean |
enableSilentAcceptanceOfUnknownDatatypes
Set this flag to true to allow unknown literal datatypes to be
accepted, if false then such literals will throw an exception when
first detected.
|
static boolean |
enableWhitespaceCheckingOfTypedLiterals
Set this flag to true to switch on checking of surrounding whitespace
in non-string XSD numeric types.
|
Constructor and Description |
---|
JenaParameters() |
public static boolean enableEagerLiteralValidation
Set this flag to true to cause typed literals to be validated as they are created.
RDF does not require ill-formed typed literals to be rejected from a graph but rather allows them to be included but marked as distinct from all legally formed typed literals. Jena2 reflects this by optionally delaying validation of literals against datatype type constraints until the first access.
public static boolean enablePlainLiteralSameAsString
RDF plain literals and typed literals of type xsd:string are distinct, not least because plain literals may have a language tag which typed literals may not. However, in the absence of a languge tag it can be convenient for applications if the java objects representing identical character strings in these two ways test as semantically "sameAs" each other. At the time of writing is unclear if such identification would be sanctioned by the RDF working group.
public static boolean enableSilentAcceptanceOfUnknownDatatypes
RDF allows any URI to be used to indicate a datatype. Jena2 allows user defined datatypes to be registered but it is sometimes convenient to be able to process models containing unknown datatypes (e.g. when the application does not need to touch the value form of the literal). However, this behaviour means that common errors, such as using the wrong URI for xsd datatypes, may go unnoticed and throw obscure errors late in processing. Hence, the default is the require unknown datatypes to be registered.
public static boolean enableWhitespaceCheckingOfTypedLiterals
public static boolean enableFilteringOfHiddenInfNodes
public static boolean enableOWLRuleOverOWLRuleWarnings
public static boolean disableBNodeUIDGeneration
Licenced under the Apache License, Version 2.0