Thank you Dick.
Already retweeted.
/Anne
On 19. nov. 2009, at 09.12, Richard Hirsch wrote:
Just blogged about our cooperation with #ubimic
http://blog.esme.us/collaborative-efforts-with-ubimic/
D.
On Sun, Nov 15, 2009 at 7:42 AM, Anne Kathrine Petterøe
<[email protected]> wrote:
Sorry, I have been so quiet on this thread.
In between work and travels, and finishing the design of the new UI
I simply
didn't find the time.
I am happy to see the collaboration take place and once the UI is
up and
running I should have more time to help you out here.
/Anne
On 13. nov. 2009, at 10.00, Richard Hirsch wrote:
Thanks.
I'll work on some more details for the scenarios this weekend.
D.
On Fri, Nov 13, 2009 at 8:41 AM, Martin Böhringer
<[email protected]> wrote:
I pointed Marcelo from akibot to our conversation. He is very
interested
and
will come back to us.
Martin
-----Ursprüngliche Nachricht-----
Von: Richard Hirsch [mailto:[email protected]]
Gesendet: Donnerstag, 12. November 2009 08:30
An: [email protected]
Betreff: Re: Collaboration with #ubimic
I was looking at the akibot offering last night and it does look
interesting. Depending on the current akibot architecture, it
might be
relatively easy to create an ESME bot based on their existing
technology. They could market their engine as a standalone
component
and offer it to customers who want to track twitter or other
microblogging systems such as ESME. The bot could analyze the
messages and either create new messages or integrate with back-end
applications. It would be a loosely-coupled integration.
We talked about having tightly-integrated plugins a while back but
never looked at it in more detail.
We should keep akibot in mind and as things develop maybe you
connect
us up to see how we might collaborate.
D.
On Thu, Nov 12, 2009 at 8:17 AM, Martin Böhringer
<[email protected]> wrote:
Hi Dick,
the current status on our student research is as following: I
have a
student
who works on the LEGO thing, the hardware is all built up and the
software
part of the project starts tomorrow with a kickoff. Another
student
is
working in his bachelor thesis on the "text analysis in
information
streams"
topic. A bachelor thesis is not that big but I hope at least
that we
get
some insights in what is possible and what not. He also should
look
at
public available APIs (like opencalais and similar) and test them
with
microblogging-like texts.
I know from the akibot guys (akibot.com) that they want to go
in a
similar
direction like us (supporting a ubiquitous microblogging scenario
with their
artificial intelligence microblogging bot). So this might be a
good
future
collaboration opportunity, too.
What I would do next is looking for a student who wants to work
intensively
on the SAP/ESME scenario. Give me a view weeks for that.
Vassil has a good point here with the business value. We are all
working in
microblogging and therefore say "hey, tweeting SAP systems are
really
cool".
However, "normal" people might not have this enthusiasm. Until we
have real
demo systems running little mockups (GUI prototypes) might do
it. We
have it
on our agenda to create a #ubimic presentation where we state
out the
motivation and the benefits. I hope to give some answers to the
business
value topic in this presentation.
Cheers
Martin
-----Ursprüngliche Nachricht-----
Von: Richard Hirsch [mailto:[email protected]]
Gesendet: Mittwoch, 11. November 2009 23:28
An: [email protected]
Betreff: Re: Collaboration with #ubimic
Hi Martin,
I see that you are doing some pretty cool stuff (for example,
"Text
Analysis in Information Streams: Status Quo and Future
Perspectives
(http://www.tu-chemnitz.de/wirtschaft/wi2/wp/en/2009/08/10/text-
analysis-in-information-streams-status-quo-and-future-
perspectives/)".
What about including a text analysis aspect to the
collaboration?
D.
On Wed, Nov 11, 2009 at 3:19 PM, Vassil Dichev <[email protected]
>
wrote:
Hi Martin,
Like I said last week when we first found out about #ubimic,
you
seem
to think along the same lines as the ESME team. So I can't
find a
any
reason why we shouldn't cooperate.
IMHO David has defined very well the differentiating
characteristics
of ESME: real-time responsiveness and actions. Actions also
have
some
vague similarity to some Google Wave bots. More importantly,
actions
are important in many integration scenarios, which is the
goal of
ESME.
What I'm eagerly awaiting is a description of some of the
benefits
of
the "aggregated data from people and things" in different
scenarios,
but I guess that's one of the goals of the collaboration ideas,
right?
Best Regards,
Vassil
