My comments below:
Rich AT EnglishLogicKernel DOT com
9 4 9 \ 5 2 5 - 5 7 1 2
On Sep 9, 2010, at 4:18 PM, doug foxvog wrote:
> Why? Every author of Java code uses the
same meaning of "method" and
> other reserved words. Every HTML author
uses the same meaning of
[CONTEXT = UNNATURAL LANGUAGE WITH NO LOGIC = ON]
I would call compiler keywords like
"method" or document parts like "title" to be content free
syntactic signs, not meaningful except between the programmer and the compiler.
Now I understand
But those are the "verbs" that come with
every software language.
Use them, spell them correctly or find other
work. Plus you have a
compiler looking over your shoulder. The VERBs
are documented in
The slippery ones are the NOUNS that people more often
than not make
up on the fly... makes sense to them... use it.
Very difficult to
decode 6 months or 6 years later.
For example, Noun Phrases are often beset
with the "wrong" interpretation of which noun is the head noun. It
isn't always positional, it is dependent on the context in which the utterance
My version of triples is VERB + OPERATOR + NOUN.
VERBs & OPERATORs
are controlled by the compilers... NOUNs are largely
The differences of underscores vs dashes and UPPER vs
just silliness & of minimal significance.
Allegedly NOUNs should be documented in mythical
variously "data dictionary" or
"metadata repository." By a show of
hands, who on this list has been in an organization
that has a
useful, accessible, accurate, & complete
business people, analysts, project managers & developers
look up what something means?
My hand votes that the data dictionary is
only useful among the DB engineering staff because the entries parse in the
database language and properly match certain names for columns, tables, values,
constraints, etc. The data dictionaries I have seen and used are by no
means consistent, and are often difficult to change or resolve errors in.
Allegedly a field/column/data element should have a
often they don't.