Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I haven't seen any statement of purpose yet (or in XP jargon "Users stories").

Are you expecting the knowledge engineer (the person writing a rules base) to be a programmer ? A Perl programmer ?

What degree of complexitiy of (real-world) problem do you expect to be able to solve ?

For a user, a table isn't a complex concept, but inputing it might be unless the system is designed to cope at the beginning. Writing a rule such as (in my pseudo code) :

[ID in (A B C)] => [D = rows from TABLE_D where KEY=ID]

could be difficult otherwise.

Re. The rule efficiency, you are right, this is the hard part.
To some extent the responsibility lies with the knowledge engineer (read ruleset creator), since you can write bad (==slow) programs/algorithms in any language.

Giving the engineer tools (such as the priority / weighting mechanism you mention can help, as can other options such as choice of search mechanism and direction.

In my experience, a lot of knowledge engineer time is spent tuning the knowledge base, and the system should be proactive in helping that process, providing timing / coverage analysis.

In reply to Re: Re: Re: Re: Rules-based Perl? by Brovnik
in thread Rules-based Perl? by Masem

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others musing on the Monastery: (9)
    As of 2018-12-12 06:27 GMT
    Find Nodes?
      Voting Booth?
      How many stories does it take before you've heard them all?

      Results (57 votes). Check out past polls.

      • (Sep 10, 2018 at 22:53 UTC) Welcome new users!