IRI invalid when filename has spaces

[lauramble]

When trying to retrieve a file on the EBRAINS KG with fairgraph, I noticed that the openminds File instance did not have an IRI property, even though the instance on the KG did. Upon further investigation, it turns out that the problem comes from the filename, which contains spaces, so the openMINDS Python module raises an Invalid IRI error.

I used the actual IRI of the file I was trying to access in a minimal example to demonstrate the issue:

from openminds import IRI
IRI(value="https://data-proxy.ebrains.eu/api/v1/buckets/p63ea6-hbp-d000017_PatchClamp-GranuleCells_pub/GrC_Subject28_240216/240216-B_0001 EPSP.abf")

Spaces should probably be avoided in IRIs, but if they are there, could they be converted into '%20' when validating the IRI? Would that work?

[apdavison]

This affects a lot of datasets. We probably need a KG cleanup and a change to the curation process to ensure only valid IRIs get into the KG, but those are out of scope for openMINDS_Python.

I can see two approaches that would make openminds and fairgraph more flexible:

1. add an optional argument "strict" to the IRI constructor in openminds/base.py and set the default value to False, which means that the constructor will convert spaces to '%20'.
2. don't check the IRI value in the constructor, instead move the check to the validator.

Option 2 seems like the most consistent with the existing behaviour of openminds.