What steps will reproduce the problem?
If an entity ID has underscore(s) in it, it will not work in owlsim because it
treats it like a delimiter between a name and idspace. Currently, IDs need to
be pre-processed to change the underscores to something else (for example,
dashes). This is really awkward.
Should underscores be permitted? I feel like they should be.
Perhaps ids can be loaded, and temporarily mapped to an identifier that is
suitable for use in owlsim, but then the output can be generated using the
original identifiers.
Original issue reported on code.google.com by nicole.l...@gmail.com on 6 Nov 2013 at 9:27
Original issue reported on code.google.com by
nicole.l...@gmail.comon 6 Nov 2013 at 9:27