Check multiple <credit> elements with various <credit-type> children (also testing the case without such a child and having two). There is also a <defaults> block to properly set up (quite small) page dimensions and a ‘tenth’ value, making the ‘default-x’ and ‘default-y’ attributes of <credit-words> children meaningful. The following <credit> elements are present, with the given <credit-type> type. – ‘page number’ (two <credit> elements, one at the top left for page ‘2’ and another one at the top right for page ‘2a’ using attribute ‘page="2"’; valign: top). – ‘rights’ (at the bottom; halign: center, justify: right, valign: bottom). – ‘title’ (two <credit-words> elements, attributes only set for the first one, almost at the top; justify: center, valign: middle, enclosure: rectangle). – No <credit-type> element (below the title; halign: center, valign: middle). – Two <credit-type> elements (types ‘foo’ and ‘bar’, at the top; justify: center, valign: top, font-stype: italic). – ‘composer’ (below the type-less element; justify: right, valign: middle). – ‘lyricist’ (below the type-less element; valign: middle). There are no metadata elements. Measure 1 contains <print blank-page="1"/> to make the music start on page 2 (i.e., all <credit> elements in this test go to page 1). Chances are high that an application ignores all <credit> elements, using only metadata to derive titles, subtitles, and more. 6.35 40 660 860 page number 2 page number 2a rights The copyright comes here. title The Title A subtitle without a type foo bar Two types (foo + bar) composer The Composer lyricist The Lyricist MusicXML Part 4 1 whole light-heavy