search

protegeproject / webprotege

The webprotege code base
Other
627 stars 253 forks source link

Inaccurate error message when imports fail #735

Open bdonohue29 opened 3 years ago

bdonohue29 commented 3 years ago

I recently tried to upload a DCAT ttl file onto our WebProtege server. I got the following error:

image

But as it turned out, the error was due to failure to resolve the DCAT file's owl:imports statement for Dublin Core Terms. The Dublin Core group had updated its URL where the DC Terms file could be found, so the import failed. When I updated the owl:imports statement to the new URL, it worked fine. Happy ending.

However, the error message WebProtege provided didn't indicate that the import failed. Rather, it sent me down a rabbit hole of trying to clear my cache and refresh my browser. So it'd be great if WebProtege's error handling were more accurate for import errors, which happen all the time.

Here's a sample of the Java error log for reference:

image

ldibanyez commented 1 year ago

Bumping. I've just hit this when trying to import (coincidentally the same DCAT ttl), from a cloud-based folder (OneDrive) in the public instance. As I had similar issues with other tools in the past I knew what could be going on.

However, when importing from the file in HDD, the error is unparsable ontology.... I'll check the owl:imports as OP to see if I'm lucky. Otherwise, I'll open a separate issue.

Edit: The unparsable ontology bit was my fault (got the html instead of the ttl). However, still getting the "Refresh Browser" message on the ttl. It has the following imports:

image

I replaced dct with the URI: http://purl.org/dc/terms/ and still nothing.

Import on Desktop Protege with URI=http://purl.org/dc/terms/ seems to work fine.