The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: Re: Long SCART working nicely


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "'ukha_d@xxxxxxx'" <ukha_d@xxxxxxx>
  • Subject: RE: [Project] XML, Byte Encoded XML, How does it talk ?
  • From: "Broadfoot, Kieran J" <Kieran.Broadfoot@xxxxxxx>
  • Date: Thu, 24 May 2001 12:11:26 +0100
  • Delivered-to: rich@xxxxxxx
  • Delivered-to: mailing list ukha_d@xxxxxxx
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

Stuart,

I completely agree however I think XML and its derivatives are very
extensible.  My thinking was that we define a simple communication protocol
which all devices must be able to use, each device then builds on this by
providing the rest of its functionality to the network in XML as well.

A light switch would need to be able to handle the standard protocol such:

Provide Unique Address
Provide Status
etc

The light switch would then inform the console of its other functions:

Status = on, off, 5% on ... 95% on.

Of course the more complex the device the more it will provide but the
protocol becomes more extensible.

I am still tempted to suggest that we use a more complex controller per
room
and use a bus for communication with devices.

Thanks
Kieran


> However, I'm a bit worried that were trying to define a protocol when
we
dont
> really know what we want to do with it, other than the brief outline
of a
> device in it's name.


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




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




Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.