16 06 22 Meeting Minutes

Jump to bottom

David Lewis edited this page Jun 16, 2022 · 2 revisions

Present:

Anna Plaksin
Laurent Pugin
David Lewis
Michael Friebel
Klaus Rettinghaus

Apologies: Giuliano Di Bacco, David Rizo, Martha Thomae

1. Conceptional cornerstones for the mensural module (continuing last meeting's discussion)

What are the principles for our contributions to the MEI standard (partly so we can properly justify decisions we’ve made). Ideas:

List elements that are only visual, and see what we have
Involve TC
Have general (visual) elements and different interpretations effect attributes (mostly) where notation is more interpretative

Problem: MEI usually goes straight for the meaning

Documentation to do

List of elements
Writing down principles

Do we actually know if the elements have a meaning?

One starting point for an assessment:

https://github.com/music-encoding/music-encoding/pull/848

https://github.com/music-encoding/mensural-ig/discussions/11

Complexity of visual (vs graphical) structures and its relationship with logical domain
- LP: MEI is traditionally visual first as a transcription of a document, with logical added in attributes, but this is clearer in some cases than others. Do we need more for visually representing things?
- What we want is (diplomatic) transcription rather than a facsimile
- DL Suggestion that AP digests the (very long) pull request so we can try to work out what we can usefully change to make it more acceptable and what we need to argue against more clearly.
- How do we know a proposed encoding solution is good enough:
  - Can Verovio (or other interpreters) render and align parts?
  - Can we reconstruct the symbols of the source to our (collective) satisfaction?
  - How idiomatic is the MEI? Does it change any existing part of the guidelines/ODD?
  - Does the proposal invalidate existing encodings?
  - To what extent can interpretation be removed from the encoding?

2. Organisational matters

What do we do with questions that span groups?
- e.g.
  - Mixed notation
  - Issues that arise in one group that’s of general concern, e.g. ornaments and tuning (from tablature)
  - Notation subtype
- How do we get people together to discuss this across the wider community?
Using GitHub as a common workspace
- Concerns about tech comfort
- Vs ‘tons of Google Docs’
- Metadata and MerMEId groups use the Wiki for minutes, etc.
- Issue of not many people coming to meetings, also maybe not engaging with online materials – they then lose the overview, so find it hard to come back in. Community members will appear and disappear either for professional or time reasons.
- Technical / structural decisions about documentation can lower barriers of entry or re-entry. Logical division between:
  - Issues – well-integrated into GitHub
  - Discussions – make sense for ongoing conversations
  - Wiki – more stable documents (including minutes and structures)

3. Any other business

MF asking about what he can do to help – discussion of Notre Dame encoding and