gellish_semantic_web
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
gellish_semantic_web [2011/10/20 23:17] peter [2. Exchange of Gellish Messages in a Network] |
gellish_semantic_web [2018/11/17 20:29] (current) andries |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== A Gellish Semantic Web ===== | + | ====== A Gellish Semantic Web ====== |
| + | |||
| ===== 1. A language for the Semantic Web ===== | ===== 1. A language for the Semantic Web ===== | ||
| - | A semantic web is a concept in which application software systems can exchange messages between each other whereas the messages can be interpreted by the receiving software so that the software can act in a correct way. Usually XML and other tools of the W3C consortium are mentioned as the semantic web technologies. However, without a 'common language' the exchanged messages cannot be correctly interpreted. Therefore, in addition to those tools there is a need for a complete language with an electronic natural language dictionary. However the XML, OWL, RDF, etc. tools only provide a mechanism to create a language, but they do not provide such a language themselves. Gellish English does provide such a language and thus can be used on top of XML and other tools. Furthermore, the Gellish Database definition provides an easy mechanism to exchange semantic rich messages between application systems. This enables to implement a semantic web, even without using the W3C tools. | + | |
| + | A real semantic web is a concept in which application software systems can exchange messages between each other whereas the messages can be interpreted by the receiving software, so that the software can act in a correct way. Usually XML and other tools of the W3C consortium are mentioned as the semantic web technologies. However, software is not able to interpret natural languages unambiguously. To enable the unambiguous interpretation of messages by computers the messages have to be expressed in a standardized 'formal language'. | ||
| + | |||
| + | |||
| + | Therefore, in addition to such tools there is a need for a kind of Formal English (or any other formalized natural language) that includes an electronic formalized natural language dictionary. 'Languages' such as XML, OWL, RDF, etc. only provide some high level concepts which enable to create languages, but they do not provide a kind of Formal English. Gellish Formal English does provide such a language and thus Gellish can be used to build a real Semantic Web, possibly on top of RDF/OWL or using other tools. Furthermore, the definition of Gellish Universal Databases and Data Exchange Messages document describe Gellish Data Tables as an easy mechanism to exchange semantic rich messages between application systems. This enables to implement a Semantic Web, even without using the W3C tools. | ||
| ===== 2. Exchange of Gellish Messages in a Network ===== | ===== 2. Exchange of Gellish Messages in a Network ===== | ||
| - | A Gellish Database can be read and updated directly via an Application Software system or via a web application. Such software may include a Gellish enabled Communication Engine. Such a Gellish Engine is software that can communicate with other Gellish Engines in a network to issue [[:Querying a Gellish English database|Gellish Queries]] and to provide Gellish Answers on such queries. Those queries and answers both are [[:Gellish messages|Gellish Messages]]. Each Gellish Message shall comply with an exchange protocol, such as for example the [[http://en.wikipedia.org/wiki/SOAP|SOAP protocol]] or the XINS protocol. A message in such a protocol contains a header and body. In a Gellish Message, the body consists of a [[:Gellish Databases|Gellish Database]] table. When such a standard protocol is used, then the Gellish Database tables are typically exchanged in XML form. | ||
| - | //**Continue with**// [[:Verification of designs]] | + | A Gellish Database can be read and updated directly via an Application Software system or via a web application. Such software may include a Gellish enabled Communication Engine. Such a Gellish Engine is software that can communicate with other Gellish Engines in a network to issue [[:querying_a_gellish_english_database|Gellish Queries]] and to provide Gellish Answers on such queries. Those queries and answers both are [[:gellish_messages|Gellish Messages]]. Each Gellish Message shall comply with an exchange protocol, such as for example the [[http://en.wikipedia.org/wiki/SOAP|SOAP protocol]] or the XINS protocol. A message in such a protocol contains a header and body. In a Gellish Message, the body consists of a [[:gellish_databases|Gellish Database]] table. When such a standard protocol is used, then the Gellish Database tables are typically exchanged in XML form. |
| + | |||
| + | |||
| + | //**Continue with** // [[:verification_of_designs|Verification of designs]] | ||
gellish_semantic_web.1319145438.txt.gz · Last modified: 2017/11/15 11:05 (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
