- From: David R. Karger <karger@theory.lcs.mit.edu>
- Date: Tue, 8 Apr 2003 01:05:21 -0400
- To: ks@micky.hpl.hp.com
- CC: john.erickson@hp.com, www-rdf-dspace@w3.org
Date: Mon, 7 Apr 2003 12:12:17 -0700 From: Kevin Smathers <ks@micky.hpl.hp.com> Cc: www-rdf-dspace@w3.org Content-Disposition: inline X-Archived-At: http://www.w3.org/mid/20030407121217.A11088@micky.hpl.hp.com X-Mailing-List: <www-rdf-dspace@w3.org> archive/latest/133 X-Loop: www-rdf-dspace@w3.org X-SBClass: Nonlocal Origin [156.153.255.206] X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: X-SpamBouncer: 1.5 (2/23/03) X-SBPass: NoBounce X-SBClass: OK X-Folder: Bulk On Mon, Apr 07, 2003 at 12:54:54PM -0400, John S. Erickson wrote: > > Kevin asks: > > So the question I am left with is: why do you think > > that Simile clients should not be limited to web browsers? > > Well, for one thing, the Haystack client is not technically a "web browser" > I agree of course. Still this is the first suggestion I've seen that the Haystack client would be used with Simile. My impression was rather that the Haystack UI would be ported, minus the client, using a Web UI interface. It's a bit questionable where the haystack UI ends and the client begins. Certainly the maximum power of haystack is achieved by the full system. Arguably, there is some value to using some of the haystack "back end" (learning agents, etc) to record and adapt to user interactions directed through a web browser. But a web browser is really quite a limited interface; we'll get a lot more power using the full haystack UI.
Received on Tuesday, 8 April 2003 01:01:02 UTC