Knowledge modeling: Difference between revisions

Revision as of 07:55, 13 July 2024

Latest revision as of 07:59, 13 July 2024

(4 intermediate revisions by the same user not shown)

Line 1:

{{unreferenced|date=March 2013}}

'''Knowledge modeling''' is a process of creating a computer interpretable model of knowledge or standard specifications about a kind of process and/or about a kind of facility or product. The resulting knowledge model can only be computer interpretable when it is expressed in some [[knowledge representation]] language or [[data structure]] that enables the knowledge to be interpreted by [[software]] and to be stored in a [[database]] or [[data exchange]] file.

[[Knowledge-based engineering]] or knowledge-aided design is a process of computer-aided usage of such knowledge models for the design of products, facilities or processes. The design of products or facilities then uses the knowledge model to guide the creation of the facility or product that need to be designed. In other words, it used knowledge about a kind of object to create a product model of an (imaginary) individual object.

Line 27:

==Explicitation of document content==

Knowledge modeling includes the explicitation of knowledge and requirements that is available in documents, such as design manuals, (international) standard specifications and standard data sheets.

In order to make such knowledge computer interpretable it needs to be expressed in a formal knowledge representation language and thus transformed into a computer interpretable form.

For example, in the form of an expressions Gellish English. This enables that the knowledge and requirements are related to the objects in the knowledge model, whereas the whole model is again stored in a Database.<br />The knowledge that is contained in documents can be modeled at various levels of explicitation.

The knowledge that is contained in documents can be modeled at various levels of explicitation. A low level of explicitation keeps large parts of the specifications in the form of natural language text. This means that the text is only human interpretable, but is nevertheless related to the objects in the knowledge model. Thus software can still present the information to users when knowledge about that object is requested. The other extreme is that the content of each sentence in a documents is converted in the formal knowledge representation language and thus the objects that are mentioned in those sentences become an integral part of the computer interpretable knowledge model. For example, the knowledge that the API 617 standard contains a standard specification for compressors can be linked to the concept compressor in the knowledge model of a compressor system. This can be expressed in a knowledge representation language (using the relation type {{angbr|is specified in}} as follows:

A low level of explicitation keeps large parts of the specifications in the form of natural language text. This means that the text is only human interpretable, but is nevertheless related to the objects in the knowledge model.

Thus software can still present the information to users when knowledge about that object is requested. The other extreme is that the content of each sentence in a documents is converted in the formal knowledge representation language and thus the objects that are mentioned in those sentences become an integral part of the computer interpretable knowledge model.

For example, the knowledge that the API 617 standard contains a standard specification for compressors can be linked to the concept compressor in the knowledge model of a compressor system.

This can be expressed in a knowledge representation language (using the relation type {{angbr|is specified in}} as follows:

* compressor {{angbr|is specified in}} API 617

A higher level of explicitation means that paragraphs or sentences in natural language are related to components in the knowledge model. A full explicit model means that the natural language sentences are completely transformed into data in a database structure.

For example, a specification of a minimum shaft diameter might be included in the knowledge model as follows:

* shaft diameter {{angbr|shall have on scale a value greater than}} 20 mm