Bravo Harry :-) let me also add without adding anythng to the header.. *keeping HTTP completely outside the picture* http header are for pure optimization issues, almos networking level. Caching fetching crawling, nothing to do with semantics.
A conjecture: the right howto document is about 2 pages long it says something"simply put RDFa on your pages and.. ( a) there is a default interpretation which works 99.99% of the time e.g. "if it has RDFa it talks about something that's an entity and its not a page" or b) you add a triple but no triple means by default that.. or c) .... ") we're almost there i feel it. Gio On Thu, Nov 11, 2010 at 1:50 AM, Harry Halpin <[email protected]> wrote: > On Wed, Nov 10, 2010 at 11:15 PM, David Wood <[email protected]> wrote: >> Hi all, >> >> I've collected my thoughts on The Great 303 Debate of 2010 (as it will be >> remembered) at: >> http://prototypo.blogspot.com/2010/11/another-guide-to-publishing-linked-data.html >> >> Briefly, I propose a new HTTP status code (210 Description Found) to >> disambiguate between generic information resources and the special class of >> information resources that provide metadata descriptions about URIs >> addressed. >> >> My proposal is basically the same as posted earlier to this list, but >> significantly updated to include a mechanism to allow for the publication of >> Linked Data using a new HTTP status code on Web hosting services. Several >> poorly thought out corner cases were also dealt with. > > I don't this solution cuts it or solves the problem to the extent that > Ian Davis was proposing. To recap my opinion, the *entire* problem > from many publisher's perpsectives is the use of status codes at all - > whether it's 303 or 210 doesn't really matter. Most people, they will > just want to publish their linked data in a directory without having > to worry about status codes. So, de facto, the only status code that > will matter is 200. > > 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. > >> >> I look forward to feedback from the community. However, if you are about to >> say something like, "the Web is just fine as it is", then I will have little >> patience. We invent the Web as we go and need not be artificially >> constrained. The Semantic Web is still young enough to be done right (or >> "more right", or maybe "somewhat right"). >> >> Regards, >> Dave >> >> >> >> >> >> > >
