chen.binary@2

Primary palette

Relationship roles

Profile verification

• Select entity definitions; attributes are generated from their fields and relationships from binary assoc/ref edges. Do not create chen.attribute/association as duplicate stored business objects.
• Keep field identity behind attribute ovals and relationship identity behind diamonds/spokes.
• Version 1 rejects n-ary metadata; key underlining does not imply a full physical schema.
• 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 relationships remain rejected instead of being flattened.
• 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.binary@2"
}

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.

Outside this profile

• n-ary relationships
• lossless external format interchange