Description
While developing new vocabulary or changing vocabulary I often encounter errors such as this from oml2owl"
The feature 'specializedTerm' of 'SpecializationAxiom null' contains an unresolved proxy 'Aspect null'
The feature 'specializedTerm' of 'SpecializationAxiom null' contains an unresolved proxy 'Aspect null'
The errors suggest that there is a parsing error but they are completely unhelpful to the developer as they provide no information that would help identify the missing dependency. Presumably, the elements being expressed here as "null" are references that are failing because the referenced vocabulary is probably missing. If the error message presented the symbols that failed to resolve it would at least give the developer a clue where the error might lie. As it is, this message is completely useless as it conveys no hint about where the problem might exist in a large vocabulary.
Steps to Reproduce
This can often be invoked by simply removing an import or changing a symbol name of a symbol from an imported vocabulary.
Expected Behavior
The error message would be much more helpful if it gave the actual symbol strings that it failed to dereference instead of null and/or a link number or some other coordinate to help identify the offending expression.
Additional Context
This is not urgent since it is usually not hard to find the offending line using luxor or rosetta editor.
But it is annoying and ought to be easy to fix.
Relevant screenshots
If applicable, add screenshots to help illustrate the issue.
Description
While developing new vocabulary or changing vocabulary I often encounter errors such as this from oml2owl"
The feature 'specializedTerm' of 'SpecializationAxiom null' contains an unresolved proxy 'Aspect null'
The feature 'specializedTerm' of 'SpecializationAxiom null' contains an unresolved proxy 'Aspect null'
The errors suggest that there is a parsing error but they are completely unhelpful to the developer as they provide no information that would help identify the missing dependency. Presumably, the elements being expressed here as "null" are references that are failing because the referenced vocabulary is probably missing. If the error message presented the symbols that failed to resolve it would at least give the developer a clue where the error might lie. As it is, this message is completely useless as it conveys no hint about where the problem might exist in a large vocabulary.
Steps to Reproduce
This can often be invoked by simply removing an import or changing a symbol name of a symbol from an imported vocabulary.
Expected Behavior
The error message would be much more helpful if it gave the actual symbol strings that it failed to dereference instead of null and/or a link number or some other coordinate to help identify the offending expression.
Additional Context
This is not urgent since it is usually not hard to find the offending line using luxor or rosetta editor.
But it is annoying and ought to be easy to fix.
Relevant screenshots
If applicable, add screenshots to help illustrate the issue.