- From: Kjetil Kjernsmo <kjetil@kjernsmo.net>
- Date: Sat, 24 Apr 2010 22:17:39 +0200
- To: Lee Feigenbaum <lee@thefigtrees.net>
- Cc: public-rdf-dawg-comments@w3.org
On Saturday 24. April 2010 15:42:31 Lee Feigenbaum wrote: > Could you give me an idea of what impact this would have on the > specification / implementations of the HTTP protocol? I'm not sure I > understand the consequences. Is there a test case or the like that > illustrates the effect of adopting httpRange-14 as a normative > reference? > So, that's what I plan to write one of these days. :-) I think that the impact is relatively minor for most of the SPARQL WG work, and the main impact is that if something gives a 200 code when dereferenced, it has to be an information resource. This may impact the work in areas where HTTP is getting involved in working with stuff that are not thought of as information resources. However, as I said in my previous mail, I think the WG should rather be concerned with the impact on the semweb community as a whole if the httpRange-14 finding is *not* adopted as a normative reference, as I think that would be very severe. Possibly take it up with the SWCG. If it is minor on SPARQL, but severe on the community, then it is most reasonable for SPARQL to adopt it even though it does have some impact. Cheers, Kjetil -- Kjetil Kjernsmo kjetil@kjernsmo.net http://www.kjetil.kjernsmo.net/
Received on Saturday, 24 April 2010 20:18:40 UTC