You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are encoding issues with non-ascii characters when interacting with Blazegraph from Python agents via the RemoteStoreClient of the JPS_BASE_LIB. For example, when uploading unit symbols like £, °, °C, or µg the Blazegraph GUI will display odd characters. The same odd characters will be returned when querying for those symbols.
Likely this encoding issue happens somewhere at the Python - Java interface, as uploading the entire ontology of units of measure rdf file using the RemoteStoreClient natively in Java does not face any of these issues.
The current workaround consists of
uploading all units with special characters at the start of relevant agents (to minimise instantiation of non-ascii Literals, as the instantiation seems to be inconsistent and previously produced different odd character sets), e.g. here
There are encoding issues with non-ascii characters when interacting with Blazegraph from Python agents via the
RemoteStoreClient
of the JPS_BASE_LIB. For example, when uploading unit symbols like£
,°
,°C
, orµg
the Blazegraph GUI will display odd characters. The same odd characters will be returned when querying for those symbols.Likely this encoding issue happens somewhere at the Python - Java interface, as uploading the entire ontology of units of measure rdf file using the
RemoteStoreClient
natively in Java does not face any of these issues.The current workaround consists of
Fore the visualisation this has been addressed by PR #466 (Issue #513)
The text was updated successfully, but these errors were encountered: