How is the message being reported: Through a JavaScript alert dialog, or
the JS console, or where?
Usually such things can be debugged by putting breakpoints into the code
(e.g. using Chrome dev tools), thus my question above.
The class tree does not require labels AFAIK.
Holger
On 30/07/2018 15:42, Rob Atkinson wrote:
(unmodified) SWA editor throws a message "null" when opening Class
tree at a specific class
data has no instances (also throws if instances) - it imports an
ontology loaded via EDG (which a specialisation of PROV-O).
If you ignore this, the class tree works - and if you reopen that
class it does not throw the error again - only after reloading the
editor page, the first time.
So three questions:
1) what is causing this (if known or guessable)
2) is there any way to get more useful diagnostics - such as a stack
trace or something to show where it fails
3) is there a unknown contract - i.e. something the data _must_ do -
such as have labels (in this case all classes do) - or should it
really handle any OWL class model ?
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
