On 8/23/06, James Ratcliff <[EMAIL PROTECTED]> wrote:
>
> This is one of the main concepts / problems of AI, is it not? Removing the ambiguity from our language in order to understand it. So you could remove it on the KR side, but you would still need to convert the regular language into the KR language, unless you would propose to have all inputs and outputs in the new KR language alone.
>
> So that conversion process would have to handle the context and ambiguity of the system still. And this is something we havnt accomplished to a high enough degree yet, but we have given it some attention, and realize that that alone is not enough.
>
> What kind of mapping would the KR need extra to handle the relationships between these newly seperated terms.
>
> James
>
> This is one of the main concepts / problems of AI, is it not? Removing the ambiguity from our language in order to understand it. So you could remove it on the KR side, but you would still need to convert the regular language into the KR language, unless you would propose to have all inputs and outputs in the new KR language alone.
>
> So that conversion process would have to handle the context and ambiguity of the system still. And this is something we havnt accomplished to a high enough degree yet, but we have given it some attention, and realize that that alone is not enough.
>
> What kind of mapping would the KR need extra to handle the relationships between these newly seperated terms.
>
> James
Yes, the problem of NL ambiguity doesn't go away, it merely shifted to the NL processing module. But I think the KR/NL separation is good because using a single representation language for both internal reasoning and NL _expression_ would be very confusing, if my intuition is right.
The "conversion" from NL to KR, or vice versa, is NOT a straightforward transliteration. It's dependent on contexts to resolve ambiguities. In addition, novel phrases like "mushroom pie" require internal processing within the NL module, before conversion could be made. (Suppose the NL module already contains a definition of "apple pie", so it knows how to convert that).
I am proposing an (almost) complete AGI architecture that can handle all these things. The only function not handled yet is planning and acting. I will post it here for discussion in a couple days =)
YKY
To unsubscribe, change your address, or temporarily deactivate your subscription, please go to http://v2.listbox.com/member/[EMAIL PROTECTED]
