I got asked on Twitter on how I would use Content-Location
with Linked Data, see https://twitter.com/elfpavlik/status/605693139119153153.
I'm referring to my remark from the Trifid-LD Readme:
Trifid-LD does not care about HTTPRange-14 and neither should you. We consider the extra 303 redirect round-trip a waste of precious response time. You get back what you asked for in content-negotiation.
As you can see later in the text we did think about the Content-Location
header but didn't implement it so far. The reason is pretty simple: While I understand the problem (up to some point at least) from a meta-level I fail to see where this is an issue in the real world. I'm just an engineer and maybe I'm oversimplifying things here but as long as no one gives me a clear explanation on why this will lead to real world problems, I will continue to ignore HTTPR