Questionnaire!
dangyogi
I would like to ask everybody to quickly fill out this questionnaire
(just 12 quick questions) and either post your answers or, if you are
shy, email them to me so that I can get a feel for how PyKE is being
used.
Thanks in advance!
-bruce
1. What are you currently using PyKE for (please include whether as a
hobby, within another open source project, within a commercial
project, or ??)?
2. Do you use forward-chaining?
3. Do you use backward-chaining?
4. Do you use PyKE's "plans" (automatic programming)?
5. Do you use question bases?
6. How would you rate the documentation?
7. How would you rate the examples?
8. Have you tried to extend one of the examples? If so, which one
(s)?
9. What do you like about PyKE?
10. What do you not like about PyKE?
11. How would you rate PyKE overall (-3 to 3)?
12. Are there any features that would make using PyKE a lot easier
for you?
Alexander Berezhnoy
>
> Hi Everybody,
>
> I would like to ask everybody to quickly fill out this questionnaire
> (just 12 quick questions) and either post your answers or, if you are
> shy, email them to me so that I can get a feel for how PyKE is being
> used.
>
> Thanks in advance!
>
> -bruce
>
> 1. What are you currently using PyKE for (please include whether as a
> hobby, within another open source project, within a commercial
> project, or ??)?
>
For now, as a hobby (related to my job in the area of the security analysis)
> 2. Do you use forward-chaining?
Yes.
> 3. Do you use backward-chaining?
Yes.
> 4. Do you use PyKE's "plans" (automatic programming)?
No.
> 5. Do you use question bases?
Yes.
> 6. How would you rate the documentation?
All necessary information is available, but structure is a bit strange.
>
> 7. How would you rate the examples?
Good.
>
> 8. Have you tried to extend one of the examples? If so, which one
> (s)?
No.
>
> 9. What do you like about PyKE?
Python
Lightweight
Both backward and forward-chainings are supported
>
> 10. What do you not like about PyKE?
Error messages are not very informative (
Compilation destination is not configurable
Sometimes it's a bit verbose if compare it with Prolog =)
>
> 11. How would you rate PyKE overall (-3 to 3)?
1 (but with a big potential)
>
> 12. Are there any features that would make using PyKE a lot easier
> for you?
Better cross-rulebase communication, like ability to match some
predicate from the other rulebase without knowing that rulebase name
in the compile-time.
Rulebase dependency management (import statements in the rulebases
without need to activate rulebases they depend on)
Ability to run an application just from the command-line, like:
pyke --activate=rb1,rb2,rb3 --proove rb3.predicate(1,2,3)
or a command-line interfaces like in Prolog.
Proof explanation (the API to trace how the predicate has been matched etc).
vim-plugin =)
--
Alexander (Sasha) Berezhnoy
http://sandals-on-my-head.blogspot.com
Jerry Spicklemire
1. What are you currently using PyKE for (please include whether as a
hobby, within another open source project, within a commercial
project, or ??)?
Not yet using PyKe, but considering it for an
upcoming (Q1, 2009) project
4. Do you use PyKE's "plans" (automatic programming)?
This is one very BIG reason PyKE is being considered.
5. Do you use question bases?
This is another.
6.7. How would you rate the documentation? examples?
OK
9. What do you like about PyKE?
It isn't Prolog.
10. What do you not like about PyKE?
It's too much like Prolog.
11. How would you rate PyKE overall (-3 to 3)?
1
12. Are there any features that would make using PyKE a lot easier
for you?
A WSGI based, user friendly TTW interface for initiating,
and populating an ontology, so that PyKe could easily be
used within Python Web Frameworks, or anti-frameworks.
This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. Verio, Inc. makes no warranty that this email is error or virus free. Thank you.