It would be quite useful for me to get the RDF representation of an entity when doing an http request with Accept: header set to an RDF serialization. For instance:
```
$ curl -I https://www.wikidata.org/entity/Q445460 -H "Accept: text/turtle"
HTTP/2 303
content-type: text/html; charset=iso-8859-1
location: https://www.wikidata.org/wiki/Special:EntityData/Q445460
...
```
and/or
```
$ curl -I https://wikidata.org/wiki/Special:EntityData/Q445460 -H "Accept: text/turtle"
HTTP/2 301
content-type: text/html; charset=iso-8859-1
location: https://www.wikidata.org/wiki/Special:EntityData/Q445460
...
```
Should return RDF or a link to the .ttl URL. For comparison, DBPedia does that:
```
$ curl -I http://dbpedia.org/resource/Shantideva -H "Accept: text/turtle"
HTTP/1.1 303 See Other
Content-Type: text/turtle
...
Location: http://dbpedia.org/data/Shantideva.ttl
Alternates: {"/data/Shantideva.atom" 0.500000 {type application/atom+xml}}, {"/data/Shantideva.jrdf" 0.600000 {type application/rdf+json}}, {"/data/Shantideva.jsod" 0.500000 {type application/odata+json}}, {"/data/Shantideva.json" 0.600000 {type application/json}}, {"/data/Shantideva.jsonld" 0.500000 {type application/ld+json}}, {"/data/Shantideva.n3" 0.800000 {type text/n3}}, {"/data/Shantideva.nt" 0.800000 {type text/rdf+n3}}, {"/data/Shantideva.ntriples" 0.500000 {type application/n-triples}}, {"/data/Shantideva.ttl" 0.700000 {type text/turtle}}, {"/data/Shantideva.xml" 0.950000 {type application/rdf+xml}}
...
```