RMLio / RMLio/MappingWeaver-java
Iterating over single value fails
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Related to the difference in iterating over arrays (cf. #6), I also noticed that MappingWeaver fails when using the index wildcard [*] in a reference to a JSON value that is not an array. Again, I don't know what the RML spec would prescribe in such cases, but RMLViewer/RMLMapper nevertheless return the single JSON value instead.
Minimal example:
:view a rml:LogicalView ;
rml:viewOn [
# JSONPath root iterator over { "key": "value" }
] ;
rml:field [ rml:fieldName "key" ; rml:reference "key[*]" ]
.
:mapping a rml:TriplesMap ;
rml:logicalSource :view ;
rml:subjectMap [ rml:termType rml:BlankNode ] ;
rml:predicateObjectMap [
rml:predicate <urn:example:hasValue> ;
rml:objectMap [ rml:reference "key" ]
] .
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing issue #9 with the minimal RML mapping and JSON value shown in the report, then trace how MappingWeaver handles the [*] reference when the referenced value is not an array. Done means the single JSON value is returned consistently with the behavior described for RMLViewer/RMLMapper, with coverage for this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100