chen.nary@3

Primary palette

Relationship roles

Profile verification

• Select entity definitions; attributes are generated from their fields and associations from source relations, including explicit n-ary assoc. Generated chen.entity/attribute/association marks are occurrences, not duplicate stored business objects.
• Keep field identity behind attribute ovals and relationship identity behind diamonds/spokes.
• Composite attributes use real nested fields. Derived, multivalued, key and partial-key adornments stay independent; keys cannot be derived/multivalued.
• A weak entity names a selected owner, has a partial key and exactly one identifying association; owner dependencies are acyclic.
• Both participant ends declare min/max bounds; identifying relations name their owner and weak entity.
• N-ary assoc adds one to six extra distinct selected entity ends beyond the binary anchors; each end retains role/multiplicity or bounds.
• Render one diamond with a labelled spoke for every participant. This version replaces the inherited binary-only rejection for n-ary assoc; ref remains binary.
• Only entity objects and object-level assoc/ref endpoints are rendered; field/port endpoints are rejected even though the base native relation role permits members.

Profile defaults

Explicit file settings override eligible CSS, then these profile defaults and the common standard apply. Unspecified semantic facts remain unspecified.

{
  "projection.kind": "chen",
  "projection.profile": "chen.nary@3"
}

Projection properties

kind, profile, width, height

Search the property codex

Design operations

• Create or select entity; edit its fields; connect a binary relationship; inspect the source identity of generated attribute and relationship marks.
• Add/remove/reorder extra participant ends on an association; edit the role and multiplicity of each end while retaining one relationship identity.

Outside this profile

• lossless external format interchange
• n-ary relationship semantics beyond visual association