Hmm, interesting. There's been a lot of work done on classification of abbreviations in the medical field.

In terms of avoiding rote memorization, the thing that helps people memorize is *structure*. So for the Mac, one assumes that there is a certain order used in creating the sandwhich (bun,meat,cheese, toppings? I dunno, I'm a vegetarian :-)). If the specifications go in the same order as the construction of the sandwhich the user has an automatic leg up on memorization. This is where knowing the knowledge domain you are dealing with becomes relevant and generic BigMac examples fall down - what is there in your domain that is already structured and how can you make use of that structure in deciding on a nmaing scheme?

In reply to Re: How do you name the possibilities? by jZed
in thread How do you name the possibilities? by dimar

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.