Your concluding rationale is exactly what the point is. Those failing to
use the inherent capability of the file system to sort resources which by
default also groups similarly named resources together are not
effectively fulfilling the client's needs.
For at least the 20 years I have been introduced to and involved
with Computer Science the methodology has been noun-verb
grammar. The subject of the sentence must be included and in
its proper place or the sentence is considered to be malformed
or a fragment and thus incoherent. In this context what we see
is a complete abscence of title text or an adjective-noun grammar
of the type 'title text - personal identifier.'
The only cogent argument I have heard suggested the reason people
use converse file naming in this context 'title text - personal identifier'
is due to the fact that the Windows menu used to recall a Favorite
only allows a fixed number of characters to be displayed when one is
attempting to retrieve a Favorite. Thus, the rationale suggests that
'title text - personal identifier' makes reading the title text easier as
the
arguement presumes to suggest that doing so displays more meaningful
text. Fallacious assumption if you ask me.
In all fallacies there is a basis of fact followed by an illogical
conclusion
and while I do find the 'readable Favorites' arguement alluring it still
obviates the objective of fulfilling the client's needs because it breaks
the
file system's inherent function to sort and group file resources.
If people wanted to create title text correctly they would adopt the
'personal identifier - title text' convention. If consideration is to be
given to the fixed number of characters displayed by a Windows
menu, the personal identifier could and perhaps should be a form
of something akin to Hungarian notation or an acronym or other short
personal identifier. If brevity is needed so as to avoid imposing what may
be an inordinate number of characters in the recalled Favorite there is no
need to remind the client that they are attempting to retrieve a Favorite
from
'My Overtly Lengthy Corporate Brand Name Inc.' other than that need
that is imposed by marketing idiots.
The Windows OS persists tool tip text when retrieving a Favorite using
the Windows OS menu. Unlike the tool tips displayed in a browser those
displayed by the OS persist and will remain displayed until a new event
takes
precedence.
If the client really needs a long and winded corporate brand as contextual
information he or she can observe 'branding' by reading the tool tip where
the domain name is displayed. Maybe its also time for those developing
Longhorn to consider this user interface issue and perhaps include the
ability
of reading meta data from the file that can be used to provide a better
description of resources stored on the file system.
Finally, what seems to be missing (other than common sense surrounding
this issue) is that we as users attempting to retrieve Favorites do so
needing contextual reminders. Those reminders are the personal and
perceptual identifiers such that I or you could easily recall and associate
the
specific resource with its source of origination from whom we have
established a sense of reliability and credibility regarding the actual
content we are hoping to retrieve.
Many analogies can be useful but one of speaking on the telephone
seems to be very apt. For example, when calling somebody we are
taught to say 'hello' followed by 'this is so and so' followed by 'I
am calling about.' This is classic 'personal identifier - title text'
structure
and it has been adopted as convention for good reason.
Surely when retrieving a Favorite regarding for example subject matter
about ASP.NET security you would prefer to return to the page(s) that
were crafted by someone whose writing and documentation has already
been perceptually established in your mind as that which you find credible
and well done? In the tactile environment we have turned corners, coffee
stains on paper, written notation and other artifacts to remind us. In the
virtual world we have descriptive text and the file system. Hello?
To be a tad abstract here I am saying the base class for perceptual human
understanding is that which has members that establsih precedence and order.
The 'title text - personal identifier' structure breaks the file system and
it
convolutes human understanding. I also have examples of this in another
context related to accessibility and screen readers which is another
subject but directly related to the way convention and usage are understood
to be useful and desireable objectives if in fact fulfilling the client's
needs
is our primary objective.
The whole notion of the semantic web relies on this type of common
sense and practical thinking. I hope taking my time to argue the merits
helps others understand. While I can stand the scrutiny of argument to
ignore or dismiss the argument all together suggests there is a 3rd way to
identify an idiot web developer.
--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET
cs*********@REM OVETHISTEXTmetr omilwaukee.com
URL
http://www.metromilwaukee.com/clintongallagher/
"David Jessee" <dj*****@housto n.rr.com> wrote in message
news:ua******** ******@TK2MSFTN GP12.phx.gbl...
Man, that's just being petty.
...and for the record (many people would do well to remember this), there
is no "correct" convention for anything. All that matters is (1) You're
consistent and (2) you effectively communicate the information. The RIGHT
way (whether its naming conventions, development methodologies or
application frameworks/architectures) is the way that lets you effectively
fulfill the client's needs.
"clintonG" <csgallagher@RE ************@me tromilwaukee.co m> wrote in
message news:eP******** ********@TK2MSF TNGP12.phx.gbl. .. I can't tell you how frustrated I get when going to a web developer's
website and observing he or she is an idiot that has not grasped
the most fundamental element of usability: page title naming
conventions.
1.) You know you are at an idiot's website when there is no page title.
Listen up idiot. Give every page a name using the HTML <title> element.
2.) When naming your page do not put the name of your website or your
company 'after' the page title text. The name of your website or your
company name should be placed 'before' the page title text. Assuming
the idiot has at least provided a page title consider...
Incorrect Page Title Naming Convention:
I Am An Idiot And Here's The Proof - IdiotWebDevelop er.com
Correct: Page Title Naming Convention:
Smart Web Developer - How to Avoid Being Identified As An Idiot
The correct page title naming convention is correct as it provides a
meaningful description of the contents of the page and the order of the
page title text 'after' the developer's website or company name allows
the developer's pages to be sorted as a group when saved as a Favorite.
--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET cs*********@REM OVETHISTEXTmetr omilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/