The LOGOS System has been designed as a Natural Language Learning, Training, Teaching, and Translation System.
By Design, LOGOS behaves like a 3-year old child.
It listens, listens, and listens ...
And, suddenly, starts to ask questions.
Typical questions, after the initial "Listening Phase", are:
What is your name? (english) Wie heißt Du? (deutsch)
Within the LOGOS System, all sentences, questions, claims, phrases, and terms are uniquely enumerated.
These enumerations are done in a
When in the *Learning* stage, LOGOS simply records sentences. It thus keeps track, by *listening*, of the phrases used:
The primary purpose in this *Learnig* mode of LOGOS is:
It does collect all of your used words, terms, phrases, and sentences in a *personal* Language EXAMPLE File.
It then goes ahead, matching your *personal* Language EXAMPLE file against the already existing *generalized* Language Definition Files.
Those Language Definition Files are *loaded on demand* into memory, as soon as
As already said, LOGOS behaves like a 3 year old child.... :-)
After having *learned* *your personal* language (most probably your
Then, comparing the used letters (and some already predefined ALPHABETS, LOGOS
is already aware of), it does TRY to decide which is your
When LOGOS cannot make a unique decision, it will ask you:
What Language are your speaking?
Otherwise, it will ask you:
Are you speaking < mother-tongue>?
This process will repeat until LOGOS does know which language is
Concurrently, this conversation, your words, terms, and phrases *are stored*
in the LOGOS lexica for further usage for other individuals having the
The Training Mode of LOGOS requires a person having a
In the *training mode*, LOGOS does ask questions (in english), like:
Then, when LOGOS does know nothing of your language, it will ask:
... It will record *your answer*, again.
It then will switch into the 'dual language mode', consisting of your
Natural Language Administrators (NLA's, see below),
and stating something like:
*Book* heißt auf deutsch *Buch*!
Welches *Buch* hast Du zuletzt gelesen?
Wer ist der Autor?
It again stores the answers, and then for instance, asks you:
Wie hat Dir
Kennst Du andere *Bücher* von *Richards Dawkins*?
When you answer with a question mark (?), the question is translated
In the TEACHING mode, it might be, that a *translation* is not yet available. LOGOS will then ask:
Was heißt *Buch* auf *englisch*?
You answer 'Book', and this translation if stored in the English Lexicon. Note that all words, terms, and phrases become *uniquely* enumerated in the LOGOS System, this enumeration is language independent.
The basic (German) Lexicon has been built by *samples*, and the enumeration has been based in decreasing frequency of occurences and importance in *ordinary conversations*.
As a base, some Face-Book messages of Thomas.Schneider. Wien, some e-mails from/to firstname.lastname@example.org, and some german and english home-pages on the Web have been used.
The only difference between the TEACHING Mode and the TRAINING mode is, that the Lexica are updated in the TRAINING mode, whereas in the TEACHING mode the *unknown* words, terms, and phrases are collected and an e-mail is generated to the proper Natural Language administrator for proper translation. After the Natural Language Administrator has updated the proper Lexicon, the new Lexicon is automatically distributed again to all LOGOS subscribers of this particular language.
Whilst LOGOS TEACH and LOGOS TRAIN are interactive, LOGOS TRANSLATE will
attempt to translate a
The implementation of the TRANSLATE funcionality is based on so called *terms* and *phrases*. A term is a word with certain properties. For instance, LOGOS does know that *Bücher* is the plural of *Buch*, in german, and *Buch* and *Buecher* are nouns.
The final LOGOS reference manual will include a complete list of all those properties and their potential values. The latin definition (mostly used in ordinary lexicons) will be used for this instances.
One of the primary goals of LOGOS will be to translate phone-calls on the fly. Usually, Phone calls do use a very restricted set of words (as most FaceBook messages do as well).
For instance, reading some 100 Facebook sentences gives only approximately 100 different words used! As the already existing example files show, 1000 Facebook sentences consist of approx 800 different words - independent of the language used!
The so called Speach Recognition Software will NOT be developed from scratch. The already existing speach Spech Recognition Software *simon-listens* will be used. *simon-listens* has been developed by Peter Grasch, a young Austrian, at the University of Graz. You may find details of *simon-listens* at www.simon-listens.org.
For speach output, an existing piece of Software will be used: TTS Service Extended, which is already available for ANDROID Handies.
For both packages, a co-operation will be signed between the LOGOS System Development Company, and the proper parties.
The market potential, especially for Phone Call translations, are enormous.
Google for instance, sells 60.000 copies of ANDROID Licences daily!
Our goal is to obtain 5% market share within the next two years.
In Europe the costs of a licence thru the ANDROID market will be € 20 one time for 5 languages of your own language (for the basic lexicon of 1,000 words and/or phrases) per language.
American, Japanese and other rich countries will have to pay US $ 20 for the same licence.
Developing countries (Africa, Asia, South America, etc. …) will obtain a reduced licence fee between for US $ 2 – 3 per mobile phone (for a 5 language pack of free choice).
The intent of the complete marketing strategy to enable all people on the planet Earth the ability to learn and communicate in the other languages used on this planet Earth.
The further potential of this software will be to translate multiple conference calls to multiple members of multiple countries in multiple languages to translate instantly and simultaneously.
This will enable universal communication between various languages instantly.
A further, more detailed, market potential analysis will be done by Klaus Hofmann, which is the Business Development Manager here in Vienna, Austria.
As already mentioned, a Natural Language Administrator will be assigned for each language. The role of this Language Administrator will be to translate the Master Dictionaries (Lexica) into his mother tongue. Most of these NLA's will be located here, in Vienna, Austria. Reason for this, is that we have enormous amount of external students here in Vienna, and a wide variety of different languages which can be supported by this approach. This will also ease the communication between the project team and the Software Author.
Currently, the following Language Administrators have been already assigned:
|Name||Language||Thomas Schneider||Deutsch||Thomas Schneider+NN||English||Joerg Bleichert||US English||NN||Italian||Sziszi Peter||Hungarian||Zuzanna Margalowa||Slovakian||Justyna Jurczik||Polish||Nina (Retsina)||Bulgarian||Josef (Retsina)||Greek||Ali (Retsina)||Turkish||Lirim||Albanian||Jiang||Chinese||Verena Metz||French||Daniel Andres Garzotto||Spain||Gonnie Steven Bras||Dutch||Gonnie Steven Bras||Afrikaans||Gabriele N.||Serbian||Eva Fuehrer||Danish||Gabi (Orange)||Serbian||Petra Popovic||Croatian|
This list will be expanded, when these Languages have been implemented in the Alpha version of the project, or on demand, when special need arises.
Each Language Administrator will get an A1 NetBook with built-in wide-band Internet.
The current costs for this Net-Book are 29 €/month. Each Language administrator will also get a unique e-mail account at the local Nessus Internet Provider (see www.nessus.at). A NLA-group will be installed to ease communication between the Software Authors, to distribute new Software Versions, and new versions of the lexica as well.
The Project Development Team consists of a number of old/new friends of Thomas Schneider, mostly located here in Vienna, Austria, Europe, to ease project communication within the Team.
Nevertheless, it deliberately does also consist of members having originally *not* *GERMAN* as the mother tongue (native language), to early be able to prove the concepts of LOGOS before releases.
This also enables the primary Software author, Thomas Schneider, to test the development version of the LOGOS System with various languages before release.
The currently assigned ROLES and the currently assigned RESPONSIBLE PERSON (manager, when you like) are listed below:
|Role||Responsible Person (manager)||Primary Software Author, CTO, CEO||Thomas Schneider|
|Project Leader||Dr. Johannes Penzias||Project Administration||Eva Führer||Public Relations||Justyna Jurczyk||Business Development||Klaus Hofmann||Investor Relationships||Gregor Urban||USA Capitol Raising||Joerg Bleichert|
|Screen Design & Implementation||Johann Widerlechner||Users Guide and Help System||Helmut Hainzl|
|Primary Linguistic Consultant||Verena Metz||Venture Capital Raisement||Stan Koci|
Klaus Hofmann, the Business Development Manager, will be in charge to contact and collect from the necessary investors. Concurrently, Red Bull Mobile here in Austria will be contacted in regard to, if they are interested, to act as the primary Investor and marketing agent.
As Red Bull Mobile has already introduced a very clever HUAWAI Handy, with a touch screen using the ANDROID Software, this co-operation might be very fruitful for both parties.
A detailed Business Plan will be developed by Klaus Hofmann and his Business Partner Gary N., within the next 3 months.
The LOGOS Software will be implemented in the following phases:
|Phase 1:||LEARN Function||80% already implemented, release 1. July 2010|
|Phase 2:||TRAIN Function||release 1. October 2010|
|Phase 3:||TEACH Function||release 1. December 2010|
|Phase 4:||simple TRANSLATE Function||alpha release 1. March 2011|
|Phase 5:||simon-listens interface||alpha release 1. March 2011|
|TTS interface||alpha release 1. March 2011|
|Phase 6:||phone call translation||beta release 1. December 2011|
The alpha-release will support ANDROID Handys. Maybe, later iPhone support will be investigated.
The Beta-Phase should be scheduled to last 6 months, to gain experience of the market potential as well, as feed-back of the usability and possible/needed improvements before commercial release.