Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RMLTC0009a-JSON and RMLTC0009b-JSON: missing null value in data #11

Open
ghsnd opened this issue Jan 13, 2025 · 3 comments
Open

RMLTC0009a-JSON and RMLTC0009b-JSON: missing null value in data #11

ghsnd opened this issue Jan 13, 2025 · 3 comments
Assignees

Comments

@ghsnd
Copy link

ghsnd commented Jan 13, 2025

These test cases assumes a null value for "Sport" in student.json in the second record. However, the Sport key is just omitted:

    { 
      "ID": 20,
      "Name": "Demi Moore"
    }

For Sport to be null, the record should look like:

    { 
      "ID": 20,
      "Sport": null
      "Name": "Demi Moore"
    }
@pmaria
Copy link
Collaborator

pmaria commented Jan 14, 2025

This depends on the reference formulation. For JSONPath for example, the question is: how do we handle JSONPaths Nothing type. This should be defined in the IO-registry. My initial feeling is that it can be handled as null for RML.

Any thoughts @ghsnd @DylanVanAssche ?

@DylanVanAssche
Copy link
Contributor

DylanVanAssche commented Jan 14, 2025

Agreed, Nothing == null for us and rml-io-registry material! Non-existing key is the same as NULL for Processors.

@dachafra
Copy link
Member

Shall we move this to rml-io-registry then?

@DylanVanAssche DylanVanAssche transferred this issue from kg-construct/rml-core Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants