Beginning with MusicXML 3.1, many MusicXML nodes can have an ID attribute. mx::api should make this available. This is related to, and requested in discussion #349 which lead to (the challenging to design and implement) issue #393.
In the discussion @rpatters1 said:
As an aside, if ID values were available in mx::api, I would be using them a lot more right now.
This is very much in this library's wheelhouse. A bit more complicated is the related #397. But with-or-without uniqueness validation, adding attribute fields that mx::api is agnostic about is easy.
Edit:
#399 exposes the most easily reachable IDs, but the following require more research or design:
Beginning with MusicXML 3.1, many MusicXML nodes can have an ID attribute.
mx::apishould make this available. This is related to, and requested in discussion #349 which lead to (the challenging to design and implement) issue #393.In the discussion @rpatters1 said:
This is very much in this library's wheelhouse. A bit more complicated is the related #397. But with-or-without uniqueness validation, adding attribute fields that
mx::apiis agnostic about is easy.Edit:
#399 exposes the most easily reachable IDs, but the following require more research or design:
mx::api#403mx::api#404mx::api#405mx::api#406mx::api#407mx::api#408