pyLODE
pyLODE copied to clipboard
RDFLib
Cater for annotation in multiple languages
We ran into an issue related to this, where ontologies that have labels in multiple languages result in mixed-language documents.
It seems relatively easy to fix though; BaseProfile already has a default_languageproperty, and filtering out all triples with a literal in a different language before assigning it to self.G seems to do the trick. It just needs some way to choose the language as it's currently still hardcoded to english. I'd be happy to help out with this one if you're open to pull requests.
I'd be happy to help out with this one if you're open to pull requests.
I love PRs! I'm going to tackle PR #114 on Monday and PR #89's very old and needs feedback from the submitter, so I may close it. Then there will be no active PRs, so a clean field for you to submit one.
I'll be doing a lot of work on pyLODE in the next couple of weeks as we're using it in projects, so this is paid work, not voluntary stuff. This means I'll have scope to help you with a PR or to address issues you raise.
(I've been meaning to get around to proper multi-lingual support for ages but have no driving resources right now, so I'm thrilled to see someone want to tackle this!)
Created a PR with a simple solution that seems to be enough for my own needs, but I'll leave it up the experts to decide if this approach is the right way to go. If not, feel free to point me in the right direction and I'll change what's needed, eventually.
The functionality from #118 was removed from cli.py with the jump to the v3 series: https://github.com/RDFLib/pyLODE/commit/7359cb69b39f41924f997b22429f7b1527a45fb1#diff-9441a88d9bc92d76088030c5d4f9468dcb3c24574ad1bcc6d76753cd4b6b3ae5
Are there any current plans or ideas to reimplement internationalisation (i18n) after the switch?
This has come up during https://lab.allmende.io/valueflows/valueflows/-/merge_requests/695#note_39778
