Harry Halpin wrote:
The question is how to build Linked Data on top of *only* HTTP 200 -
the case where the data publisher either cannot alter their server
set-up (.htaccess) files or does not care to.
(1) use fragments
(2) if using slashes, admit "I was wrong" and migrate data (REAL uris do
change)
(3) come up with a fragile set of rules fro slash URIs that only a small
percentage of the web even knows about, let alone understands
(1) is easy, (2) is harder but possible, (3) is what will probably
happen, and it's what people want, 200 OK and sort out the mess via
reasoning later (hopefully).
IMHO, it really is that simple.
Nobodies willing to discuss (2), (1) isn't used 100% of the time, so it
has to be (3).
Doesn't matter what obscure processing rules anybody here comes up with,
most of the web won't know about them let alone implement. So it has to
be just 200 OK your slashes and we'll either manage to sort out the mess
later or junk the ambiguous data.
The answers aren't in the specs, this is a reality issue, and reality
conflicts with what some want, so reality distortion is needed.
Best,
Nathan