TL;DR: This thesis presents an integral solution to this problem in the form of the semantically rich standard Open Source Gellish English language, which can replace data models, and provides an extendable ontology with standard reference data for customization and harmonization of systems.
Abstract: Since long data storage and data communication lack a common standard universal data model as well as a common data language for the application domains of database users. This hampers data communication between systems and causes costly data conversion processes. Various solutions have been proposed. However, those solutions either have a limited scope and are mutually incompatible or are difficult to implement. This thesis presents an integral solution to this problem in the form of the semantically rich standard Open Source Gellish English language. Gellish enables electronic data storage and data exchange in a neutral and system independent way. Gellish is relatively easy to implement. Gellish English is the English variant of Gellish and is a structured subset of natural English. Variants for other languages are under development. Gellish enables automated translations between language variants. This means that Gellish English messages can be displayed in any other language variant. Gellish is an extension and integration of the concepts defined in various ISO and non-ISO standard data models and dictionary standards. The Gellish language can replace data models, and provides an extendable ontology with standard reference data for customization and harmonization of systems. A Gellish implementation typically uses the Gellish Table, which is a single table, based on an object-relation-object structure, that is sufficient to express any kind of factual information. The Gellish Dictionary / Taxonomy / Ontology can be used among others to harmonize the content of existing systems, such as data in Design systems, ERP systems and Procurement systems. It also enables the integration of data from different sources, such as data from various engineering and E-Business applications. For example, it enables to describe product catalogues in a system independent way or to describe product requirements, equipment designs, equipment performance, business processes and business transactions so that they can be exchanged between different systems from different parties without the need to convert or translate the data. Usage of Gellish is supported by an Open Source website on http://sourceforge.net/projects/gellish/.
TL;DR: The authors provide impressive statistical evidence that the relationship between age and Maximal Heart Rate is related to age and the likelihood of heart attack.
Abstract: Gellish and associates (3) are to be congratulated for their paper, "Longitudinal Modeling of the Relationship between Age and Maximal Heart Rate," published in this issue of Medicine & Science in Sports & Exercise®. The authors provide impressive statistical evidence that the
TL;DR: This case study argues for the usage of a machine-oriented controlled natural language as interface language to knowledge systems instead of using formal languages that are difficult to learn and to remember for non-specialists.
Abstract: In this case study I argue for the usage of a machine-oriented controlled natural language as interface language to knowledge systems. Instead of using formal languages that are difficult to learn and to remember for non-specialists, authors should be able to write specifications texts in a well-defined subset of English that can be unambiguously processed by a computer. This subset of computer-processable English (PENG) consists of a restricted grammar and lexicon and is used together with an intelligent text editor that guides the writing process. The editor of the PENG system communicates with a language processor that generates logical structures while the author writes a specification text. The language processor is connected via a server with reasoning services that allow for acceptability checking and question answering. Texts written in PENG look seemingly informal and are easy to write and understand for humans but have first-order equivalent properties.
TL;DR: It is illustrated that a single table database or data exchange file format, the Gellish table format, is sufficient to express a wide range of kinds of facts about classes as well as facts about individual objects so that it can replace data models.
Abstract: Data storage and data communication lack a common standard widely applicable data model as well as a common data language and knowledge base with a taxonomy of concepts and a grammar for data exchange messages. We present a solution to this problem in the form of the new "open" industry standard Gellish language and knowledge base, as a further development of the standard data model and ontology of two new ISO standards. We state that Gellish is a suitable language for neutral data exchange between systems. The definition of Gellish includes the public domain ("open data") Gellish knowledge base (STEPlib) with definitions of a large number of concepts and product models. This provides an ontology with standard reference data for customization of systems in a standardized way to be prepared for data harmonization, data integration and data exchange. It illustrates that a single table database or data exchange file format, the Gellish table format, is sufficient to express a wide range of kinds of facts about classes as well as facts about individual objects so that it can replace data models.
TL;DR: This paper sketches a possible route to overcome the problems of ambiguous use of the function notion in engineering by implementing functional descriptions in a formal language, viz.
Abstract: This paper sketches a possible route to overcome the problems of ambiguous use of the function notion in engineering. Our method is to implement functional descriptions in a formal language, viz. Gellish English, which is standardized structured English defined in STEPlib (based on ISO 10303221 (AP221) and ISO 15926). Our main results are twofold. First, we provide a formal taxonomy in Gellish English of three different and important senses of the term function: the SE-function featuring in systems engineering colloquially characterized as the “actions carried out to achieve the system’s objectives”; the KB-function, which is mainstream in knowledge base architectures as “being the performer of the activity,” and the C-function in philosophy as “the capacity of the performing object.” Second, we show how to prune philosophical accounts of functions down to manageable detail for practical engineering applications.