YARRRML-parser could use JSON Path Plus for the parsing and use of JSON Path directives in iterators.
Why it is useful
This would allow for a broader range of patterns available to end users. It would for instance simplify nested RDF generation by doing multiple JSONPath traversals to unfold the nesting, by allowing the '^' parent lookup in order to create IDs. See #67 for a previous discussion.
Existing features it breaks
It is difficult to square strict conformance with the spec, ease of use and appropriate default behavior. For instance in doing this change RocketRML parses the path strings with JSON Path Plus even if user asserts merely that the path string provided is a JSON Path string (but that assertion might strictly sensu be wrong, just as in one RocketRML example!)
Issue type: :unicorn: Feature
Description
YARRRML-parser could use JSON Path Plus for the parsing and use of JSON Path directives in iterators.
Why it is useful
This would allow for a broader range of patterns available to end users. It would for instance simplify nested RDF generation by doing multiple JSONPath traversals to unfold the nesting, by allowing the '^' parent lookup in order to create IDs. See #67 for a previous discussion.
Existing features it breaks
It is difficult to square strict conformance with the spec, ease of use and appropriate default behavior. For instance in doing this change RocketRML parses the path strings with JSON Path Plus even if user asserts merely that the path string provided is a JSON Path string (but that assertion might strictly sensu be wrong, just as in one RocketRML example!)