UserObservationHub (UOH)

The UserObservationHub - shortly: UOH (pronounced "uh-oh!" ;-)) ist a *tiny* project and service catching several registered user observation evidences and notifications (e.g., from ​http://dragontalk.opendfki.de) and passes them on to interested listeners. So, there's multiple input sources to the UOH providing observed user operations and multiple output targets getting notified by the UOH -> these are "user observation listners".

Involved Persons:

• Sven Schwarz (DFKI GmbH, Kaiserslautern) -> for Projects Mymory and Nepomuk
• Leo Sauermann (DFKI GmbH) -> for Project Nepomuk
• Julien Gaugaz (L3S, Hannover) -> for Project Nepomuk
• Gianluca Demartini (L3S, Hannover) -> for Project Nepomuk

Check out the UOH from this SVN repository:

https://usercontext.opendfki.de/repos/trunk/UserObservationHub

NOP ontology (vocabulary)

The NOP ontology (nop.rdfs) is hosted at these two positions:

• ​http://ontologies.opendfki.de/repos/ontologies/userobs/nop.rdfs <-- the "real" one
• ​https://usercontext.opendfki.de/repos/trunk/UserObservationHub/src/de/dfki/km/usercontext/userobservationhub/vocabulary/nop.rdfs <-- a copy is used by the UserObservationHub
• NOTE: Those two MUST always be synchronized!

Goals:

• Important is, that the input to the UOH is in a language that can be understood by all listerners, i.e, they all should use the same schema for observed NOPS.
• On the other hand, information loss is not really acceptable, that is, down-translating to simple UOH language may remove interesting data.
• Idea: Translate to UOH schema while KEEPING the "native" (richer) data. That means: The incoming NOP contains for example a richer data object modeling. This will then be translated to the simpler UOH data object modeling BUT the original richer modeling still stays in the RDF an is also linked (via rdf:type) to data object the NOP is triggering.

Extending the UOH:

• You may add more subclasses to allow more NOPs or data objects. For example, add a SwitchOnLights NOP.
• You should inform the UserObservationHub team, such that, the new NOP can be included in the nops.rdfs and distributed to other researchers listening to UOH.