| |
 |
Tuesday, June 04, 2002 |
|
Groovespace, blogspace, and Google: Q and A from Michael Herman
A little Q and A from Michael Herman, CTO of Parallelspace:
Q: What happens to edge-based content as it ages? e.g. a richly populated Groove shared space?
A: As soon as the content can be indexed and searched, it may physically live at the edge but logically, it becomes a center-based resource.
Q: What is Google?
A: Google is the world's largest distributed document management system. [Michael Herman, Parallelspace]
My question for Michael (with whom I had several hours of enjoyable debate, at ETCON, about Groovespace vs blogspace) is:
Q: How do you maximize the horizon of observability in Groovespace?
A: I don't know. I think about it a lot, though. I agree that edge services are key, but I don't see the whole picture clearly (yet).
4:48:38 PM 
|
|
|
"Its in the spec, it's ten lines of code, just bloody write it!" - Simon Fell
4:25:03 PM
|
|
|
Visualizing XML with Flash
Jeremy Allaire wrote to point out an interesting Flash visualization of the Macromedia resource feed. It uses the two extra metadata elements in the feed -- resource type and product -- as handles for filtering. The presentation is a bit confusing because your eye tries to put the product indicators into a tabular layout that is (falsely) implied by the resource type names. That row of names reads as a table header, but isn't one. Still, very slick!
Will we soon see a convergence of interest between the social network visualizers and the Flash developers? I hope so.
12:03:31 PM
|
|
|
Bold neighbors
Some weblog neighbors who should be bold are not:
My Weblog Neighborhood. Odd that my site is on the list but is not bold. [Sam Ruby]
I think I see the problem. Sam's page contains <link> elements in the body as well as the head. I suspect the fix is to run html.parseLinks against only the content of the <head> element of the HTML page. The harvester can perhaps use tcp.httpClient(method:'HEAD'...) instead of the default method:'GET'? I will try to fix this when I get a chance, but have no time today.
(These kinds of data-related bugs are fascinating. Is there a name for them?)
I spoke with Jon Schull yesterday, who's very interested in visualizing this data. As I mentioned to him, the weblog neighborhood tool is just one of many possible approaches. Its prime virtue, I think, will be to make visible who is, and is not, traversable in this new way. Once many blogs support the new style, there are many paths forward. Jon Schull, I hope, will do his own spidering and visualization. Ideally Google would exploit this new information as well. This is exactly what I meant when I said that the Google API is a two-way street.
9:53:35 AM
|
|
© Copyright 2002 Jon Udell.
|
|
