1.1 --- a/thesis/bib/thesis.bib	Mon Dec 15 19:18:27 2008 +0100
     1.2 +++ b/thesis/bib/thesis.bib	Tue Dec 16 14:09:23 2008 +0100
     1.3 @@ -103,8 +103,8 @@
     1.4  
     1.5  @incollection{lenke95,
     1.6  	author = "Nils Lenke and Peter Schmitz",
     1.7 -	title = "\emph{Geschwätz im `Globalen Dorf' -- Kommunication im Internet}",
     1.8 -	booktitle = "Osnabrücker Beiträge zur Sprachtheorie",
     1.9 +	title = "\emph{Geschwätz im `Globalen Dorf' -- Kommunikation im Internet}",
    1.10 +	booktitle = "Osnabrücker Beiträge zur Sprachtheorie: Neue Medien",
    1.11  	publisher = "Ulrich Schmitz",
    1.12  	volume = "50",
    1.13  	year = "1995",

     2.1 --- a/thesis/tex/2-MarketAnalysis.tex	Mon Dec 15 19:18:27 2008 +0100
     2.2 +++ b/thesis/tex/2-MarketAnalysis.tex	Tue Dec 16 14:09:23 2008 +0100
     2.3 @@ -110,7 +110,7 @@
     2.4  
     2.5  The easiest way of unified messaging is to base it on either email and convert all input sources to email messages (as attachments for instance) and store them in the user's mail box. Or use the telephone system as basis and convert text messages to speech. Both is no problem for asynchronous communication.
     2.6  
     2.7 -Finally a critical voice from Jesse Freund, who voted unified messaging on top of a hype list for \name{Wired.com}, ten years ago \cite{wired:hype}. His description of the technology ended with the humorous sentences: ``Unified messaging is a nice idea, but a tough sell: The reason you bought a cell phone, a pager, and a fax/modem is because each does its job well. No one wants to download voice mail as a series of RealAudio messages or sit through a voice mail bot spelling out email, complete with `semicolon dash end-parenthesis' for ;-).''
     2.8 +Finally a critical voice from Jesse \person{Freund}, who voted unified messaging on top of a hype list for \name{Wired.com}, ten years ago \cite{wired:hype}. His description of the technology ended with the humorous sentences: ``Unified messaging is a nice idea, but a tough sell: The reason you bought a cell phone, a pager, and a fax/modem is because each does its job well. No one wants to download voice mail as a series of RealAudio messages or sit through a voice mail bot spelling out email, complete with `semicolon dash end-parenthesis' for ;-).''
     2.9  
    2.10  
    2.11  %todo: have a result here?
    2.12 @@ -211,6 +211,10 @@
    2.13  
    2.14  Whether email will be the one surviving, or short message service, or another one, does not matter. Probably it will be \name{unified messaging}, which includes all of the other ones in it, anyway. \MTA{}s are a kind of software needed for all of these messaging methods---programs that transfer and receive messages.
    2.15  
    2.16 +\subsubsection*{Unified Communication}
    2.17 +Integration of asynchonous with synchronous communication channels is what Unified Communication is about. It seems not be possible to merge the two worlds on basis of email in an evolutionary way. As only a revolutionary change of the whole email concept would make it possible, it is best to ignore it. New designed technologies are usually superior to heavily patched and bent old technologies anyway. A general merge of synchronous and asynchronous communication has good chances to be fatal for email.
    2.18 +
    2.19 +Until Unified Communication will become reality---if ever---electronic mail has a good position, also as basis for Unified Messaging.
    2.20  
    2.21  
    2.22  

     3.1 --- a/thesis/tex/3-MailTransferAgents.tex	Mon Dec 15 19:18:27 2008 +0100
     3.2 +++ b/thesis/tex/3-MailTransferAgents.tex	Tue Dec 16 14:09:23 2008 +0100
     3.3 @@ -36,7 +36,7 @@
     3.4  \subsubsection*{Groupware}
     3.5  Normally the term ``groupware'' does not mean one single program, but a suite of programs. They build a framework which is then populated with various modules that provide actual functionality. Modules for mail transfer, file storage, calendars, resource management, instant messaging, etc., are commonly available.
     3.6  
     3.7 -One would use one of these program suites if the main work to do is not mail transfer, but providing integrated communication facilities and team working support for a group of people. The most common scenario are companies. They have \name{groupware} running to provide adequate services for their teams to work efficiently. But one may use \name{groupware} on the home server for his family members also.
     3.8 +These program suites are used if the main work to do is providing integrated communication facilities and team working support for a group of people. Mail transfer is only part of the problem to solve. The most common scenario are companies. They have \name{groupware} running to provide adequate services for their teams to work efficiently. But one may use \name{groupware} on the home server for his family members also.
     3.9  
    3.10  Examples are: \name{Lotus Notes}, \name{Microsoft Exchange}, \name{OpenGroupware.org} and \name{eGroupWare}.
    3.11