Gellish Wiki

User Tools

Site Tools

Trace: • gellish_semantic_web

Sidebar

Go to www.gellish.net

Table of content:

  1. Why Gellish
  2. Formalized languages
  3. Outline of Gellish
  4. How to start writing Gellish
  5. The Semantic Modeling Methodology
  6. The Taxonomic Dictionary
  7. Integrated Information Models, Building Information Models (BIM), etc.
  8. Product Modeling
  9. Modeling of activities and processes
  10. Document management
  11. Knowledge modeling
  12. Requirements modeling
  13. Product type modeling
  14. Verification of Gellish expressions
  15. How to write Gellish enabled software
  16. Example software - the Gellish Communicator
  17. Gellish Expression Format (the Gellish syntax)
  18. Universal databases
  19. Dictionary Extension (Proper definitions of concepts)
  20. Rules for names of concepts
  21. Gellish messages for data exchange
  22. Querying databases
  23. Gellish Semantic Web
  24. Verification of designs
  25. Automatic translation
  26. Change management
  27. Gellish Nederlands (in Dutch)

Note that each Wiki page has its own table of content about the details on that page.

gellish_semantic_web

Table of Contents

A Gellish Semantic Web

1. A language for the Semantic Web

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

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 Gellish Queries and to provide Gellish Answers on such queries. Those queries and answers both are Gellish Messages. Each Gellish Message shall comply with an exchange protocol, such as for example the 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 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

gellish_semantic_web.txt · Last modified: 2018/11/17 20:29 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
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki