Notations are stored in the notation table with a notation_type discriminator value of the lower case element name, with dashes replaced by spaces. Examples: tied, accidental mark.

Notation records each belong to a notations list that is referenced in the notations table (notations list records then join to a note record in the music_data table).

A tuplet's tuplet-actual and tuplet-normal values are each separate records in the tuplet_portion table, joined on foreign keys tuplet_actual_id and tuplet_normal_id in the notations record.

The MusicXML schema allows a dynamics object to be used as either a notation or a direction type. In the database schema, dynamics data are stored as direction_type records.

A dynamics defined as a notation in a MusicXML file is stored as a notation record with discriminator value dynamics, and a joined record in the direction_type table (discriminator value dynamics) contains the dynamics data.