RMLio / RMLio/MappingWeaver-java

Templates not working for non-http IRIs

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Description

When using rml:template to construct an IRI, explicitly indicated with rml:termType, the triples in question are missing from the output, except when they result in a well-formed HTTP URI.

Minimal example:

:mapping a rml:TriplesMap ;
  rml:logicalSource [
    # JSONPath root iterator over { "key": "value" }
  ] ;
  rml:subjectMap [ rml:termType rml:BlankNode ] ;
  rml:predicateObjectMap [
    rml:predicate <urn:example:http> ;
    rml:objectMap [
      rml:termType rml:IRI ;
      rml:template "http://example.org/{key}"
    ]
  ], [
    rml:predicate <urn:example:file> ;
    rml:objectMap [
      rml:termType rml:IRI ;
      rml:template "file:///example/{key}"
    ]
  ], [
    rml:predicate <urn:example:urn> ;
    rml:objectMap [
      rml:termType rml:IRI ;
      rml:template "urn:example:{key}"
    ]
  ], [
    rml:predicate <urn:example:relative> ;
    rml:objectMap [
      rml:termType rml:IRI ;
      rml:template "./{key}"
    ]
  ] .

Output:

_:Blank1 <urn:example:http> <http://example.org/value> .

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the minimal mapping example and tracing how rml:termType rml:IRI with rml:template is handled. Compare the HTTP, file, URN, and relative templates to find why only the HTTP result is emitted. Done means all four expected triples appear in the output.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
data-engineering
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.