Frame (artificial intelligence): Difference between revisions

Revision as of 02:20, 12 July 2025

Latest revision as of 22:59, 31 July 2025

(2 intermediate revisions by 2 users not shown)

Line 6:

Frames are also an extensive part of [[knowledge representation and reasoning]] schemes. They were originally derived from [[semantic network]]s and are therefore part of structure-based [[Knowledge representation and reasoning|knowledge representations]].

According to [[Stuart J. Russell|Russell]] and [[Peter Norvig|Norvig]]'s ''[[Artificial Intelligence: A Modern Approach]]'', structural representations assemble "[...]facts about particular objectsobject and event types and [arrange] the types into a large [[taxonomy|taxonomic]] hierarchy analogous to a [[biological taxonomy]]".

== Frame structure ==

{{Unreferenced section|date=July 2025}}

The frame contains information on how to use the frame, what to expect next, and what to do when these expectations are not met.

Line 30 ⟶ 31:

== Features and advantages ==

{{Unreferenced section|date=July 2025}}

A frame's terminals are already filled with default values, which is based on how the [[Mind|human mind]] works.

Line 44 ⟶ 45:

== Example ==

{{Unreferenced section|date=July 2025}}

Worth noticing here is the easy analogical reasoning (comparison) that can be done between a boy and a monkey just by having similarly named slots.

Line 157 ⟶ 158:

===Comparison of frames and objects===

Frame languages have a significant overlap with [[Object-oriented programming|object-oriented]] languages. The terminologies and goals of the two communities were different but as they moved from the academic world and labs to the commercial world developers tended to not care about philosophical issues and focused primarily on specific capabilities, taking the best from either camp regardless of where the idea began. What both paradigms have in common is a desire to reduce the distance between concepts in the real world and their implementation in software. As such both [[paradigm]]s arrived at the idea of representing the primary software objects in [[Taxonomy|taxonomies]] starting with very general types and progressing to more specific types.

The following table illustrates the [[correlation]] between standard terminology from the object-oriented and frame language communities: