This section provides details for each class and property defined by RML Execution Report (RER) Vocabulary.
Classes
RML Execution Reportc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#RmlExecutionReport
-
Is defined by
-
https://w3id.org/dre/rer#
-
Example
-
[] a rer:RmlExecutionReport
rer:isSuccess false;
rer:isComplete false;
rer:processorName "BURP";
rer:processorVersion "0.1.2";
rer:generatedStatements 0;
rer:generatedStatementsPerTriplesMap [
rer:triplesMap <PersonTM>
rer:generatedStatements 0
];
rer:generatedStatementsPerTriplesMap [
rer:triplesMap <MovieTM>
rer:generatedStatements 0
];
rer:hasErrors [
rer:timestamp "2025-11-26+13:20:00"^xsd:dateTime
a rer:ReferenceFormulationExecutionError
rer:message "Execution Error in JSONPath `$.film.title.value`."
rer:reference "$.film.title.value"
rer:referenceFormulation rml:JSONPath
rer:iteration "{film:{title:'A film title'}}"
rer:stackTrace "A java stack trace"
rer:mappingStatement [
ptr:statement <<:a0 rml:template "$.film.title.value`.">>;
ptr:part ptr:object
];
].
-
is in domain of
-
generated statements dp, generated statements per Triples Map op, generated statements per target op, has error op, has log op, is complete dp, is success dp, number of triples map dp, processor name dp, processor version dp
IRI: https://w3id.org/dre/rer#Log
-
Is defined by
-
https://w3id.org/dre/rer#
-
has sub-classes
-
Error c, Information c, Warning c
-
is in domain of
-
Potential Cause ap, Potential Confusion ap, Potential Confusion Error ap, Potential Solution ap, Suggested Context ap, Timestamp of the log message. dp, iteration data dp, iteration index dp, mapping statement op, message dp, order dp, stack trace dp
-
is in range of
-
Potential Confusion Error ap, has log op
Unrecognized Termc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#UnrecognizedTerm
-
Potential Cause
-
This could be a typo in the mapping or a feature from a newer RML version this engine does not know.
-
Potential Solution
-
Check for typos in the term. If it is correct, this engine may be outdated.
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Warning c
Deprecated Featurec back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#DeprecatedFeature
-
Potential Cause
-
The mapping employs a term or construct that has been marked as deprecated in the RML specification or processor.
-
Potential Solution
-
Update the mapping to use the recommended alternative constructs as per the latest RML specification.
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Warning c
Configuration Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#ConfigurationError
-
Potential Cause
-
Required configuration options, environment variables, or parameters are missing, invalid, or inconsistent.
-
Potential Solution
-
Review engine configuration, command line parameters, and environment variables; fix invalid values and provide missing ones.
-
Potential Confusion
-
Do not confuse with Mapping Error (mapping definition is wrong) or Execution Error (data-related issues).
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Error c
-
has sub-classes
-
Cannot Read Mapping Document c, Missing Dependency c
Cannot Read Mapping Documentc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#CannotReadMappingDocument
-
Potential Cause
-
Wrong path or URI to the mapping file, missing file, or insufficient file system / network permissions.
-
Potential Solution
-
Verify that the mapping path/URI is correct, the resource exists and the process has sufficient permissions to read it.
-
Potential Confusion
-
Do not confuse with RDF Mapping Syntax Error; here the mapping cannot be read at all, not parsed.
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Configuration Error c
Function Execution Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#FunctionExecutionError
-
Potential Cause
-
The function implementation raised an exception or received invalid arguments during execution.
-
Potential Solution
-
Inspect the function definition, arguments and implementation; fix invalid inputs or implementation bugs.
-
Potential Confusion
-
Type Conversion Error could be an alternative when we precisely know that's the issue.
-
Potential Confusion Error
-
Type Conversion Error c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Execution Error c
Ill-typed Literal Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#IllTypedLiteralError
-
Potential Solution
-
Fix the value of the typed literal to be valid according to the datatype or update the datatype to match the actual value, you may also leave the datatype empty to let the engine infer it.
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Data Error c, Datatype Expectation Error c
Incorrect Term Typec back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#IncorrectTermType
-
Potential Cause
-
The mapping specifies a term type (IRI, blank node, literal) inconsistent with the position or constraints in the target RDF model.
-
Potential Solution
-
Adjust the mapping term type or target constraints so that subject, predicate and object positions use valid term types.
-
Potential Confusion
-
May be confused with Type Conversion Error; here term type is wrong, not the lexical value datatype.
-
Potential Confusion Error
-
Type Conversion Error c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Out Of Spec c
-
is in domain of
-
allowed term types op
Invalid IRIc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#InvalidIRI
-
Potential Cause
-
The mapping constructs IRIs by concatenation or templating that yields illegal characters or structure.
-
Potential Solution
-
Validate IRI templates and input values; encode or sanitize components before building IRIs.
-
Potential Confusion
-
May be confused with Predicate Not Reifiable; here the issue is invalid syntax of the IRI itself.
-
Potential Confusion Error
-
Invalid URI c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Invalid Output RDF c
Invalid URIc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#InvalidURI
-
Potential Cause
-
The mapping constructs URIs by concatenation or templating that yields illegal characters or structure.
-
Potential Solution
-
Validate URI templates and input values; encode or sanitize components before building URIs.
-
Potential Confusion
-
May be confused with Predicate Not Reifiable; here the issue is invalid syntax of the URI itself.
-
Potential Confusion Error
-
Invalid IRI c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Invalid Output RDF c
Logical Source Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#LogicalSourceError
-
Potential Cause
-
The reference formulation, iterator, is incompatible
-
Potential Solution
-
Review the logical source, reference formulation and iterator expression to ensure they are compatible with the actual source structure.
-
Potential Confusion
-
May be confused with Reference Formulation Execution Error, which relates to value extraction rather than iteration.
-
Potential Confusion Error
-
Reference Formulation Execution Error c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Execution Error c
Logical Targetc back to ToC or Class ToC
IRI: http://w3id.org/rml#LogicalTarget
-
is in range of
-
target op
Missing Dependencyc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#MissingDependency
-
Potential Cause
-
The engine was started without installing or enabling a required dependency.
-
Potential Solution
-
Install and enable the missing dependency, update the classpath/module-path, or configure the engine to use an available alternative.
-
Potential Confusion
-
May be confused with Unsupported Function, which refers to a function not implemented even when dependencies are present.
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Configuration Error c
No Triples Mapc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#NoTriplesMap
-
Potential Cause
-
The mapping file is empty or contains no resources recognized as TriplesMap
-
Potential Solution
-
Ensure that the mapping defines at least one Triples Map with the correct IRIs and prefixes.
-
Potential Confusion
-
May be confused with Source Access Error; here the source may be fine but no mapping is defined to use it.
-
Potential Confusion Error
-
Source Access Error c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Mapping Error c
Out Of Memoryc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#OutOfMemory
-
Potential Cause
-
Input data is too large, processing is not streamed, or memory limits for the process/VM are too low.
-
Potential Solution
-
Increase memory limits, enable streaming or chunked processing, or split the job into smaller executions.
-
Potential Confusion
-
Do not confuse with Source Access Error; here the problem is resource exhaustion, not reaching the source.
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Execution Error c
Out Of Specc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#OutOfSpec
-
Potential Cause
-
A cardinality violation, usage of a property on the wrong class, or an invalid literal value for a configuration property. Likely to be caught by the shapes.
-
Potential Solution
-
Refactor the mapping to adhere to the RML specification constraints. Validating the mapping against SHACL shapes usually reveals the fix.
-
Potential Confusion
-
May be confused with Unsupported Mapping: An Out Of Spec error indicates the mapping is objectively invalid and should not work on any compliant processor.
-
Potential Confusion Error
-
Unsupported Mapping c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Mapping Error c
-
has sub-classes
-
Incorrect Term Type c
Predicate Not Reifiablec back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#PredicateNotReifiable
-
Potential Cause
-
The mapping attempts to reify a predicate that is reserved, unsupported or structurally incompatible with reification.
-
Potential Solution
-
Adapt the mapping to use a different predicate or another representation that does not require reification.
-
Potential Confusion
-
Do not confuse with Invalid IRI, which is about syntactic invalidity of the IRI, not reifiability.
-
Potential Confusion Error
-
Invalid IRI c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Invalid Output RDF c
RDF Mapping Syntax Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#RDFMappingSyntaxError
-
Potential Cause
-
The mapping file contains invalid RDF syntax or serialization errors.
-
Potential Solution
-
Validate and fix the RDF syntax using an RDF parser or validator before running the engine.
-
Potential Confusion
-
Do not confuse with Invalid Output RDF, which refers to invalid generated RDF data rather than mapping syntax.
-
Potential Confusion Error
-
Invalid Output RDF c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Mapping Error c, Parsing Error c
Source Access Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#SourceAccessError
-
Potential Cause
-
Error in the access path or credentials
-
Potential Solution
-
Verify the source URI, network connectivity, and authentication credentials; update the mapping or environment configuration accordingly.
-
Potential Confusion
-
Do not confuse with Logical Source Error, which concerns iterating over the source rather than reaching it.
-
Potential Confusion Error
-
Logical Source Error c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Execution Error c
Type Conversion Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#TypeConversionError
-
Potential Cause
-
An ExpressionMap generates a value of a type that is not convertible to the expected/specified type.
-
Potential Solution
-
Adjust the mapping to generate values in the expected datatype or update the target type to match the actual data.
-
Potential Confusion
-
Do not confuse with Function Execution Error, where the function fails even if the types are correct.
-
Potential Confusion Error
-
Function Execution Error c
-
Suggested Context
-
Data dp
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Data Error c, Datatype Expectation Error c
Unexpected Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#UnexpectedError
-
Potential Cause
-
Unhandled exception, logic bug, or inconsistent internal state within the RML processor.
-
Potential Solution
-
Collect logs and stack traces, report the issue to the engine maintainers, and update to a fixed version when available.
-
Potential Confusion
-
Do not confuse with Configuration Error or Mapping Error, which are caused by user-provided configuration or mapping definitions.
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Error c
Unparseable Data Errorc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#UnparseableDataError
-
Potential Cause
-
The source value uses an unexpected syntax or format that cannot be parsed.
-
Potential Solution
-
Normalize the input format or adjust the reference formulation and parsing rules to accept the observed format.
-
Potential Confusion
-
May be confused with Type Conversion Error; here the problem is parsing, not converting a parsed value.
-
Potential Confusion Error
-
Type Conversion Error c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Data Error c, Parsing Error c
Unsupported Functionc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#UnsupportedFunction
-
Potential Cause
-
The function IRI exists in the mapping, but the engine has no registered code associated with that IRI.
-
Potential Solution
-
Register the custom function implementation with the engine or ensure the necessary function libraries are loaded.
-
Potential Confusion
-
Distinguished from Function Execution Error: Here the function code is never called because it wasn't found. In execution errors, the code runs but fails.
-
Potential Confusion Error
-
Function Execution Error c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Unsupported Mapping c
Unsupported Mappingc back to ToC or Class ToC
IRI: https://w3id.org/dre/rer#UnsupportedMapping
-
Potential Cause
-
The mapping uses a feature that is not implemented in this specific engine.
-
Potential Solution
-
Check the engine documentation for supported features. You may need to simplify the mapping, switch to a compatible engine, or implement the missing feature plugin.
-
Potential Confusion
-
The difference with Out Of Spec is that the engine don't know if this is spec compliant or not, whereas an Out Of Spec mapping is invalid everywhere.
-
Potential Confusion Error
-
Out Of Spec c
-
Is defined by
-
https://w3id.org/dre/rer#
-
has super-classes
-
Mapping Error c
-
has sub-classes
-
Unsupported Function c
Object Properties
IRI: https://w3id.org/dre/rer#allowedTermTypes
IRI: https://w3id.org/dre/rer#dataType
IRI: https://w3id.org/dre/rer#expectedDataType
IRI: https://w3id.org/dre/rer#hasSourceData
Data Properties
IRI: https://w3id.org/dre/rer#hasSourceData