On Thursday, November 4, 2010, Nathan <nat...@webr3.org> wrote:
If 303s are killing you then use fragment URIs, if you refuse to use fragments for whatever reason then use something new like tdb:'s, support the data you've published in one pattern, or archive it and remove it from the web.
These are publishing alternatives, but I'm focussed on the 303 issue here.
Why? 303 is a sub issue not the real issue - Why not compare which style
(slash, frag, tdb) is the least ambiguous, easiest to deploy and
consume, kindest to the network and to servers, and /then/ work at
fixing the issues with that one.