review the code

[saidfathalla]

Hi Mustafa, could you please take a look and test and tell me if you see any improvements?

[mustafasoylu]

1. using if __name__ == '__main__ is not best practice, you already set the package in pyproject.toml so i think you can delete that in here
2. scripts/validate_sssom.py file seems redundant
3. since this is a CLI tool, it might be good to have a dynamic --version option. You can take it from pyproject.toml using a library. You can check how we do that in somesy
4. I suggest to add --debug option to log more information, especially where do you think there might be problems, great option to have when users report bugs
5. it might be good to use logging library for better formatting and it would be easier to do (4). In addition, I suggest adding more logs and separating the logs to info, debug, warning and error levels (logging lib enables this). if the program works without problem, there is no need to show all the logs to the user (not more than necessary)
6. using a general exception is not recommended line
7. folder (and files) in src/fdo2rdf/samples, src/fdo2rdf/mappings, and src/fdo2rdf/outputs seems to not related to the code. It would be better to move these folder out of src folder and add to a folder in root maybe called docs or another name. src folder should only have the files that are code or used in code
8. this is just a suggestion but, i suggest using ruff instead of black in pre-commit hooks. again, you can check somesy [pre-commit file]{https://github.com/Materials-Data-Science-and-Informatics/somesy/blob/3b14642f0dfb2bd9d0a587f58fa720c30f2a5b10/.pre-commit-config.yaml#L24) and pyproject.toml for its settings

[mustafasoylu]

• If you are planning to publish this to pypi, you can set GitHub CI pipeline to have a release for both GitHub and pypi. for reference: somesy ci files
• it would be great if you can add some tests to test basic functionality. you can use those tests before publishing the package