Difference between revisions of "Domoverse platform"
From Tmplab
m (→Resources) |
m (→Project organization) |
||
| Line 13: | Line 13: | ||
# Implementation of XMLRPC-like server for services exposition (X10, ...) | # Implementation of XMLRPC-like server for services exposition (X10, ...) | ||
# Linking virtual objects' actions to XMLRPC calls | # Linking virtual objects' actions to XMLRPC calls | ||
| − | # Gluing all together | + | # Gluing all together for first prototype |
| + | # Hardware integration on low-consumption devices (WRT?) | ||
= Components = | = Components = | ||
Revision as of 20:33, 14 June 2008
Description
This page is intended as placeholder for preparing the Domoverse platform project.
It is a project whose aim is to explore the HMI capabilities of Metaverse-related technologies (OpenSim/OpenLife/OpenCroquet/Solipsis) in a domotics context (X10/Z-Wave, Gumstix, ZigBee...), as home server control and root web house.
Project organization
- State of the art: metaverse platforms and domotics management systems
- Evaluation of metaverse and domotics management systems candidates
- Implementation of a tmplab server for experimentation
- 3D Replication of the lab and it's electronic devices
- Implementation of XMLRPC-like server for services exposition (X10, ...)
- Linking virtual objects' actions to XMLRPC calls
- Gluing all together for first prototype
- Hardware integration on low-consumption devices (WRT?)
Components
- XMLRPC server:
- keeps a list of all detected devices and features
- exposes their functionality trough the remote procedure call interface
- hosts a 3D modelization of controlled items
- device_connectors: protocol-specific plugins
- X10 devices exploitation
- ZigBee
- Z-Wave
- metaverse_connectors: metaverse-specific components (speaks with metaverse server)
- metaverse objects and scripting codebases and snippets, domoverse-related templates and coding resources
