The list of a field's values in contracts may consolidate values from different domains
Only a field of type one of in a RecordType described in contracts may have as its values those the domains add, each domain listing the values it adds in a rule of its own.
A RecordType described in contracts is shared by the domains, and so are its fields, so each domain may add the values it brings, and the variants answering to them (§s-z3dnru6qqdf9m6j), without changing the RecordType, which the owner of contracts holds. A RecordType one domain provides is described in that domain (§s-7vm323mhry2enx3), so that domain alone answers for its fields' values and declares them itself.
The links it makes
The links made to it
The decisions taken on it
- Problem
The rule named, beside a field's own list of values, the tables one project's tools read such values from.
- Ruling
The owner: the SpecSheriff guidelines keep the field's own list, and a project's own guidelines may declare such values elsewhere (§s-bsya3febm6u64ab).
- Problem
The rule allowed a place a project's own guidelines name for a variant's values, and nothing described how they name it, so the tools read the field's own list alone.
- Ruling
The owner: the other place stays and is described. For a data record described in contracts, a rule of a domain defines a list of the field's values and refines the data record by its sid; the tools collect the values from every such list and refuse one declared twice, the variant stands where its value is declared, and the generated types list every value. A data record one domain provides keeps its values in its own field, as the rule on contracts requires.
- Problem
The values the domains add to a field of contracts stood in one rule with every other source of a field's values, named the lists of domains, which read as the list of the domains, and stated from the field's side.
- Ruling
The owner: the list of a field's values declared in contracts may consolidate values from different domains, the field being shared by them; only such a field may have as its values those the domains add, each domain listing its own in a rule of its own, and a data record one domain provides declares its fields' values itself.
- Problem
The node named a kind of node "data record" and a node's place "address" or "id".
- Ruling
A technical replacement following the owner's decisions of that day: a data record is a RecordType, and a node's address or id is its location.