Sorry to be coming back to this so late in the thread. MusicXML seems to already specify that xml:id can be used as per Thomas Weber's suggestion, independently of the "id" attribute as defined in MusicXML: http://www.musicxml.com/for-developers/musicxml-xsd/xml-namespace/ This would be an area that I would want to clarify in MNX by avoiding use of any MusicXML-specific "id" attributes, so that there is no potential for conflict. I see xml:id as ultimately becoming the only "id" attribute. . . . . . ...Joe Joe Berkovitz President Noteflight LLC +1 978 314 6271 49R Day Street Somerville MA 02144 USA "Bring music to life" www.noteflight.com On Wed, Aug 3, 2016 at 9:05 PM, Thomas Weber <tw@notabit.eu> wrote: > Am 03.08.2016 um 18:18 schrieb Michael Good: > > Unfortunately we can't quite do the "every element has an id attribute > that is an ID type" proposal without breaking compatibility with earlier > MusicXML versions. MusicXML 3.0 already has several commonly-used elements > where the id attribute is an IDREF rather than an ID. > > > > > > Standards to the rescue: With xml:id attributes, there's no > incompatibilities with earlier versions. > > https://www.w3.org/TR/xml-id/ > > >
Received on Monday, 19 September 2016 16:03:51 UTC