gellish
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
gellish [2011/10/28 00:24] andries |
gellish [2016/01/26 21:19] andries |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Gellish Modeling Method ====== | + | ====== Gellish Modeling Methodology ====== |
| - | The Gellish Modeling Method is a method that covers the following five area's: | + | The Gellish Modeling Methodology covers the following five area's: |
| Line 8: | Line 8: | ||
| - | The creation of a [[:gellish_domain_dictionary|Smart Dictionary-Taxonomy]] implies the creation of [wiki:"Definition Models"] for concepts in a particular application domain in some natural language. \\ The method includes the creation of Definition Models in which facts about the defined concepts that are by definition true are explicitly modeled such that the expressions are computer interpretable. Each Definition Model includes at least a subtype-supertype relation and a specification of at least one aspect that distinguishes a subtype concept from its supertype concept and from its neighboring concept(s). This ensures that the concepts in the Dictionary are arranged in a Taxonomy structure. A Definition Model also includes the specification of one or more names, synonyms, abbreviations, symbols, etc. to denote the concept in one or more languages and contexts (language communities). Furthermore the Dictionary includes the definition of kinds of aspects and aspect values that are used to define concepts. The relation types that are used to specify relations between concepts are themselves also defined in the dictionary. A collection of Definition Models thus forms a semantic network of concepts, which make it a computer interpretable Smart Dictionary / Taxonomy that is an extension of the general purpose Gellish Smart Dictionary. Guidelines for the creation of Definition Models can be found in the document 'Guide for the extension of the Gellish Dictionary' in the download area of this website. | + | The creation of a [[gellish_domain_dictionary|Smart Dictionary-Taxonomy]] implies the creation of [[proper_definition_of_a_concept|Definition Models]] for concepts in a particular application domain in some natural language. \\ The method includes the creation of Definition Models in which facts about the defined concepts that are by definition true are explicitly modeled such that the expressions are computer interpretable. Each Definition Model includes at least a subtype-supertype relation and a specification of at least one aspect that distinguishes a subtype concept from its supertype concept and from its neighboring concept(s). This ensures that the concepts in the Dictionary are arranged in a Taxonomy structure. A Definition Model also includes the specification of one or more names, synonyms, abbreviations, symbols, etc. to denote the concept in one or more languages and contexts (language communities). Furthermore the Dictionary includes the definition of kinds of aspects and aspect values that are used to define concepts. The relation types that are used to specify relations between concepts are themselves also defined in the dictionary. A collection of Definition Models thus forms a semantic network of concepts, which make it a computer interpretable Smart Dictionary / Taxonomy that is an extension of the general purpose Gellish Smart Dictionary. Guidelines for the creation of Definition Models can be found in the document 'Guide for the extension of the Gellish Dictionary' in the download area of this website. |
| Line 17: | Line 17: | ||
| - | ===== 3. Creation and use of Standard Specification Models and [wiki:"Requirements Models"] ===== | + | ===== 3. Creation and use of Standard Specification Models and Requirements Models ===== |
| Line 26: | Line 26: | ||
| - | 'Standard requirements' are requirements about kinds of things. For example, requirements for data and documents about facilities that have to be delivered by contractors, manufacturers and suppliers that realize capital projects. Such requirements are usually applicable in a particular company or project context in which they are declared to be applicable. They may include requirements for data and documents about products, procedures and applications. Such requirements are expressed for example in best practices guides of companies, but also in national and international standards as well as in governmental rules. Usually such requirements are expressed in textual documents. This part of the Gellish Modeling Method provides guidance for the creation of requirements models that are computer interpretable and that can be used for computer-aided support for the verification whether a deliverable (such as a design or a fabricated product) satisfies those requirements. [[:br|br]] Standard Specification Models as well as Requirements Models that are expressed in Gellish use the concepts that are defined in a Gellish Dictionary. | + | '[[requirements_models|Standard requirements]]' are requirements about kinds of things. For example, requirements for data and documents about facilities that have to be delivered by contractors, manufacturers and suppliers that realize capital projects. Such requirements are usually applicable in a particular company or project context in which they are declared to be applicable. They may include requirements for data and documents about products, procedures and applications. Such requirements are expressed for example in best practices guides of companies, but also in national and international standards as well as in governmental rules. Usually such requirements are expressed in textual documents. This part of the Gellish Modeling Method provides guidance for the creation of requirements models that are computer interpretable and that can be used for computer-aided support for the verification whether a deliverable (such as a design or a fabricated product) satisfies those requirements. [[:br|br]] Standard Specification Models as well as Requirements Models that are expressed in Gellish use the concepts that are defined in a Gellish Dictionary. |
| - | ===== 4. The creation of [wiki:"Facility Information Models"] ===== | + | ===== 4. The creation of Facility Information Models ===== |
| - | Facility Information Models are models with information about individual objects. This may be data and documents about imaginary objects, such as designs of objects, it may also be data and documents about realized facilities and their operation and/or maintenance. This part of the Gellish Modeling Method provides guidance on how to create such a Facility Information Model in a neutral computer interpretable form as a Gellish Database. This means that there is no need to specify a database structure for such a model. The resulting Facility Information Model will usually include at least four sections: %%\%%%%\%% 1. A model of the facility and its components and processes, such as a building, a ship, a process plant, a railway, a car, etc. %%\%%%%\%% 2. A document and data sets repository with the data sets and documents about those components with relations to the components, so that the facility model can be used to search for the data and the documents about them. %%\%%%%\%% 3. A Smart Dictionary part, because the individual components, their properties and documents will be classified by standard concepts (classes) as defined the Gellish Dictionary or a Domain Dictionary. As a consequence the Facility Information Model is expressed in a consistent common language that enables to integrate data from various sources, and it also enable very powerful searching, especially by making use of the knowledge that is contained in the Gellish taxonomy. %%\%%%%\%% 4. A collection of Requirements Models that expresses the requirements for the first and second section (the facility model and the documents and data set) so that they can be verified on completion and other information quality aspects. | + | [[facility_information_models|Facility Information Models]] are models with information about individual objects. This may be data and documents about imaginary objects, such as designs of objects, it may also be data and documents about realized facilities and their operation and/or maintenance. This part of the Gellish Modeling Method provides guidance on how to create such a Facility Information Model in a neutral computer interpretable form as a Gellish Database. This means that there is no need to specify a database structure for such a model. The resulting Facility Information Model will usually include at least four sections: |
| + | - A model of the facility and its components and processes, such as a building, a ship, a process plant, a railway, a car, etc. | ||
| + | - A document and data sets repository with the data sets and documents about those components with relations to the components, so that the facility model can be used to search for the data and the documents about them. | ||
| + | - A Smart Dictionary part, because the individual components, their properties and documents will be classified by standard concepts (classes) as defined the Gellish Dictionary or a Domain Dictionary. As a consequence the Facility Information Model is expressed in a consistent common language that enables to integrate data from various sources, and it also enable very powerful searching, especially by making use of the knowledge that is contained in the Gellish taxonomy. | ||
| + | - A collection of Requirements Models that expresses the requirements for the first and second section (the facility model and the documents and data set) so that they can be verified on completion and other information quality aspects. | ||
| ===== 5. Creation and interpretation of messages between systems ===== | ===== 5. Creation and interpretation of messages between systems ===== | ||
| - | The part of the Gellish Modeling Method describes how to create [wiki:"Gellish messages" messages] for the exchange fo data between systems. This includes messages that express [wiki:"Querying a Gellish English database" queries] to people or to query central or distributed databases, messages that contain responses with answers and messages with statements. The method describes how software should create and interpret (parse) such messages that are exchanged between Gellish enabled software. In other words, it describes messages for system independent communication via Internet through a [wiki:"Gellish Semantic Web"]. [[:http:iresearchpapers.com_order.php|http://iresearchpapers.com/order.php]] order term papers] 'Continue with '[wiki:"Gellish English Dictionary"] | + | The part of the Gellish Modeling Method describes how to create [[gellish_messages|messages]] for the exchange of data between systems. This includes messages that express [[querying_a_gellish_english_database|queries]] to people or to query central or distributed databases, messages that contain responses with answers and messages with statements. The method describes how software should create and interpret (parse) such messages that are exchanged between Gellish enabled software. In other words, it describes messages for system independent communication via Internet through a [[gellish_semantic_web|Gellish Semantic Web]]. |
| + | |||
| + | **Continue with** [[gellish_english_dictionary|Gellish English Dictionary]]\\ | ||
| + | **Return to** [[start|Overall Table of Content]] | ||
gellish.txt · Last modified: 2017/11/15 11:15 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
