GlossaristGlossarist

Hyperedges · Playground

Hyperedge Playground

Edit hyperedge YAML on the left; the rake renders live on the right with inline validation. Three preset examples cover the common shapes. This is a teaching tool — for production validation useglossarist-ruby orglossarist-js.

Examples:
112-02-09partitive_relationcompleterequired · exactly_one112-02-10required · multiple112-03-26optional · exactly_one112-02-06criterion: measurement result composition
Validation0 errors · 0 warnings
  • okAll structural checks pass — comprehensive + ≥2 members + valid MECE combos.

What am I looking at?

The diagram follows ISO 704:2022§5.5.4 line notation:

  • Single solid line — required · exactly_one (compulsory part)
  • Double solid line — required · multiple (compulsory multiple parts)
  • Single dashed line — optional · exactly_one
  • Single solid + single dashed — required · at_least_one
  • Bold 3x-width line — is_delimiting: true (partitive only, distinguishes from coordinate concepts)

For generic_relation, every member must carry a delimitingCharacteristic(the intension-difference text per ISO 704 §5.5.4.2.1). The renderer shows it under each species.

Validation rules checked

  • type is partitive_relation or generic_relation
  • comprehensive is a non-empty ConceptRef
  • members has at least 2 entries (ISO 704 "two or more")
  • Every member's ref is a non-empty ConceptRef
  • Invalid MECE combo (optional + at_least_one) rejected
  • generic_relation members must carry delimitingCharacteristic
  • Warning: is_delimiting + presence: optional is semantically incoherent

Learn more