rism-digital/pae-code-spec

Issues

• Specify how to have a fermata over an entire chord

  #65 opened 4 months ago by BaMikusi
  0

• Add a new field to representations, `version`

  #48 opened 5 months ago by ahankinson
  0

• Provide form of rests

  #41 opened 5 months ago by ahankinson
  0

• Alternating time signature representation

  #64 opened 2 years ago by lpugin
  0

• Order and spacing for score definition elements in single line input

  #62 opened 2 years ago by lpugin
  0

• Clarify order of octave and accidentals for notes

  #61 opened 2 years ago by ahankinson
  0

• Specify how to encode tied chords

  #60 opened 2 years ago by carlolic
  1

• Rename "note" column on examples

  #59 opened 2 years ago by ahankinson
  0

• Decide on order of naturals in cancellations

  #58 opened 2 years ago by ahankinson
  0

• Move MARC and UNIMARC references to the "Representations" section.

  #34 opened 2 years ago by ahankinson
  0

• Write introduction to the specs

  #57 opened 2 years ago by ahankinson
  0

• Clarification of the order requirement for octave, duration, accidental and pitch

  #56 opened 2 years ago by lpugin
  0

• Clarify methodology when encoding incipits

  #30 opened 3 years ago by BaMikusi
  7

• Add note about transposing instruments

  #52 opened 2 years ago by ahankinson
  0

• Create encoding "guidelines"

  #50 opened 2 years ago by ahankinson
  0

• Make clef a required field

  #32 opened 2 years ago by ahankinson
  0

• Clarify required clef shapes

  #33 opened 2 years ago by ahankinson
  0

• Subfield $s, coded validity note

  #25 opened 2 years ago by jenniferward
  3

• Clarify required clef, keysig, timesig fields

  #11 opened 3 years ago by ahankinson
  7

• Clarify beam nesting

  #45 opened 2 years ago by ahankinson
  0

• Add prose description to the bar/measure lines section

  #44 opened 2 years ago by ahankinson
  0

• Add prose introduction to the "Music notation" section

  #43 opened 2 years ago by ahankinson
  0

• Improve octave values prose

  #40 opened 2 years ago by ahankinson
  0

• Improve Rhythmic values section

  #39 opened 2 years ago by ahankinson
  0

• Add prose to and examples to 'Note names' section

  #13 opened 3 years ago by ahankinson
  0

• Add prose for Accidentals section

  #42 opened 2 years ago by ahankinson
  0

• Move field references for clefs, keysig, timesig, etc. to single string representation section.

  #35 opened 2 years ago by ahankinson
  0

• Explicitly spell out the form of time signatures

  #38 opened 2 years ago by ahankinson
  0

• Make key signature a recommended field

  #36 opened 2 years ago by ahankinson
  0

• Add a section on serialization formats

  #7 opened 2 years ago by ahankinson
  1

• Host legacy and new versions simultaneously

  #10 opened 2 years ago by ahankinson
  1

• Add prose to note name section

  #14 opened 2 years ago by ahankinson
  1

• Make time signature an optional field

  #37 opened 2 years ago by ahankinson
  0

• Document license and copyright

  #31 opened 2 years ago by ahankinson
  0

• Split spec into v1 and v2

  #18 opened 2 years ago by ahankinson
  0

• Clarify whether `n` is a valid accidental type in key signatures.

  #26 opened 3 years ago by jenniferward
  9

• Use of `+` for something else than ties

  #28 opened 3 years ago by lpugin
  17

• Encoding Neumatic notation

  #4 opened 3 years ago by ahankinson
  5

• Clarify multi-measure rests must be followed by a barline

  #29 opened 3 years ago by ahankinson
  1

• No double dots support for mensural notation

  #27 opened 3 years ago by lpugin
  0

• Default values in incipits?

  #24 opened 3 years ago by jenniferward
  3

• Clarification for certain meters

  #23 opened 3 years ago by jenniferward
  5

• Clarification with order of elements in ornaments

  #22 opened 3 years ago by jenniferward
  1

• Decide on editors / editorial process

  #9 opened 3 years ago by ahankinson
  1

• Clarify use of square brackets with more accidentals in key signature

  #17 opened 3 years ago by carlolic
  0

• Allow square brackets in key signature

  #6 opened 3 years ago by ahankinson
  1

• Order of sharps or flats in key signature

  #15 opened 3 years ago by carlolic
  5

• Repeated sharps or flats in key signature

  #16 opened 3 years ago by carlolic
  0

• Use RFC2119/RFC8174 keywords

  #12 opened 3 years ago by ahankinson
  0

• Determine a new version code for 031$2

  #5 opened 3 years ago by ahankinson
  0