The Mymory Project


Difference between version 7 and version 3:
At line 5 changed 1 line.
This page links to (open source) software developed in ''My''mory.
This page links to (open source) software (co-)developed in ''My''mory.
At line 7 added 21 lines.
!!! Kaukolu Wiki
The semantic wiki system [Kaukolu|] serves as the central document workspace of Mymory.
!!! User Observation Hub
The [UserObservationHub|] is a compact project and service catching several registered user observation notifications (e.g., from 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.
!!! Servicia
[Servicia|] is an infrastructure for building and running service-oriented systems with all vital properties with minimum burden for the developers. The framework focuses on an environment where
* different software components and services are developed by various people, usually not software engineers but researchers.
* the components should be easily assembled to prototypical software systems,
* multiple instances of such a system may run in parallel,
* the use of the file-system as storage backend is allowed,
* some of the components may run in separate address-spaces (on other virtual machines),
* services/components ideally use their functionality via method invocations when running in the same address space but the components should also be accessible via a standard web-protocols,
* non-java components (written, for example in javascript) should also be able to communicate with the services,
* developers should not be bothered with technical details of invoking other services, like generating stubs.
Overview presentation for Servicia: [PPS|]

Back to Software, or to the Page History.