The following Message Schema have been ratified by The xPL Project:
xPL protocol core schemas
- HBEAT Device heartbeat signalling
- CONFIG Device configuration
- FRAGMENT Message fragmentation (STATUS: PROPOSED)
Home Control Family
- HVAC Interaction with HVAC related devices (thermostats etc)
- LIGHTING Control for any lighting system (X10, UPB, ZWave, CBus, etc)
- MEDIA Control of media related devices (MP3/CD/DVD players, HTPC etc)
- SECURITY Interaction with security related devices (alarm panels, motion sensors, smoke alarms etc)
- HOMEEASY.BASIC Native control of Byron HomeEasy devices
- X10.BASIC Native control of X10 devices.
- X10.SECURITY For X10 Security Devices.
- ZWAVE.BASIC Native control of Z-Wave devices.
Caller ID Family
The AUDIO.BASIC schema has been extended several times to accomodate various media players. TTS (Text to Speech) is included within the audio family, and allows various implementation of TTS engines to inject speech alerts into audio streams.
On Screen Display Family
Time of Day Family
Database and Logging Family
Remote Control Family
These schema seek to present a unified way to represent IR Control data within the xPL environment.
Digiguide TV Guide
This early schema family is improperly formed, that is, a simple .basic type has not been defined. It will probably be redesigned to more accurately reflect the mor powerful inheritance based schema model, as well as being extended to support more sources of TV guide info.
Send Message Family
This family of schema will be extended over time to support different mechanisms, such as SMS, MEN Messenger etc.
One of the most powerful message schemas, Control and Sensor work together to allow a variety of simple devices (switches, temperature sensors, buttons, beam breaks etc) to be represented within an xPL environment. The simple rule of thumb for developers is - if the message is an xpl-trig sent by a device, it should probably use "sensor.basic", if it's a command that a device should carry out (ie, an xpl-cmnd message) then control.basic is more appropriate.