RE: referendum on httpRange-14 (was RE: "information resource")

Patrick Stickler writes:

> Forced indirect access to representations via
> URIrefs with fragment identifiers is inefficient
> and non-scalable. Yes, it can work in some cases,
> for some applications, for some data. But it is
> *not* a scalable solution for the future of the
> web and semantic web.

With the caveat that I'm still coming up to speed in this long-running 
debate and have not formed firm opinions, I have some sympathy with the 
particular statement above.  There is at least conceptual and perhaps 
operational overhead in requiring that one resource be indirectly 
identified as secondary to another, unless that relationship is for other 
reasons natural.    That doesn't by any means settle the httpRange-14 
question, but I agree with the point taken in isolation. 

That said, my understanding is that the TAG has in Basel suggested a way 
forward, documented in the draft minutes at [1].  Specifically: 

"RESOLVED: to drop [I.e. from the Architecture Document draft...Noah] the 
HashSlashDuality text (section 2.2.1 and descendants in a draft that was 
projected) and use as input to finding on HTTPrange-14, DC, TBL 
abstaining. ACTION DC: with Norm, develop a finding on httpRange-14 
starting with the HashSlashDuality text"

I suggest that many of the important points on both sides of the debate 
have been made (perhaps more than once?) in this email thread, and thus my 
preference would be to back-burner the email  discussion until some 
progress is made on a draft finding.  Then we'll have something concrete 
to debate and tune. 



Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142

Received on Wednesday, 20 October 2004 14:41:08 UTC