RE: Re: [Project] XML, Byte Encoded XML, How does it talk ?

["James Hoye" <james.hoye@xxxxxxx>]

This email was delivered to you by The Free Internet,
a Business Online Group company. http://www.thefreeinternet.net
---------------------------------------------------------------
> Maybe it should go like that: "Each 'simple' (not supporting XLM)
device
> should come with a 'device driver', which is a XML file specifying
> operations device can perform. Device driver should include
> tokenizing table
> to allow the hub to talk with the device via simplified,
> 'byte-encoded XML'
> protocol."

Now we're getting somewhere!

A simple device (eg. light switch, temp. sensor, dimming module) can talk
its own or a common, simple protocol to a controller that will understand
it
(eg. light module, dimmer module) for direct control. A SBC, PC or other
box
with more processing power/storage that a simple micro controller could be
loaded with a 'device driver' to understand what's going on and to provide
a
programmable interface, allowing a UI/whatever to sit on top.  I wouldn't
envisage a lightswitch talking to a PC - probably to a controller which
could then pass through to the PC - that way if the PC dies/crashes (for
Windows users) local control will still be possible as the controller will
be aware of the PC dying and could process the command itself.  This way
you
would not be reliant on a PC to provide control.  Of course, if the
controller died....

This is starting to get complex - and we've only just begun.  I think that
a
brainstorming session is definitely needed at this early stage - as once we
start speccing and prototyping it's going to be difficult without any firm
guidlines to follow.

James H




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/