Question: how should API clients attach notation attributes to regular ties?

[rpatters1]

I see that mx::api::NoteData currently has two tie-related surfaces:

1. NoteData::isTieStart / isTieStop

   • These write the sound-level <tie type="start|stop">.
   • They also appear to write a notation-level <tied type="start|stop">.
   • However, the bool path has no place to attach notation attributes such as orientation, placement, bezier data, etc.

2. NoteData::noteAttachmentData.curveStarts / curveStops with CurveType::tie

   • These can carry notation attributes through CurveStart / CurveStop, including curveOrientation.
   • But these write only <notations><tied ...>, not the sound-level <tie>.
   • If used together with isTieStart, it looks like this would emit duplicate <tied type="start"> elements.

Is there an intended way in mx::api to express a regular sounding tie whose notation-level <tied> also needs attributes such as orientation="over| under"?

For example, I would like to emit something conceptually like:

<note>
  ...
  <tie type="start"/>
  <notations>
    <tied type="start" orientation="over"/>
  </notations>
</note>

without producing duplicate <tied type="start"> elements.