incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: Collaboration with Akibot
Date Thu, 26 Nov 2009 07:17:48 GMT
Created a Jira item to fix the tag double posting:
https://issues.apache.org/jira/browse/ESME-131

D.

On Thu, Nov 26, 2009 at 7:26 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
> Here what the message looks like on the akibot side:
>
> Yes, it did, this is a dump of the record:
>
> +-----+------+-------------------+---------------------+------------+---------+-----------+---------------------+-------------------------------+---------+--------+----------+-------------+-----+-------+-----------+---------------------+-----------+---------------+--------+
> | id  | mode | remote_message_id | remote_timestamp    | company_id |
> user_id | user_nick | received            | message
>   | private | urgent | reply_to | in_reply_to | via | links |
> processed | processed_at        | situation | sub_situation | entity |
> +-----+------+-------------------+---------------------+------------+---------+-----------+---------------------+-------------------------------+---------+--------+----------+-------------+-----+-------+-----------+---------------------+-----------+---------------+--------+
> | 333 |    0 |              1214 | 2009-11-03 00:00:00 |          3 |
>  1412 | Dick      | 2009-11-25 18:16:02 | Test4 #Akibot
>        #Akibot |       0 |      0 |        0 |           0 |    
|
>   |         1 | 2009-11-25 18:16:03 |         0 |             0 |
>  0 |
> +-----+------+-------------------+---------------------+------------+---------+-----------+---------------------+-------------------------------+---------+--------+----------+-------------+-----+-------+-----------+---------------------+-----------+---------------+--------+
>
> @Vassil: I noticed that message includes the tag twice. Didn't we have
> this problem before but somewhere else in the app.
>
> D.
>
> On Thu, Nov 26, 2009 at 12:24 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
>> Just wanted to inform the list that I just posted an akibot message
>> via an HTTP POST action.
>>
>> So it works.
>>
>> D
>>
>>
>> On Wed, Nov 25, 2009 at 9:06 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
>>> I've started a separate wiki page with detailed information about this
>>> initial use case:
>>> http://cwiki.apache.org/confluence/display/ESME/Akibot+Use+Case+description
>>>
>>> This page can be used for more detailed technical discussions.
>>>
>>> D.
>>>
>>> On Wed, Nov 25, 2009 at 8:51 AM, Richard Hirsch <hirsch.dick@gmail.com>
wrote:
>>>> @Marcelo:
>>>>
>>>> What about using this initial use case as a first step in a
>>>> collaborative process?
>>>>
>>>> The idea would be to establish various iterations so that we don't
>>>> have to tackle everything at once.
>>>>
>>>> The first step would be to leave the akibot configuration exactly as
>>>> it is right now and we just try to get ESME to use the Akibot REST
>>>> API. Once we've accomplished this, we could start changing the akibot
>>>> configuration  (contextual analyzer, etc.) to be more ESME-specific.
>>>>
>>>> D.
>>>>
>>>> On Wed, Nov 25, 2009 at 7:38 AM, Marcelo Pham <marcelo@akibot.com>
wrote:
>>>>> Hi everybody,
>>>>>
>>>>> Thanks Martin and Dick. My name is Marcelo, I'm the head developer of
Akibot
>>>>> and thank you for having Akibot in mind for the ESME project, we feel
proud
>>>>> to involved with this community and happy to help in any way we can.
>>>>>
>>>>> I posted today in the wiki a proposed messaging protocol layout and we're
>>>>> working on improving the documentation and following API ESME format
for
>>>>> incoming messages.
>>>>>
>>>>> A few things:
>>>>>
>>>>> -Akibot used to be hosted in GAE but it is not anymore. Due to database
>>>>> limitations (GAE uses BigTable which has a lot of limitations for
>>>>> performance purposes) we walked out of GAE and are now in the Rackspace
>>>>> cloud, which allows us to expand vertically and horizontally quickly
and
>>>>> easily. We had to migrate the whole code and database, but fortunately
we're
>>>>> done with it. We were able to keep some of the interface with Google
(Google
>>>>> Docs for now)
>>>>>
>>>>> -Use case: we're working on a couple of real life scenarios and wanted
to
>>>>> share a few use cases. Here goes the first one, if you follow this use
case
>>>>> with the diagram I posted in the wiki, it will be a lot easier to understand
>>>>> and follow:
>>>>>
>>>>> One of our beta testers is an online retailer, one of the biggest for
baby
>>>>> products. They carry 20k+ products and their sales, marketing and purchasing
>>>>> processes are very fast paced.
>>>>> Their main groups are the Sales/Marketing group and the Purchasing group.
>>>>> They both use their microblogs to chat about day to day issues.
>>>>>
>>>>> 1. One of the Purchasing employees posted this in the Purchasing micro-blog
>>>>> group:
>>>>> "@victoria I just ordered 3,000 more G70" (G70 is an item "Kidco fireplace
>>>>> gate").
>>>>> to let his boss know that he ordered what they discussed some days ago.
>>>>>
>>>>> 2. Akibot picked up the conversation and understood that 3,000 G70 were
>>>>> ordered (through the contextual analyzer)
>>>>>
>>>>> 3. Akibot inquired the purchasing history for G70 (through an ERP feed)
and
>>>>> noticed that this was an unusual quantity (through the directive processor)
>>>>>
>>>>> 4. Akibot then called up another application that inquiries the price
for
>>>>> G70 in Amazon and other online retailers (through the directive processor
as
>>>>> well)
>>>>>
>>>>> 5. Akibot found that Toys'r'us is selling G70 cheaper (through the directive
>>>>> processor as well)
>>>>>
>>>>> 6. Since Purchasing just ordered more G70, and competitors are selling
it
>>>>> cheaper, there will be a problem!
>>>>>
>>>>> 7. Akibot posts back a message alerting the Sales group:  "Purchasing
just
>>>>> ordered 3,000 more G70. We're selling it at $194.99, the competition
at
>>>>> $184.99 (Toysrus)"
>>>>>
>>>>> 8. Sales will contact Purchasing, and either they lower the price or
cancel
>>>>> the purchase order
>>>>>
>>>>> This "reasoning" that Akibot has, is through directives. This use case
above
>>>>> is one directive. Akibot comes with standard directives and you can add
>>>>> custom directives ("teach" him). These directives can be shared by other
>>>>> companies using Akibot, so the more companies use Akibot, the more Akibot
>>>>> learns...
>>>>>
>>>>> Hope this helps understand Akibot behavior a little bit better and how
it
>>>>> can help companies. Not sure if we should include this in the wiki...
and I
>>>>> can give more use cases if it helps more... please let me know
>>>>>
>>>>> Thanks again and have a great day!
>>>>>
>>>>>
>>>>> Marcelo
>>>>>
>>>>>
>>>>> On Nov 24, 2009, at 3:41 AM, Richard Hirsch wrote:
>>>>>
>>>>>> Martin Böhringer from #ubimic introduced me to Marcelo Pham who
is the
>>>>>> CEO from Akibot.
>>>>>>
>>>>>> Akibot is the first semantic actionable micro-blogging platform for
>>>>>> the enterprise. Akibot not only allows real-time group collaboration
>>>>>> and awareness through short, instant messages (like a Twitter for
the
>>>>>> company), but it also understands those messages and, if applicable,
>>>>>> takes action.
>>>>>>
>>>>>> A good description is provided by a ReadWriteWeb blog (
>>>>>>
>>>>>> http://www.readwriteweb.com/archives/akibot_an_enterprise_twitter_clone_infused_with_ai.php
>>>>>> ).
>>>>>>
>>>>>> What intrigued me about akibot was the semantic analysis of
>>>>>> microblogging messages.
>>>>>>
>>>>>> The basic idea is that akibot functionality can complement existing
>>>>>> ESME functionality. We (the ESME community) aren't able to do
>>>>>> everything.  We should look for partners who will work with us to
>>>>>> further establish microblogging in the enterprise.
>>>>>>
>>>>>> I've started a wiki page to describe the collaboration (
>>>>>>
>>>>>> http://cwiki.apache.org/confluence/display/ESME/Collaboration%20with%20Akibot
>>>>>> ) and would appreciate any thoughts on this new collaboration
>>>>>>
>>>>>> D.
>>>>>
>>>>>
>>>>
>>>
>>
>

Mime
View raw message