TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
The "ascii form" you mention is called EBNF ("extended backus-naur format") and there is a specification for defining languages in it. The diagrams are called railroad diagrams and are usually generated from the EBNF itself.
Note that EBNF is a technical specification, and the commands/syntax you are documenting may not actually conform to EBNF depending on how sloppy your developer is.
Laura
On Oct 13, 2014, at 1:04 PM, Robert Lauriston <robert -at- lauriston -dot- com> wrote:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l