+1 This configuration looks very neat and concise.
If the ML mediator will be primary used on a single domain, would it make
sense to include an optional domain attribute to the ML node? I could see
two uses for an optional domain attribute:
1. It could be useful for logging, annotation and troubleshooting.
2. Perhaps it could be used as a default filter?
<ml domain="string">
<model storage-location="string"/>
<feature name="string" expression="xpath"/>+
<prediction expression="xpath"/>
</ml>
Perhaps 'target-domain' or 'domain-name' would be better than simply
'domain'. Perhaps this is just duplicating functionality of the 'name'
attribute and filter mediator. WDYT?
Thanks,
Colin Roy-Ehri
Software Engineer
*WSO2, Inc. : wso2.com <http://wso2.com/>*
*Mobile* : 812-219-6517
On Tue, Mar 24, 2015 at 12:00 PM, Manorama Perera <manor...@wso2.com> wrote:
> Hi,
>
> ESB mediator for WSO2 ML enables making use of the models generated by
> WSO2 Machine Leaner, to predict values in message mediation in ESB.
>
> - Machine Learner feature needs to be installed in ESB prior to
> configure the ML mediator.
> - Mediator will extract the data from the incoming messages and send
> to the ML model as features.
> - The mediator use the Machine Learner features to predict the output
> value for every message passing through the mediator.
>
> *Proposed Mediator Configuration*
>
> <ml>
> <model storage-location="string"/>
> <feature name="string" expression="xpath"/>+
> <prediction expression="xpath"/>
> </ml>
>
> *model*
> storage-location : Storage location of the generated model.
>
> *feature*
> name : Feature name according to the generated model.
> expression : XPath expression used to determine the feature value.
>
> *prediction*
> expression : XPath expression to determine the location to insert the
> predicted value.
>
> The generated models can be applied to predict only the data coming from
> the same domain, as the data used to train the model. So the mediator
> should be configured only to mediate messages which carry data coming from
> the same domain, as the data used to train the model.
>
> Any suggestion are appreciated.
>
> Thanks.
>
> --
> Manorama Perera
> Software Engineer
> WSO2, Inc.; http://wso2.com/
> Mobile : +94716436216
>
> _______________________________________________
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
