Thank you. I've encoded the strings to NFC (both the file name and the jsonld data) and all the errors and warnings went away. As far as I understand they are just two ways to represent the same symbol, using either a single codepoint or two. Other than that, the two strings should be equivalent (they look the same) and not "incorrect".
- Code: 46/NOT_NFC in PATH: The IRI is not in Unicode Normal F... zPlus
- Re: Code: 46/NOT_NFC in PATH: The IRI is not in Unicode... Simon Bin
- Re: Code: 46/NOT_NFC in PATH: The IRI is not in Uni... zPlus
- Re: Code: 46/NOT_NFC in PATH: The IRI is not in... Andy Seaborne
- Re: Code: 46/NOT_NFC in PATH: The IRI is no... zPlus
- Re: Code: 46/NOT_NFC in PATH: The IRI is no... Shaw, Ryan
- Re: Code: 46/NOT_NFC in PATH: The IRI is no... Andy Seaborne
