Changes between Version 8 and Version 9 of UserObservationHub

Timestamp:

11/06/07 19:12:09 (17 years ago)

Author:

sauermann

Comment:

--

UserObservationHub

@@ -12 +12 @@
 The UserObservationHub - shortly: UOH (pronounced "uh-oh!" ;-))
 is a compact project and service catching several registered user observation notifications (e.g., from http://dragontalk.opendfki.de) and passes them on to interested listeners.
+For one user, one user observation hub is running on his or her desktop.
 There are multiple input sources that actually observe the user - these '''observers''' are implemented as plugins to applications or as listeners to operating system events. They connect to the User observation hub, or more precisely to '''collectors''' which are started together with the user observation hub. Each collector provides a different kind of interface, the differences can be both on communication layer (SOAP, REST, XML-RPC) or on the message layer. Some observers report messages to the collectors using serialized RDF conforming to the NOP ontology, others call methods of a collector and pass information as method arguments. Therefore, multiple collectors exist providing the needed interfaces. Each collector standardizes the input observations to RDF, which is then passed to the user observation hub.
 
@@ -49 +50 @@
 Before passing the RDF message to the listeners, a '''mapping of ontologies''' is done. 
 
-The NOP ontology focuses to describe the domain of native operations. '''Data Objects''' is not intended to be complete but to be minimal. We acknowledge that other endavours, such as [http://www.semanticdesktop.org/ontologies/nie/ NIE] (with its more detailled sub-ontologies NCO, NMO, ...) or the W3C ontologies for calendaring are more detailled description of such data objects. However, the NOP Data Objects provide a simple schema to be understood and interpretable by all listeners to a user observation hub, independent of detailled modelling. 
+The NOP ontology focuses to describe the domain of native operations. '''Data Objects''' is not intended to be complete but to be minimal. We acknowledge that other endavours, such as [http://www.semanticdesktop.org/ontologies/nie/ NIE] (with its more detailed sub-ontologies NCO, NMO, ...) or the W3C ontologies for calendaring are more detailed description of such data objects. However, the NOP Data Objects provide a simple schema to be understood and interpretable by all listeners to a user observation hub, independent of detailed modelling. 
 To realize a standardization of vocabulary, we require observers to describe and pass on observed user actions using NOP's native operation classes. However they are allowed to describe Data Objects either using UOH/NOP DataObjects or in their proprietary data format. 
 As output, the original input messages will be passed on, with data objects transformed to NOP's dataobject vocabulary if needed. So the UOH is liberal in what it accepts and conservative in what it passes on.