 |
Tim Knip/Suite75: 6/5/02 10:48 AM
yo!
Jeroen Bekkers/Suite75: 6/5/02 10:50 AM
yo
Tim Knip/Suite75: 6/5/02 10:48 AM
http://www.xmethods.com
Tim Knip/Suite75: 6/5/02 10:48 AM
check available webservices...
Jeroen Bekkers/Suite75: 6/5/02 10:51 AM
ok
Tim Knip/Suite75: 6/5/02 10:50 AM
hehe, kan ik nu allemaal gebruiken vanuit groove
Tim Knip/Suite75: 6/5/02 10:52 AM
maar goed... nu eerst een toepassing verzinnen...
Tim Knip/Suite75: 6/5/02 10:54 AM
maar tof hoor, google api: search, spelling-suggestion etc
Jeroen Bekkers/Suite75: 6/5/02 11:02 AM
just invited Jon Udell
Jeroen Bekkers/Suite75: 6/5/02 11:05 AM
just invited Hugh Pyle
Jeroen Bekkers/Suite75: 6/5/02 11:05 AM
Hi jon
Jon Udell: 6/5/02 11:04 AM
Hi Jeroen and Tim
Tim Knip/Suite75: 6/5/02 11:04 AM
hi Jon
Jeroen Bekkers/Suite75: 6/5/02 11:06 AM
hi, i thought let's open this space to discuss some integration scenario's
Jeroen Bekkers/Suite75: 6/5/02 11:07 AM
Tim has been doing some nice experiment to integrate Groove and Radio and we feel it's a powerfull combination
Tim Knip/Suite75: 6/5/02 11:05 AM
with upcoming Groove Edge Services, integration could be compelte...
Jon Udell: 6/5/02 11:06 AM
Can Tim's work be demonstrated here?
Tim Knip/Suite75: 6/5/02 11:06 AM
I have to make a tool first, hehe
Jeroen Bekkers/Suite75: 6/5/02 11:08 AM
hi Hugh
Jeroen Bekkers/Suite75: 6/5/02 11:08 AM
can you invite matt and John , i don't have their vcards
Hugh Pyle/Groove: 6/5/02 11:11 AM
Hi Jeroen - greetings from rainy England. (Dylan's happy, though - Ireland 1:1 against Germany!)
Tim Knip/Suite75: 6/5/02 11:07 AM
had to get to grips with SOAP, WDSL etc...
Hugh Pyle/Groove: 6/5/02 11:11 AM
Sure
Tim Knip/Suite75: 6/5/02 11:07 AM
hehe! last minute!
Hugh Pyle/Groove: 6/5/02 11:13 AM
Just catching up - back later
Hugh Pyle/Groove: 6/5/02 11:13 AM
I invited Matt and John
Jeroen Bekkers/Suite75: 6/5/02 11:11 AM
ok, thx,
Jeroen Bekkers/Suite75: 6/5/02 11:13 AM
Tim, can't we add an early version of the blogger tool ?
Jon Udell: 6/5/02 11:12 AM
I'd be very interested to see that.
Tim Knip/Suite75: 6/5/02 11:12 AM
sure, but it's not SOAP. Blogger Tool uses XML-RPC / Blogger API
Tim Knip/Suite75: 6/5/02 11:12 AM
blogger.com only...
Jon Udell: 6/5/02 11:13 AM
Why only blogger.com?
Tim Knip/Suite75: 6/5/02 11:13 AM
oops... description not found
Tim Knip/Suite75: 6/5/02 11:14 AM
it was start of exploration XMLRPC + SOAP
Tim Knip/Suite75: 6/5/02 11:14 AM
after succeeding using blogger.api started checking out SOAP
Matt Pope/Groove: 6/5/02 11:20 AM
Hello all
Jon Udell: 6/5/02 11:16 AM
FWIW, XML-RPC and blogger API are the most prevalent integration path in blogspace today. I regard the transition from that to SOAP as a relative non-issue. The big issue, to me, is how to construct a user experience that makes sense for conversations flowing between the two worlds.
Tim Knip/Suite75: 6/5/02 11:16 AM
Hi Matt.
Tim Knip/Suite75: 6/5/02 11:17 AM
y, Jon, I agree: I now have the knowledge to create an experience. Question is: what experience
Jeroen Bekkers/Suite75: 6/5/02 11:19 AM
hi matt
Matt Pope/Groove: 6/5/02 11:23 AM
Hey Jeroen. IMO, the experience needs to be seamless. Jon is correct in that we don't need edge services or any other hooks now to test the concept. But we do need a more seamless transition for the experience to pass some threshold of usability. There need to be on-ramps and off-ramps in between Groove and any other application or system, Radio or otherwise.
Matt Pope/Groove: 6/5/02 11:24 AM
I'm going to invite John Burkhardt to this space.
Jon Udell: 6/5/02 11:21 AM
What experience: exactly. I know there have been some use cases articulated already. Probably by one of you guys. Can those be captured here as a point of reference?
Tim Knip/Suite75: 6/5/02 11:22 AM
The Blogger Tool (new version) connects to blogger.com or RU just to send posts to the blog. Posts can be edited etc.
Matt Pope/Groove: 6/5/02 11:34 AM
The experience I was referring to in my post is the following (again, just one example): 1) Many people are operating in blogspace, making posts, perusing eachothers, but limited by time in the extent to which they can become engaged in all that they may find interesting, 2) Somebody makes a post that merits a more intimate and dynamic conversation than can be accounted for in an I-post-you-post sort of way (admittedly participants may not realize this until they've already been through a few I-post-you-post cycles), 3) The dialog gets brought into groovespace - via a seamless on-ramp - where contextual tools and new participants can be added readily, 4) when the discussion/collaboration ends, or through intermittent updates from a persistent discussion, participants post information/results back into blogspace - via an off-ramp - from the Groove shared space for a wider audience to consume. Further, linking and syncing with public groovespaces from weblogs would make the integration even tighter.
Matt Pope/Groove: 6/5/02 11:34 AM
again, that was just one "experience" example
Tim Knip/Suite75: 6/5/02 11:33 AM
the off-ramp is easy, wondering how to do the on-ramp...guess this could be done by some invitation-link?
Jon Udell: 6/5/02 11:34 AM
Matt: I think this is perhaps the central use case. Lots of questions to resolve. For example, does "dialog gets brought into groovespace" mean importing a structure of links, or fully replicating the content. In either case, how are the boundaries of the dialog defined?
Matt Pope/Groove: 6/5/02 11:38 AM
True, you've done the off-ramp. We've done other forms of on-ramps. For instance, we have an Outlook on-ramp that allows a user to rather easily move an email thread into a new Groove space and simultaneously invite the email thread participants to that space. Same concept should apply here.
Matt Pope/Groove: 6/5/02 11:41 AM
Jon, those are great questions. I don't have a readied answer, but I think the Outlook on-ramp example provides some insight. Having said that, it is different within blogspace because of the fact that there is no single "place" to import stuff from; there may be a 5-way blogspace dialogue - how do we pull the relevant info from each place? And how do we determine what is relevant? Good questions
Jon Udell: 6/5/02 11:43 AM
Matt: Agreed. The answer is emerging, I suspect. We see blogs beginning to be conscious of, and to encode, their relationships to other blogs. I'm sure this will continue because people are finally seeing it is in their own self-interest to be more formally self-descriptive.
Tim Knip/Suite75: 6/5/02 11:43 AM
let the Google API make a search? check the urls's you want into that space. Hmmm, the url's must be accessible via Blogger API... just thinking aload
Matt Pope/Groove: 6/5/02 11:52 AM
All, I need to check out of here to go prepare for a meeting this afternoon. BUT, I would love to see this conversation persist over time. I will check back later to add further thougts and comments. Jeroen, thanks for creating this space!
Jeroen Bekkers/Suite75: 6/5/02 11:51 AM
ok, see you later, just invite other interested people..
Jeroen Bekkers/Suite75: 6/5/02 11:56 AM
I think for any tool or integration scenario it's important that people still feel the Grovespace is a secure environment, having a all or nothing button can make people a bit hesitant in expressing their thoughts in the Groovespace thinking that any moment all contents can be published. i can think of some explicit non-to-be-published area's within a space/scenario
Jeroen Bekkers/Suite75: 6/5/02 11:59 AM
but again many scenario's possible from simple collaborative blogging (for a conference etc) or in a bigger framework like Rendeszvoo.net with a more open and fluid interaction between spaces of different intrest
Jon Udell: 6/5/02 12:06 PM
Like Matt, I have to run. But will check back. Thanks for inviting me here!
Jeroen Bekkers/Suite75: 6/5/02 12:10 PM
ok, later :-)
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:14 PM
Hi John
Jeroen Bekkers/Suite75: 6/5/02 1:22 PM
hi michael
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:21 PM
Hi Jeroen
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:22 PM
I was just looking for some information on a Asynch Pluggable Protocol (app) handler I wrote called "ddtp:"
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:23 PM
It enable web developers write plain own HTML web page based web sites and host them in an offline Outlook/Exchange public folder
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:23 PM
e.g. ddtp://localhost/ddtproot/default.htm
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:24 PM
in your browser would render the HTML content, MS Word docs, etc.
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:24 PM
There's no reason why the same could be written for Groove (with EasyWeb as a base).
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:25 PM
...or for that matter, write an HTTP server that runs as a local Groove tool
Michael Herman (Parallelspace V2#3)/Parallelspace Corporation: 6/5/02 1:28 PM
...continued in http://parallelspace.blogspot.com/ |