Difference between revisions of "Form:Association Theory"
Jump to navigation
Jump to search
| (11 intermediate revisions by the same user not shown) | |||
| Line 79: | Line 79: | ||
! Formulation Text: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">Give the exact formulation of the theory here. IMPORTANT: Please avoid any wiki markup here, such as references, or wiki links.</p> | ! Formulation Text: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">Give the exact formulation of the theory here. IMPORTANT: Please avoid any wiki markup here, such as references, or wiki links.</p> | ||
| {{{field|Formulation Text|input type=textarea|rows=5|mandatory}}} | | {{{field|Formulation Text|input type=textarea|rows=5|mandatory}}} | ||
| + | |- | ||
| + | ! Formulation File: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">Often formulations need to appear in a standard box with a title and text. Select or upload the image for this formulation.</p> | ||
| + | | {{{field|Formulation File|input type=text with autocomplete|existing values only|values from namespace=File|uploadable|property=Formulation File}}} | ||
|- | |- | ||
! Association Type: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">Aggregation is a '''Has-a''' relationship, where one class can exist independent of another. A composition is a '''Part-of''' relationship, where the part cannot exist independent of the whole. For all other types of relations, select "Association".</p> | ! Association Type: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">Aggregation is a '''Has-a''' relationship, where one class can exist independent of another. A composition is a '''Part-of''' relationship, where the part cannot exist independent of the whole. For all other types of relations, select "Association".</p> | ||
| − | | {{{field| | + | | {{{field|Association Type|input type=dropdown|mandatory|values=Aggregation,Composition,Association|default=Association}}} |
|- | |- | ||
| − | ! Association Direction: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">This is important for aggregation and composition relations: the direction is always from the "child" class to the "parent" class, from the "part" class to the "whole" class, and from the "element" class to the "aggregate" class.</p | + | ! Association Direction: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">This is important for aggregation and composition relations: the direction is always from the "child" class to the "parent" class, from the "part" class to the "whole" class, and from the "element" class to the "aggregate" class.</p><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">Left-to-Right: the right class is the parent (e.g. in "A theory is an answer to a question", the question is the parent, so the direction should be Left-to-Right).</p><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">Right-to-Left: the left class is the parent (e.g. in "A theory can be presuppsoed by a question", the theory is the parent, so the direction should be Right-to-Left.).</p> |
| − | | {{{field|Association Direction|input type=dropdown|mandatory|values=Left-to-Right,Right-to-Left|default= | + | | {{{field|Association Direction|input type=dropdown|mandatory|values=Left-to-Right,Right-to-Left|default=Left-to-Right}}} |
|- | |- | ||
| − | ! Left Role: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">What role does the left class play in this association?</p> | + | ! Left Role: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">What role does the left class play in this association? On class diagrams, this label will appear on the connector next to the left class (e.g. in "A theory is an answer to a question", the role of a theory is "an answer to" or "answers").</p> |
| − | | {{{field|Left Role|input type=text|size=50|maxlength= | + | | {{{field|Left Role|input type=text|size=50|maxlength=20}}} |
|- | |- | ||
| − | ! Right Role: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">What role does the right class play in this association?</p> | + | ! Right Role: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">What role does the right class play in this association? On class diagrams, this label will appear on the connector next to the left class (e.g. in "A question presupposes theories", the role of a theory is "a presupposition" or "presupposed").</p> |
| − | | {{{field|Right Role|input type=text|size=50|maxlength= | + | | {{{field|Right Role|input type=text|size=50|maxlength=20}}} |
|- | |- | ||
! Left Multiplicity: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">How many instances of the left class can be in association with an instance of a right class? E.g. 0..*, 1..*, 0..1</p> | ! Left Multiplicity: <br><p class="sfFieldDescription" style="font-size:0.7em; color:gray;">How many instances of the left class can be in association with an instance of a right class? E.g. 0..*, 1..*, 0..1</p> | ||
Latest revision as of 15:41, 15 January 2023
This is the "Association Theory" form. It is used to create new entries for ontological claims about aggregation, composition, and other association relations. When the form is used to create a new association theory (as opposed to merely editing an existing one), it expects one of the following parameter to be passed onto the query string:
query string= Term= //the left class
