Dbquity Metamodel

The busy diagram below captures the Dbquity Metamodel where each box can be clicked taking you to the reference page of the notion that it represents, and the boxes with non-italic names also directly represents a keyword in the Dbquity Modeling Language and reveal language syntax in their tooltip.

A model is either a site or a library, which comprises any number of classifiers, each of which is either

• an enumeration with a set of named options, or
• a complex, which may nest a number of other classifiers, compose a number of members of type field, action, or function and is either
  • a class,
  • an entity composing a number of step, filter, and query members organised by a behaviour expression, and with
    • either a named collection and (most often) an identity field, or
    • a singleton modifier, or
  • a specialised entity, which is either
    • an association, which composes one or more end members,
    • a container, which is a singleton by default and may declare access permissions,
    • an area, whichs is a singleton container and acts as the root of all collections, or
    • a blob, which may store a binary large object such as an image or a video clip.

A model may declare references to other models to use classifiers declared in these other models.

A curious note about the metamodel diagram

The diagram is generated using the dot command of the CLI:

dbquity dot overview metamodel -filter:primitives+Classifiers+Members+Models+Core +l -r -nolabel

and then manual removal of the base edges from element to parameter and from member to field in overview.dbquity.dot followed by

dot2svg overview

If you open the source file, Metamodel.dbquity, you'll notice that it is quite atypical, because in addition to an abundance of diagramhint properties it abuses most of the language keywords and redefines them to declare pseudo entities that capture the metamodel including site, field, and entity.