Error messages in the log are the one place that Protege doesn't display one of the configured label annotations. To ameliorate this I propose that the OWLAPI add the ability to be configured, for the purposes of error reporting, in the same way as Protege is with a priority list of annotation properties. When configured this way, labels rather than an IRIs would sent to the error log. I'm submitting the issue here because I believe it to be the case that the error messages I see in the log come from the OWLAPI.
The only error type that I know to show up in the log are cases of violations of the global restrictions. There may be others, and there may be situations in the syntax error dialog where an IRI is shown, but I'm not sure. I don't interact with that much.
I would suggest consulting with @BrianHaugh, who has reported running into a number of situations where this happens, making debugging more difficult.
Error messages in the log are the one place that Protege doesn't display one of the configured label annotations. To ameliorate this I propose that the OWLAPI add the ability to be configured, for the purposes of error reporting, in the same way as Protege is with a priority list of annotation properties. When configured this way, labels rather than an IRIs would sent to the error log. I'm submitting the issue here because I believe it to be the case that the error messages I see in the log come from the OWLAPI.
The only error type that I know to show up in the log are cases of violations of the global restrictions. There may be others, and there may be situations in the syntax error dialog where an IRI is shown, but I'm not sure. I don't interact with that much.
I would suggest consulting with @BrianHaugh, who has reported running into a number of situations where this happens, making debugging more difficult.
See also: https://github.com/CommonCoreOntology/CommonCoreOntologies/issues/105 . The OBO Foundry already uses Opaque IRIs so this change would also benefit OBO ontology developers.