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: Protocol name (again)


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

RE: Protocol Name


  • To: <ukha_d@xxxxxxx>
  • Subject: RE: Protocol Name
  • From: "James Hoye" <james.hoye@xxxxxxx>
  • Date: Tue, 12 Jun 2001 14:23:23 +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

This email was delivered to you by The Free Internet,
a Business Online Group company. http://www.thefreeinternet.net
---------------------------------------------------------------
> Am I the only one who thinks accronyms are a bit naff. Why is it
necessary
> to have the project name spell out some words that might be loosely
> connected. Take HomeVision for example or Comfort, they are
> reasonable names
> without all this faffing about. I selected Solarfish for my
> company because
> it was simple, unique on the internet (though some sod be me to it for
a
> yahoo ID), usually spelt correctly when read out over the phone and
fairly
> easy to make into a logo. Whether you like the end result or not I
don't
> really care, but the point is that these things could be more
> important than
> getting it to actually spell out something. Just IMHO of course.

What about Xcape?

eXtensible Control and Automation Protocol over Ethernet, or in Paul
Gordon's case, X-rated Control and Automation Protocol over Ethernet!!!

James H




____________________________________
Automated Home UK
http://www.automatedhome.co.uk
____________________________________

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.