Questions about slur object

[rpatters1]

I am diving into the slur object and some questions arose.

• lineType I am not certain what this is. Is it a string-valued enum? If so, shouldn't it have a list of values? I could imagine it being choices like "dashed" and "solid", but then the comment about software determining it when absent doesn't make sense. When absent it would seem like the default should be "solid".
• location Is there a use case for this beyond excerpts and cues where target/previous is cut off? The example file appears to be using it like an l.v tie, which is already covered in tie.
• sideEnd Rather than specifying that it is the same as side when omitted, could it be changed to be "usually" the same as side? In the cross staff example given, I would like to be able to leave it up to the consuming software to decide the side of both ends. (when the consuming software would decide they should be different.)

[adrianholovaty]

Thanks for bringing these up.

For lineType, that is indeed a string enum. I've filled in the allowed strings (taken from MusicXML) in e701cc1.

For location, that was indeed a poor abstraction. I've removed that in 624271e. I also removed the example document; eventually I'll add a new example document for l.v. ties, which was really the better approach (as you say).

For sideEnd, thanks, I've just updated the docs in b031d91 to remove that default value.

[samuelbradshaw]

Thank you for the in-depth work you're doing, @rpatters1, to make sure MNX is robust enough to handle all of these cases!