[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
RE: Protocol Name
- To: <ukha_d@xxxxxxx>
- Subject: RE: Protocol Name
- From: "Graham Howe" <graham@xxxxxxx>
- Date: Tue, 12 Jun 2001 13:31:49 +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
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.
Graham
____________________________________
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
|