Changes between Version 28 and Version 29 of Introduction


Ignore:
Timestamp:
08/04/05 19:45:23 (16 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Introduction

    v28 v29  
    44While E-Mail can be archived long-term server-side using the IMAP standard, there is no standard for archiving IM conversations. Chat logs are mostly stored locally on the client machine, using IM-client-specific file formats. This has several disadvantages: Storing the archive locally on the client computers is inconvenient when using more than one computer, archives are spread over different installations, are out of sync and get easily lost. Using proprietary, client- and protocol-specific formats to store the information makes it hard to manage and search the stored information using other interfaces than the client UI. 
    55 
    6 This project thesis addresses these issues by developing [http://nabu.opendfki.de/ Nabu], a system providing server-side logging of instant messages. 
    7 It tries to integrate instant messaging into the efforts made in the [http://www.ryerson.ca/~dgrimsha/courses/cps720_02/resources/Scientific%20American%20The%20Semantic%20Web.htm Semantic Web] community to store and retrieve information in a unified way. It uses the semantic web standard [http://www.w3.org/RDF/ RDF] to describe the stored information on the server. For retrieving the stored information, it  supports the [http://www.w3.org/TR/rdf-sparql-query/ SPARQL] query language, which is currently in an ongoing standardization process at the W3C. 
     6This project thesis addresses these issues by developing [http://nabu.opendfki.de/ Nabu], a system providing server-side logging of instant messages.  
     7 
     8Nabu tries to integrate instant messaging into the efforts made in the [http://www.ryerson.ca/~dgrimsha/courses/cps720_02/resources/Scientific%20American%20The%20Semantic%20Web.htm Semantic Web] community to store and retrieve information in a unified way. It uses the Semantic Web standard [http://www.w3.org/RDF/ RDF] to describe the stored information on the server. For retrieving the stored information, it  supports the [http://www.w3.org/TR/rdf-sparql-query/ SPARQL] query language, which is currently in an ongoing standardization process at the W3C. 
    89 
    910Besides the logging of chat messages, there are further requirements: 
     
    1718Related to Nabu, a [http://www.jabber.org/jeps/jep-0136.html storage format and protocol for server-side message archives] was proposed as Jabber protocol enhancement. The proposal suggests a simple protocol and storage format for message archiving. While being simple, it defines its own format and does not use existing standards. In my opinion using existing technology as RDF and SPARQL makes the our approach more powerful without having to reinvent the wheel. Also, Nabu can be more easily integrated with other information sources, and offers additional features as log sharing and adding custom metadata. 
    1819 
    19 The ''[http://haystack.lcs.mit.edu/overview1.html Haystack project]'' builds a client for information management  by integrating various information sources in one frontend, using an infrastructure based on RDF. A [http://www2003.org/cdrom/papers/poster/p231/p231-quan.htm messaging model was developed] to represent conversations from various communication channels, such as e-mail, news groups and instant messaging, in a unified way. 
     20The ''[http://haystack.lcs.mit.edu/overview1.html Haystack project]'' builds a client for information management  by integrating various information sources in one frontend, using an infrastructure based on RDF. A [http://www2003.org/cdrom/papers/poster/p231/p231-quan.htm messaging model was developed] to represent conversations from various communication channels, such as e-mail, news groups and instant messaging, in a unified way. In contrast to Nabu, Haystack is a client-based solution. 
    2021 
    2122The ''[http://kmi.open.ac.uk/projects/buddyspace/docs/jabberconf02-eisenstadt-dzbor.pdf BuddySpace]'' research project extends the presence concept in Jabber (simple offline/online/busy states) and adds information such as geographical location, current work focus etc. to the presence state. Furthermore it investigates how such additional semantics can be used to facilitate collaboration over networks. The [http://buddyspace.sf.net/ BuddySpace Jabber client] demonstrates the concepts.