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.
Subject:Re: Looking for words From:"Olivia C. Williamson" <olivia -at- SULMAIL -dot- STANFORD -dot- EDU> Date:Tue, 6 May 1997 16:51:47 -0700
On Tue, 6 May 1997 20:17:57 GMT Len Olszewski <saslpo -at- UNX -dot- SAS -dot- COM> wrote:
> In article <8625648F:006BC57C -dot- 00 -at- gpsnotes8 -dot- gps -dot- com>, RJACOBSE -at- gps -dot- com writes:
> |> I'm looking for alternatives to the words "parent" and "child" to describe
> |> entities in a outline-like conceptual structure. One alternative for
> |> "child" is "dependent," but I can't think of an easily aprehended analog
> |> for "parent."
> "Main" and "subordinate" seem to work here. You could try "primary" and
> "subordinate", or if you need other levels, "primary", "secondary",
> "tertiary", and so forth.
The only other terminology I've seen is that used for directory structures,
with "branching nodes" and "leaf nodes". Example: C:\Windows\win.ini is a
leaf node, while the next higher node is C:\Windows, a branching node that
contains other nodes.
However, if you have a lot of levels, that might get clunky.
Why do you want to avoid parent and child?
Olivia C. Williamson
Manager, SUL/AIR Expert Partner Program
olivia -at- sulmail -dot- stanford -dot- edu