Version 1.1 of MEAD offers the following updates over Version 1.0.1:

• The composites to describe parties have been removed. These composites have been moved, and adapted, into the new Party Information and Enrichment Standard (PIE). The only element from the PartyInformation composite of version 1.0.1 of MEAD that is retained is the ability to communicate focus tracks. This now appears in the ResourceInformation composite;

• The ##other element has been moved from the root tag into the WorkInformation, ResourceInformation and ReleaseInformation composites to allow these core composites to be extended by users (instead of adding new information lists);

• The handling of genres has been updated by adding a GenreCategory in addition to the SubGenreCageory;

• Tempo has been moved from the TimeSignature composite and made into a major composite of its own;

• Form has been added as an element on the ResourceInformaiton (it was already in MEAD 1.0.1 in the WorkInformation composite);

• ProgrammaticTheme and LyricTheme have been separated into Theme and Activity. Where the theme or activity is relating to the composition or the lyrics this can now be communicated in an attribute;  

• The same applies to DanceAndRhythmStyle which has been split into  DanceStyle and RhythmStyle; and

• The MeadMessage contains a mandatory AvsVersionId XML attribute. The AvsVersionId at  publication is 2. DDEX may update the list of allowed value sets (AVS) over time and therefore might increase the AvsVersionId over time. At that stage, the then current AvsVersionId will be made public on the DDEX Knowledge Base.

Version 1.0.1 corrects an error with the ##other element at the end of the MeadMessage. The XSD for Version 1.0 did not allow for the use of an XSD for any additional tags that a Message Sender may wish to included into the message. This has now been corrected.