The id attributes introduced by the v3.1 are definitely a great feature that deserves becoming standard in any MusicXML software. But today, many MusicXML-exporting software (such as Finale Dolet) do not generate those IDs yet.
I suggest providing XSLT for ID generation.
On this fork, here are a draft proposal. It consists in two XSL files, generateIdMusicXmlTimewise.xsl and generateIdMusicXmlPartwise.xsl, that add generate missing IDs for all elements that may have such id attribute.
About the format of ID values, the one I suggest is name-XXXXX, where nameis the element name and XXXXX is an alphanumeric hashcode.
This would encourage people introducing IDs in their MusicXML files.
We cannot accept this script as-is since @PhilippeCuvillier is not a member of the W3C Music Notation Community Group. I plan to move this out of the 4.0 milestone.
Here is a another feature request.
The
id
attributes introduced by the v3.1 are definitely a great feature that deserves becoming standard in any MusicXML software. But today, many MusicXML-exporting software (such as Finale Dolet) do not generate those IDs yet.I suggest providing XSLT for ID generation. On this fork, here are a draft proposal. It consists in two XSL files,
generateIdMusicXmlTimewise.xsl
andgenerateIdMusicXmlPartwise.xsl
, that add generate missing IDs for all elements that may have suchid
attribute. About the format of ID values, the one I suggest isname-XXXXX
, wherename
is the element name andXXXXX
is an alphanumeric hashcode.This would encourage people introducing IDs in their MusicXML files.
(P.S. : some XSpec unit tests are also provided)