i'-45 Thus, to define an output concept nun~ber of 285, and to attach it to node nun~ber 3 instead of the keynode, and also to double its weight, the user punches =285.3.*6 as an output concept number field. If, in addition, the concept number on node 2 is to be moved onto nodes 4 and 5 with half weight, another output concept nun~ber field would be added, the total reading: =285.3.*6=N2.4.5.*3 c) it is also necessary to supply the conditions specified for each node. For each node ex&ctly one node condition fiel& exists, except that conditions need not be specified for the last node (and adjacent nodes) if a definition using a tree type is en~loyed, and the syntactic and structural criteria supplied by the type are all that is needed for these trailing nodes. The first node condition field begins immediately after the output concept number fields. Each node condition field is followed by a slash, (I) except for the last node condition field which is followed by a dollar sign ($). If the tree is being defined according to a standard type, oniy the semantic information need be supplied in the node condition fields. If a type is being defined, however, or if a tree is being defined without the use of a type, all information `mist be supplied for each node. In this case, there ~st be exactly as many node condition fields as there are nodes in the final tree. If structural data is being specified, all but exactly one node condition field should begin with either an I or a D followed by an integer. The node whose condition field does not begin with an I or D is taken as the root of the criterion tree. A node whose condition field begins with tInli niist match a node which is descended from (direct or indirect ancestor) the correspondent of node n~~er n. A node whose condition field begins with "~" must match a node which is the direct (first-generation) descendant of the node which matches node n. "Descend'1 is understood in the