On Mon, January 14, 2008 17:19, Michael Smethurst wrote: > In the case of classical music identifying the track played by ordinality > on the release is extremely useful. So a way to markup ordinality other > than as a list would be preferable
In the following, for "piece" read "piece", "sequence" or some other term: <foo class="item start-piece">Piece 1, part 1</foo> <foo class="item">Piece 1, part 2</foo> <foo class="item">Piece 1, part 3</foo> <foo class="item end-piece">Piece 1, part 4</foo> <foo class="item start-piece">Piece 2, part 1</foo> <foo class="item">Piece 2, part 2</foo> <foo class="item">Piece 2, part 3</foo> <foo class="item end-piece">Piece 2, part 4</foo> or: <foo class="piece"> <foo class="item">Piece 1, part 1</foo> <foo class="item">Piece 1, part 2</foo> <foo class="item">Piece 1, part 3</foo> <foo class="item">Piece 1, part 4</foo> </foo> <foo class="piece"> <foo class="item">Piece 2, part 1</foo> <foo class="item">Piece 2, part 2</foo> <foo class="item">Piece 2, part 3</foo> <foo class="item">Piece 2, part 4</foo> </foo> though the latter again causes problems in tables (unless a TBODY is used for each piece; which is arguably good practice). "Item" is an absolutely awful (and semantically-barren) name; it might be best to use "piece and "subpiece" or something like that, assuming that the piece's name is shown (unlike the above examples). Perhaps you have some real examples in mind? How any levels of sub-division are there? I have recently posted links to others' efforts to solve the problem of codifying the structure of disparate types of music: <http://tinyurl.com/2uval5> on the wiki. In particular, see: <http://oakroadsystems.com/genl/itunes.htm> -- Andy Mabbett ** via webmail ** _______________________________________________ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new