Skip to content

Create Architecture Schema #53

@SeanMcOwen

Description

@SeanMcOwen
  1. It will be what you get when you have a collection of blocks/spaces or as Z puts it:
    " the pattern you get when you take a system and say "this pattern of blocks and spaces" but not necessarily THESE concrete processors satisfying the definition of an architecture and should probably be supported at the toolbox level -- think of its a coloring book -- Fill me in however you want but please paint in the lines!"
  2. Should it be an optional attribute of a toolbox which you don't have to use, but can have multiple versions of to record some standard architectures?
  3. Is this something we want to have that a system would have as a parent?
  4. Would this be better to have as an extension versus in the core protocol?

One way we could design it would be:

Toolboxes have an optional attribute of Architecture which is a list of json docs which have:

  1. Name
  2. Description (Optional)
  3. Blocks
  4. Spaces

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions