Accessing Wikidata resources forbidden (User Agent?)

[John Gomersall]

I'm building a SKOS ontology which has references to WikiData entries, e.g.

@prefix ex: <https://example.org#> .

@prefix skos: <http://www.w3.org/2004/02/skos/core#> .

@prefix wd: <http://www.wikidata.org/entity/> .

ex:fruit a skos:Concept;

  skos:exactMatch wd:Q1364;

But when I try to double click on the link in the Resource pane I get:

Server returned HTTP response code: 403 for URL: https://www.wikidata.org/entity/Q1364

I think this might be because of the User Agent that Semantic Turkey is using when it makes the query to the WikiData endpoint, as the following works fine:

curl -H "Accept: text/turtle" -L http://www.wikidata.org/entity/Q1364

Is there a way to configure the User Agent string that is used to avoid this?

Cheers, John

[Peter Viskup]

According to UA Policy, any 'default UA' is in question of blocking by Wikimedia.

https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy

Nevertheless, possibility to configure specific UA is crutial.

It just might seems to be weird in contrast to Chromium's deprecation of UA headers and proposal/implementation of UA Hints headers.

https://chromestatus.com/feature/6224706757853184

And the last notice of Wikimedia's way to deal with huge load of 'AI agents' is the proposal of Enterprise API

https://enterprise.wikimedia.com/

Peter

Dňa pi 3. 7. 2026, 17:40 John Gomersall <the...@gmail.com> napísal(a):

--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/3f4ad8f8-aed9-4b94-a3a9-677856f004c9n%40googlegroups.com.

[John Gomersall]

Hi Peter,

I assume from your response that there is no way to configure the User Agent header at the moment?

The Chrome article seems to be more about reducing the information in the UA header rather than removing it. When I looked the header is still there and quite comprehensive and seems to still keep Wikidata happy (e.g. "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36")

I'm not sure that the Enterprise API is ideal as I would like to include a functional URL in our RDF document and we wouldn't want to include API keys in that.

John