Skip to content

Clarify purpose of hierarchy, consider a more general relationships construct to complement it. #31

Closed

Description

@mindsocket

Status: WIP on extending hierarchy to support a "layered DAG" construct. More general relationships approach for non-hierarchy rels TBD

Schema metadata includes a 'hierarchy' attribute, used for hierarchy validation.

I think this basically serves as an optional convenience to get hierarchy validation automatically, but schemas generally don't depend on it.

A more graph-based schema (or hybrid with partial hierarchy) in theory should also work, but the onus is currently on the schema maintainer to enforce those relationship rules another way.

It might make sense to also allow expression of relationships with corresponding automatic validation.

Will need to think about how relationships are expressed in markdown and in schema. A simple start might be to write some jsonata rules that are parameterized, which could be generally useful or render the need for a specific relationships spec unnecessary

Activity

  1. changed the title [-]Clarify purpose of hierarchy, consider a more general relationships construct to complement it.[/-] [+]Clarify purpose of hierarchy, consider a more general relationships construct to complement it. Will need to think about how relationships are expressed in markdown and in schema. A simple start might be to write some jsonata rules that are parameterized, which could be generally useful or render the need for a specific relationships spec unnecessary[/+] on Mar 7, 2026
  2. changed the title [-]Clarify purpose of hierarchy, consider a more general relationships construct to complement it. Will need to think about how relationships are expressed in markdown and in schema. A simple start might be to write some jsonata rules that are parameterized, which could be generally useful or render the need for a specific relationships spec unnecessary[/-] [+]Clarify purpose of hierarchy, consider a more general relationships construct to complement it.[/+] on Mar 7, 2026
  3. mindsocket commented on Mar 8, 2026

    @mindsocket
    OwnerAuthor

    While more general relationships are good to think about, the more proximate opportunity is to expand from a hierarchical tree to a hierarchical/layered DAG. https://g.co/gemini/share/5ff3bbec3ffb

    In short, we keep the hierarchy concept, add a way to specify, express, validate and visualise the layers that have many to many relationships.

    Specify:

    • hierarchy array (existing)
    • a way to indicate per node type pair which ends specifies (parents specify array of children or children specify array of parents), and field name

    Express: single wikilink or array matching above

    Validate: ensure resolved nodes models and accurately reflects (I'm thinking it should normalise children refs to parent refs on child nodes); ensure we only read relationships as specified ( if expecting children don't allow parents on the other end)

    Visualise: ok for Miro, show command may need a dag based format instead of bullets, or to denormalise.

  4. self-assigned this
    on Mar 8, 2026
  5. mindsocket commented on Mar 9, 2026

    @mindsocket
    OwnerAuthor

    Reviewing the collection of modelling issues, here are some observations:

    Scope Overlaps & Gaps:

    Suggestions:

    1. Consolidate Consider more opinionated sub-entities - problem statement, risk, assumption, insight, decision, principle #5, Integrate with other systems of work? #6, Cross-space references: linking entities across schemas and spaces #8 under a 'schema extensions' umbrella - they're all about extending the basic model
    2. Clarify that Clarify purpose of hierarchy, consider a more general relationships construct to complement it. #31 is about graph relationships (DAGs, multi-parent) while Schema composability: shared building blocks and team-composed schemas #17 is about schema composition
    3. Consider adding a new issue for 'temporal relationships' to capture evolution of entities
    4. The modelling scope feels appropriate but could benefit from clearer separation between:
  6. mindsocket commented on Mar 9, 2026

    @mindsocket
    OwnerAuthor

    This issue may also depend on #33 (Support full cross-schema resolution of refs) - if we want relationships to reference schema definitions across files, we'll need full cross-schema resolution first.

  7. mindsocket commented on Mar 17, 2026

    @mindsocket
    OwnerAuthor

    Most of this has been address in #52 . New issues cover potential refactor and extension to ways of supporting relationships.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions