[sc34wg3] RM4TM Table 1
Steven R. Newcomb
sc34wg3@isotopicmaps.org
26 Nov 2002 13:18:33 -0600
"Marc de Graauw" <marc@marcdegraauw.com> writes:
> Apparently there has been an editing mistake in Table 1.
>
> Form 8 - Case 2: 0, when a case 2 node may serve as 1+ x endpoints.
>
> In fact the entire columns Form 8 and Form 7 seem reversed, if I read
> correctly that beneath the Form row, the next row (C x ......) are node N2
> endpoint values and the next row (x C ......) N1 endpoint values.
>
> Further:
>
> Form 6 - Case 4 should be 0
> Form 5 - Case 4 should be 1
> Form 3 - Case 4 should be 0
> Form 6 - Case 5 should be 1+
> Form 5 - Case 5 should be 0
>
> Marc
Thanks, Marc, for discovering this mess. The normative
text is correct, but the table in Note 11 has all the
errors you list above.
Here is my attempt to provide a correct Table 1 (which
appears in Note 11). You need to use a monospace font
to view it. I won't object if anybody wants to check
it!
Form of 8 7 6 5 4 3 2 1 node Subject requires
Connectedness .... .... .... .... .... .... .... .... type constraint built-n
(node N2) C x C R A C A T name (if any). SIDP
node N1 x C R C C A T A (if any). Subject is: value(s)?
--------------------------------------------------------------------------------------------
N1 Case 1 0 0 0 0 0 0 0 0 (none) (unconstrained) yes
N1 Case 2 1+ 0 0 0 0 0 0 0 (none) (unconstrained) no
N1 Case 3 0+ 0 0 0 0 2+ 0 1? "a-node" assertion no
N1 Case 4 0+ 1? 0 1 1 0 0 0 "c-node" casting no
N1 Case 5 0+ 0 1+ 0 0 0 0 0 "r-node" role type no
N1 Case 6 0+ 0 0 0 0 0 1+ 0 "t-node" assertion type no
-- Steve
Steven R. Newcomb, Consultant
srn@coolheads.com
Coolheads Consulting
http://www.coolheads.com
voice: +1 972 359 8160
fax: +1 972 359 0270
1527 Northaven Drive
Allen, Texas 75002-1648 USA