| daniel added a comment. |
In T119536#2938483, @thiemowmde wrote:Please correct me if I'm wrong, but this is what I understand:
Your are correct, though we should also consider convenience.
- https://www.wikidata.org/entity/Q36661 is what we call a canonical concept URI. This is supposed to be called without a file extension, and supposed to do content negotiation.
The canonical URI does not have a file extension. But being able to call /entity/Q64.json is very convenient. I'd like to keep support for it if that can be done without too much trouble.
- Special:EntityData is supposed to be called with a file extension. We want this to be cacheable.
Yes. E.g. https://www.wikidata.org/wiki/Special:EntityData/Q36661.json is the canonical URI (and URL) of the JSON document describing Q36661.
The fact that the same special page also does content negotiation is a technical detail, because the code doing this must be somewhere.
Indeed.
This means https://www.wikidata.org/wiki/Special:EntityData/Q36661 is a technical detail that could as well be hidden.
Yes, indeed. But the URL will be used internally (that's what /entity/Q36661 gets rewritten to) to trigger content negotiation. Preventing external access while allowing internal access may not be trivial, and cause confusion. Supporting this URL externally may also be useful for testing.
What am I missing? What could be the worst negative effect this change may have?
I don't see any. It just needs doing.
Cc: Esc3300, thiemowmde, hoo, elf-pavlik, JanZerebecki, Aklapper, StudiesWorld, daniel, D3r1ck01, Izno, Luke081515, Wikidata-bugs, aude, fbstj, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
