As the mapping to RDF for Lexemes is not defined yet we should disable the RDF export for Lexemes for the first roll-out in order to not let people get used to a wrong/random mapping.
Notes:
Return http code that says the resource isn't there.
Description
Description
Details
Details
Related Objects
Related Objects
Event Timeline
Comment Actions
That should probably be a 501 "Not Implemented", see https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_errors.
Comment Actions
I would suggest 501 Not Implemented. Alternatively, we could respond with 204 No Content or nginx’ nonstandard 444 No Response.
If we change our mind, and keep the partial RDF which we currently produce (assuming that we will want to add to it, but not change it), 206 Partial Content sounds appropriate.
Comment Actions
Also, requesting a form ID (example) currently returns a 400 Bad Request. We might want to change that to a different HTTP code as well. (Though I must admit I don’t know what our plan for those URIs is.)
Comment Actions
Change 398486 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/Wikibase@master] Intorduce disabledRdfExportEntityTypes repo config variable
Comment Actions
With https://gerrit.wikimedia.org/r/#/c/398486 merged we'd need a config on wikidata-lexeme.wmflabs.org, no?
Comment Actions
Change 398486 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Introduce disabledRdfExportEntityTypes repo config variable
Comment Actions
Change 399225 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/Wikibase@master] Treat ttl format as rdf
Comment Actions
Change 399225 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Treat ttl format as rdf