Proposal for Text::Text_Bayes

Andreas Ahlenstorf (http://pear.php.net
/user/sunflyer) proposes Text::Text_Bayes.

You can find more detailed information here:
 http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Matthew Weier O'Phinney (http://pear.ph
p.net/user/weierophinney) has commented on the proposal
for Text::Text_Bayes.

Comment:

Could you put up a .phps to make viewing the source easier?
Thanks

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Markus Wolff (http://pear.php.net/u
ser/mw21st) has commented on the proposal for
Text::Text_Bayes.

Comment:

Hi,

nice idea, something like that is surely needed. One
suggestion though:
When learning stuff, the class only takes either HAM or SPAM
as the
classification parameter. If there was another, maybe
optional parameter
where you could also specify a kind of "pool",
or "domain" or whatever for
the current text, the user could classify several kinds of
texts. Like,
"this text has a 80% probability to fit in drawer A,
but also a 75%
probability to fit into drawer B...". Alternatively,
this could also be
passed as an option to the storage container, so that it
knows what pool
to insert the classification data into.

I hope this was at least half understandable 

CU
 Markus

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Philippe Jausions (http://pear.php.net
/user/jausions) has commented on the proposal for
Text::Text_Bayes.

Comment:

Is there any specific reason to not use MDB2 instead of PDO?

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Andreas Ahlenstorf (http://pear.php.net
/user/sunflyer) has commented on the proposal for
Text::Text_Bayes.

Comment:

Markus Wolff:

Sorry, I don't get it.

Do you like to have something like multi user capability? We
would be able
to maintain different spam/ham counts for each user instead
of having a
global spam/ham database for all users.

Or do you think about user-supplied spam probabilities? This
makes not
much sense because that's already what's the training
mechanism about.

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Christian Weiske (http://pear.php.net/
user/cweiske) has commented on the proposal for
Text::Text_Bayes.

Comment:

I think Markus wants to be able to define multiple
containers, not only
spam/ham.

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Philippe Jausions (http://pear.php.net
/user/jausions) has commented on the proposal for
Text::Text_Bayes.

Comment:

Also, check if Services_SpamCheck
http://pear.php.net/pepr/pepr-proposal-show.php?id=378
 and you package
could play nice together. Not necessarily as one package,
but at least try
to bring consistency to the API.

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Andreas Ahlenstorf (http://pear.php.net
/user/sunflyer) has commented on the proposal for
Text::Text_Bayes.

Comment:

Philippe Jausions:

We don't use MDB2 and I personally never used it too. But
we're heavily
using PDO (Reasons: sqlite3, prepared statement emulation
etc.). 

Adding a driver for MDB2, the native database extensions or
even Berkeley
DB wouldn't be a problem. That's what the interface is
for.

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Andreas Ahlenstorf (http://pear.php.net
/user/sunflyer) has commented on the proposal for
Text::Text_Bayes.

Comment:

Regarding the multiple containers (not only spam/ham):

I thought some time about it, but I couldn't find a real
use case for it.
Any suggestions?

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Markus Wolff (http://pear.php.net/u
ser/mw21st) has commented on the proposal for
Text::Text_Bayes.

Comment:

Andreas said:
> Sorry, I don't get it.
>
> Do you like to have something like multi user
capability?

...and Christian responded:
> I think Markus wants to be able to define multiple
containers, 
> not only spam/ham.

Almost. I just envision multiple containers in which to put
texts. Within
these containers, the choices boil down to spam and ham, for
this
particular container.

So the user does not just say "this is ham" or
"this is spam", but he
says: "this is ham for the container
'Advertisements'", "this is ham for
the container 'Personal Email'", or "this is
spam for the container 'Open
Source Projects'"... so you could basically build a
filter for incoming
emails (for example) that is solely based on classification.

It would eliminate the need to filter mail into fitting
folders by
specifying mail headers, you'd just classify mail and then
let the Bayes
filter do its work. The filtering is then done by content
assessment.

CU
 Markus

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=431

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php