Current version (1.5.0) only supports creating the subject id based on a template.
Because processors always perform percent-encoding when IRIs are generated from string templates, this becomes cumbersome in cases where the subject id already exists pre-fabricated in the source.
Note: R2RML always performs percent-encoding when IRIs are generated from string templates.
If IRIs need to be generated without percent-encoding, then rr:column should be used instead of rr:template,
with an [R2RML view](https://www.w3.org/TR/r2rml/#dfn-r2rml-view) that performs the string concatenation.
... the equivalent to R2RML views in RML are path-expressions (eg. XPath or JSONPath).
Current version (1.5.0) only supports creating the subject id based on a
template
.Because processors always perform percent-encoding when IRIs are generated from string templates, this becomes cumbersome in cases where the subject id already exists pre-fabricated in the source.
Quoting from the spec https://www.w3.org/TR/r2rml/#from-template :
... the equivalent to R2RML views in RML are path-expressions (eg. XPath or JSONPath).
Sample XML input:
Feature request: