![]() ![]() Functional sentences must be rigorous, unambiguous, and have the form of if-then rules and factual statements. They may also include pseudocode, for more rigor. The latter are sentences in a natural language (typically, in English) that distill the operational information contained in the original text. The outcome of this step would normally be a representation of the taxonomy of concepts to be used in the knowledge base (typically in the form of a UML diagram) and a body of functional sentences. We will have to make some modeling decisions and choices, and it is a good practice to document and justify whatever choices were made. ![]() One does not need to represent any sentences that do not contain such knowledge. The development will follow these main steps:ĭesign the knowledge representation informally, on paper or electronically, using functional sentences or pseudocode.įor each sentence appearing on the drivers handbook page, analyze it to identify the knowledge that is specific and can be operationally used by the driver of a vehicle. ![]() We will then test the representation using a set of sample questions prepared in advance. We will formally represent the content from one page in the Driver’s Handbook. An electronic version of the California Driver’s Handbook is available at. For this tutorial, we will reduce the task of answering questions to answering queries expressed in a formal language and posed against a relevant knowledge base. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |