The UK Home Automation Archive

Archive Home
Group Home
Search Archive

Advanced Search

[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

More questions......

  • Subject: More questions......
  • From: "turner228" <kevin@xxxxxxxxxxxxxxxx>
  • Date: Wed, 20 Oct 2004 18:38:17 -0000

Well I have some more questions after reading various specs and so
on (again):-

The specification says taliking about a source address
"The <vendor> field is assigned to the device developer by the
So If I were to write a connector program to interface with some
external device, say using VB and the OCX (from Patrick Lidstones
site I think (which appears to be down at the moment)) Would someone
here have to agree the vendor ID with me?

The specification also talks about Target addressing. Thinking about
the desktop, is this supported for the different displays on a
desktop, or will it be?

I am a little confused about the schema. I have seen examples in the
specification and elsewhere, eg

Which don't seem to be supported by published schema. Are they valid
schemas or just examples?

Are the schema fixed, can they be modified and new ones created? By
anyone who is developing? Is there an approval process? (and by
developing I don't just mean the core xAP team but those of us who
might use the OCX or some scripting say within Homeseer)

For instance I have a couple of LCD devices which have 8 rows by 24
characters. This could not be supported by the display.text schema
because it only allows 5 lines. So could I create a display.biglcd
schema based on that of display.text?

To be clear, I am not trying to be awkward, just to understand, and
I am fully recognise the part time/hobby status of the key players
who are producing the goods


xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

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.