[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: BSC v1.3
- Subject: Re: BSC v1.3
- From: Kevin Hawkins <lists@xxxxxxxxxxxxxxxxx>
- Date: Sun, 26 Sep 2004 19:05:31 +0100
- References: <4156F57A.8000605@ukusa.co.uk>
> Crossposted to both xAP groups:
>
>
> Just in case anyone has missed it the specification for the 'Basic
> Status and Control' schema BSC v 1.3 is released and in the
> files area of this group. It is now far more capable than BSC v1.2
> and I strongly recommend that people have a read and consider
> including it in as many possible applications as they can,
> particularly hardware applications although it can be applied to
> software endpoints too using the text type.
> One of the great benefits of BSC is that it allows your applications
> data to be recognised and controlled by other applications
> automatically. For example HomeSeer with the xAP plugin can
> automatically discover & create devices for you that mirror your
xAP
> devices and are scriptable (controllable) from within HomeSeer.
> Likewise any HomeSeer device will appear on xAP . All the endpoints
> and their capabilities are automatically discovered and the status of
> these endpoints are tracked in realtime in for example HomeSeer.
> Where people will be using a centralised controller application with
> xAP then BSC is a wonderful mechanism for your device to be instantly
> supported without recourse to specific schema support. Of course you
> can, and should include other feature rich schemas within your
> application to fully exploit the potential of your product.
>
> BSC1.3 replaces BSC v1.2 which will be deprecated. Support for BSC1.3
> is available (either released or beta versions) for the following...
>
> xAPHomeSeer plugin
> xAP BSC Mapper
> X10 (Edwards xFX application)
> xAP Desktop
> xAP C-Bus gateway
>
> I just wanted to highlight BSC Mapper as it is effectively a matrix
> switcher or 'switchboard' for xAP - it allows any source to be linked
> to any destination using a very high speed redirection. Hence a xAP
> switch(s) can be linked to a xAP light(s) without any scripting for
> example. Taking this one step further a C-Bus switch could control
> an X10 light or vica versa....
>
> Kevin
>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|