knowledge_modeling_in_gellish
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
knowledge_modeling_in_gellish [2018/11/02 21:06] andries [2. What is a knowledge model] |
knowledge_modeling_in_gellish [2018/11/02 21:23] andries [3.5 Options for subtypes of components] |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| The result of a knowledge modeling activity is 'modeled knowledge'. When such modeled knowledge is a coherent computer interpretable collection of expressions about a particular kind of thing we can call the collection a **knowledge model**. Knowledge is expressed as | The result of a knowledge modeling activity is 'modeled knowledge'. When such modeled knowledge is a coherent computer interpretable collection of expressions about a particular kind of thing we can call the collection a **knowledge model**. Knowledge is expressed as | ||
| relations between **kinds** of things (concepts) that specify //possibilities// (what **can be** the case) for things of a particular **kind**. For example, knowledge may be specified about the possible kinds of components of a kind of thing and its possible kinds of properties and the possible kinds of properties of the kinds of components. The knowledge may also include options for values within the constraints of the definition of the kind of thing. This means that a knowledge model is a specification in the form of formal expressions and not so much as textual descriptions (in a natural language). However, it is possible to express knowledge by relating objects to pieces of text that are included as 'information objects' in a knowledge model and it is also possible to relate an object to a document (as is described in the section about [[document_management|document modeling]]. \\ | relations between **kinds** of things (concepts) that specify //possibilities// (what **can be** the case) for things of a particular **kind**. For example, knowledge may be specified about the possible kinds of components of a kind of thing and its possible kinds of properties and the possible kinds of properties of the kinds of components. The knowledge may also include options for values within the constraints of the definition of the kind of thing. This means that a knowledge model is a specification in the form of formal expressions and not so much as textual descriptions (in a natural language). However, it is possible to express knowledge by relating objects to pieces of text that are included as 'information objects' in a knowledge model and it is also possible to relate an object to a document (as is described in the section about [[document_management|document modeling]]. \\ | ||
| - | Thus knowledge models are supposed to express possibilities about kinds of things, whereas product and process models express thates of affairs about individual things. The latter models are thus mainly composed of relations between individual things. The relations between individual things express different meanings from relations between kinds of things in knowledge models. \\ | + | Thus knowledge models are supposed to express possibilities about kinds of things, whereas product and process models express states of affairs about individual things. The latter models are thus mainly composed of relations between individual things. The relations between individual things express different meanings from relations between kinds of things in knowledge models. \\ |
| An example of knowledge is the expression that a pipe generally has an internal diameter. Such knowledge can be expressed in Gellish by specifying a relation between the concepts 'pipe' and 'internal diameter', using the kind of relation '//can have as aspect a//', so that the expression becomes: \\ | An example of knowledge is the expression that a pipe generally has an internal diameter. Such knowledge can be expressed in Gellish by specifying a relation between the concepts 'pipe' and 'internal diameter', using the kind of relation '//can have as aspect a//', so that the expression becomes: \\ | ||
| ^Name of left hand object^Name of kind of relation^Name of right hand object^ | ^Name of left hand object^Name of kind of relation^Name of right hand object^ | ||
| Line 76: | Line 76: | ||
| ==== 3.5 Options for subtypes of components ==== | ==== 3.5 Options for subtypes of components ==== | ||
| - | A knowledge model or a general specifications model usually will allow flexibility to select various types of components from a list of possible subtypes. For example, the Gellish English Dictionary specifies that there are many types of bearing, such as radial bearing, axial bearing, roller bearing, ball bearing, etc. Each of those subtypes may have different components and different characteristics. | + | As the Gellish Dictionary is a taxonomy that specifies known subtypes of kinds of things, a specification of a possible kind of component implies that such a component might be more precisely classified as a subtype of the specified kind of component. Thus a knowledge model usually allows for flexibility for selecting any kinds of component from a list of possible subtypes of the specified kind of component. For example, the Gellish Dictionary specifies that there are many kinds of bearings, such as radial bearing, axial bearing, roller bearing, ball bearing, etc. Knowledge about each of those subtypes may specify that have different kinds of components and different characteristics. It may even be that manufacturer's models from their catalogues are included in (an extension of) the dictionary as further subtypes, whereas knowledge about those subtypes are specified as well. This is further discussed in the section about product types. |
| ====== 4. Using knowledge for creating individual things ====== | ====== 4. Using knowledge for creating individual things ====== | ||
| - | Note that the expression of knowledge (and requirements and definitions) about kinds of things uses different kinds of relations than the corresponding expression of information about individual things, although they can all be integrated into one integrated semantic network. For example, the above kind of relation 'can have as aspect a' corresponds in information about individual things to the kind of relation 'has as aspect'. The expressions of knowledge can be used by software to guide the specification of individual things. To enable such an application, Gellish contains relations between the two kinds of relations, as is further described in [[Requirements_Models|requirements modeling]]. The following is an example of an expression of an idea about a particular individual pipe P-1 that has an internal diameter of 30 inch. The expressions can be derived from and correspond to the above information about the kind 'pipe'. | + | Note that the expression of knowledge (and requirements and definitions) about kinds of things uses different kinds of relations than the corresponding expression of information about individual things, although they can all be integrated into one integrated semantic network. For example, the above kind of relation 'can have as aspect a' corresponds in information about individual things to the kind of relation 'has as aspect'. The expressions of knowledge can be used by software to guide the specification of individual things. To enable such an application, Gellish contains relations between the two kinds of relations, as is further described in [[Requirements_Models|requirements modeling]]. The following is an example of an expression of an idea about a particular individual pipe P-1 that has a nominal diameter of 30 inch. The expressions can be derived from and correspond to the above information about the kind 'pipe'. |
| ^Name of left hand object^Name of kind of relation^Name of right hand object^Name of unit of measure^ | ^Name of left hand object^Name of kind of relation^Name of right hand object^Name of unit of measure^ | ||
| | P-1| is classified as a | pipe | | | | P-1| is classified as a | pipe | | | ||
| | P-1| has as aspect | D-1| | | | P-1| has as aspect | D-1| | | ||
| - | | D-1| is classified as a| internal diameter| | | + | | D-1| is classified as a| nominal diameter| | |
| | D-1| is quantified on scale as equal to| 30|inch | | | D-1| is quantified on scale as equal to| 30|inch | | ||
| - | The first classification relation expresses the P-1 is a pipe and thus the knowledge about the concept 'pipe' (and its supertypes!) is applicable to P-1. Thus software can suggest that P-1 might have an internal diameter and may generate a proposal for the other three expressions. | + | The first classification relation expresses the P-1 is a pipe and thus the knowledge about the concept 'pipe' (and its supertypes!) is applicable to P-1. Thus software can suggest that P-1 might have an nominal diameter and may generate a proposal its possible values and for the other three expressions. |
| **//Continue with//** [[Requirements Models]] | **//Continue with//** [[Requirements Models]] | ||
knowledge_modeling_in_gellish.txt ยท Last modified: 2018/11/02 21:25 by andries
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
