Yes plan is 1. Receive tweets via ESB as strings 2. Send to CEP 3. Extract data using CEP string toolbox 4. Write CEP extension to run trained model (that can be added to NLP toolbox)
--Srinath On Wed, Nov 5, 2014 at 1:07 AM, Sriskandarajah Suhothayan <[email protected]> wrote: > Since out NLP tool box doesn't support this > +1 for an extension, but do make this extension generic as much as > possible so that we can use this for other scenarios too. > > Regards > Suho > > On Tue, Nov 4, 2014 at 1:44 AM, Malithi Edirisinghe <[email protected]> > wrote: > >> Hi Madhawa, >> >> I agree with you on above. We moved to the Stanford NLP library due to >> some limitations we had in implementing the queries we planned using Open >> NLP lib. This was discussed at architecture@ under "[Architecture][CEP] >> NLP Toolbox". >> >> AFAIK Stanford NLP lib also can be used with custom models; but, we will >> have to research on that a bit and improve the existing implementation of >> the NLP query extension to support that. >> >> Thanks, >> Malithi. >> >> On Tue, Nov 4, 2014 at 11:44 AM, Madhawa Gunasekara <[email protected]> >> wrote: >> >>> Hi All, >>> >>> We cannot use existing NLP toolbox for our use case since it was >>> implemented using Stanford NLP. Plus it cannot be used for loading custom >>> trained models. We have already implemented most of the NLP parts using >>> Apache OpenNLP. Therefore we are planning to write a custom adapter for NLP >>> purpose. Please give your suggestions. >>> >>> Thanks. >>> Madhawa >>> >>> On Mon, Nov 3, 2014 at 12:05 PM, CD Athuraliya <[email protected]> >>> wrote: >>> >>>> Hi all, >>>> >>>> We are working on a road traffic extractor from Twitter feed. Here we >>>> are extracting useful road traffic information from a public Twitter feed >>>> using natural language processing tools and then publishing to WSO2 >>>> CEP. Feed was narrowed down to @road_lk Twitter account, popular for >>>> posting free crowd sourced traffic alerts. @road_lk feed also was used >>>> train NLP models which are utilized for name entity recognition. >>>> >>>> In real time scenario, users can view/search for road traffic from a >>>> web UI and also can subscribe for a location to receive traffic alerts >>>> regularly. To generate traffic information available in feed alerts, >>>> Twitter feed is processed in two steps. First each tweet will go through >>>> the NLP module and location, traffic level will be extracted from it. Then >>>> these extractions will be published to CEP as an input event stream. Custom >>>> Siddhi queries will further process streams to generate traffic information >>>> according to user request which will be published back to web UI or to >>>> alerts. >>>> >>>> We have currently implemented modules given in the diagram. At our last >>>> code review it was suggested to make following changes to our current >>>> implementation. >>>> >>>> 1. Use ESB or CEP as the data publishing server instead of a custom >>>> server >>>> 2. Use existing NLP toolbox for name entity recognition >>>> 3. Use ESB Twitter connector for Twitter interactions >>>> 4. Integrate implemented extra UI features to existing geo-dashboard >>>> >>>> >>>> >>>> Your valuable feedback and suggestions on above changes will be much >>>> appreciated. >>>> >>>> Thanks and best regards. >>>> >>>> -- >>>> *CD Athuraliya* >>>> Software Engineering Intern >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> Mobile: +94 716288847 >>>> LinkedIn <http://lk.linkedin.com/in/cdathuraliya> | Twitter >>>> <https://twitter.com/cdathuraliya> | Blog >>>> <http://cdathuraliya.tumblr.com/> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Madhawa Gunasekara* >>> Software Engineering Intern >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 719411002 >>> >>> >>> >> >> >> -- >> >> *Malithi Edirisinghe* >> Senior Software Engineer >> WSO2 Inc. >> >> Mobile : +94 (0) 718176807 >> [email protected] >> > > > > -- > > *S. Suhothayan* > Technical Lead & Team Lead of WSO2 Complex Event Processor > *WSO2 Inc. *http://wso2.com > * <http://wso2.com/>* > lean . enterprise . middleware > > > *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: > http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: > http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: > http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* > -- ============================ Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://people.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
