Lookup service has been down for some time

1

Hi

The lookup service seems to have been down for several weeks.

Any pointers as to who manages this service or whether it will be back up soon?

Thanks

Paul

2

Noticed the same and interested when the service is going to be up again.

3

Any news?
It is not working now.

4

It looks like it’s back up but it seems the response might have changed slightly. I’m seeing an ‘id’ property where before there was a ‘resource’ property.

5

Lookup is working again but might have changed due to small changes in the configurations. I will revert back to “resource” for the uri then, otherwise it might break some apps.

Also there still seems to be a problem with the XML formatting, I will have a look.

EDIT: I just checked the implementation and the change to “id” will stay as it is tied to the new feature of join queries and is more consistent with the naming of lucene and solr. It is now recommended to use “id” in applications to get the resource identifier. I will try to add “resource” to the DBpedia lookup result sets and set it to the same value as “id”.

6

Up again with the “resource” field re-added and the xml formatting working

1 Like
8

It has been solved.

9

If the lookup service has been down for several weeks, start by identifying who manages it—this info is usually available in the documentation or support sections. Check if they have a status page where they post updates about outages. If no information is available, contacting customer support can give you more details about the issue and when it might be resolved. You can also look for updates on social media or community forums, as users or the service provider may have posted something there. In the meantime, consider finding a temporary alternative if the service is critical for your work.