From 146a371de10907bf1ae369dca091532d40fb7c72 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Sun, 31 May 2026 21:19:58 +0000 Subject: [PATCH] Move docs of sdb_actor, sdb_actee, and sdb_mutual into ROLE_CODES --- doc/src/code_tables.m4 | 9 +++++++++ doc/src/tables/roles.m4 | 11 ----------- 2 files changed, 9 insertions(+), 11 deletions(-) diff --git a/doc/src/code_tables.m4 b/doc/src/code_tables.m4 index 0d80c08..9776cbe 100644 --- a/doc/src/code_tables.m4 +++ b/doc/src/code_tables.m4 @@ -793,6 +793,11 @@ The ``sdb_actor`` and ``sdb_actee`` codes When there is such a dyadic interaction and one participant is assigned one of these roles, the other participant must be assigned the other role. + This means that, for any given |ROLES.EID| value when there is a + row with a |ROLES.Role| value of ``sdb_actor`` there must be + another row on ROLES, with the given |ROLES.EID| value, with a + |ROLES.Role| value of ``sdb_actee``, and vice-versa. |transaction + commit| The ``sdb_mutual`` code The code ``sdb_mutual`` has a special meaning. @@ -802,6 +807,10 @@ The ``sdb_mutual`` code When there is such a dyadic interaction and one participant is assigned this role, the other participant must also be assigned this role. + This means that, for any given |ROLES.EID| value when there is a + row with a |ROLES.Role| value of ``sdb_mutual`` there must be + another row on ROLES, with the given |ROLES.EID| value, with a + |ROLES.Role| value of ``sdb_mutual``. |transaction commit| Column Descriptions diff --git a/doc/src/tables/roles.m4 b/doc/src/tables/roles.m4 index 8f7e4da..dc92d50 100644 --- a/doc/src/tables/roles.m4 +++ b/doc/src/tables/roles.m4 @@ -55,25 +55,14 @@ An individual can only be a participant once, in any given event. This means that the combination of |ROLES.Participant| and |ROLES.EID| must be unique. -.. These next 2 paragraphs are redundant. They are also in - the ROLE_CODES speical values section. But it seems worthwhile.... - The |ROLES.Role| values of ``sdb_actor`` and ``sdb_actee`` are :ref:`special `. They are used in dyadic interactions, where they must be paired. -This means that, for any given |ROLES.EID| value when there is a row -with a |ROLES.Role| value of ``sdb_actor`` there must be another row -on ROLES, with the given |ROLES.EID| value, with a |ROLES.Role| value -of ``sdb_actee``, and vice-versa. |transaction commit| The |ROLES.Role| value of ``sdb_mutual`` is :ref:`special `. It is used in dyadic interactions, where their must be 2 rows in ROLES each of which uses this role. -This means that, for any given |ROLES.EID| value when there is a row -with a |ROLES.Role| value of ``sdb_mutual`` there must be another row -on ROLES, with the given |ROLES.EID| value, with a |ROLES.Role| value -of ``sdb_mutual``. |transaction commit| For further information on the required, and expected, relationship between ROLES, |EVENTS|, and other tables see the documentation of the -- 2.34.1