Since Google actively supports the Music microdata structure, I would like to implement this on a site that publishes music mixtapes.
In context of this website, music mixes are usually 60 minute compilations of music, weaved together in a seamless fashion, much like the experience you'd get when going to an Electronic Dance Music festival.
Problem with the MusicRecording schema
The format of the website doesn't match this microdata structure closely enough. For example, Google Webmasters indicates that my submitted microdata is missing the
startDate properties. I have no desire of fixing these errors because they do not actually befit my content.
Alternative microdata structures
The main problem with alternative schemas is that I haven't seen official recognition by Google. Other problems are:
The expected schema for content that is delivered through WordPress, the software on which the website runs. While content can be considered a blog post, its contents are usually little more than a blockquote from the mix artist, and a tracklist for the music used in the mix.
While supported by Google, my content doesn't actually review the mix. It provides information about it. At best, my visitors' comments could be considered mini-reviews, but I have already structured them as Comments.
The main issue with this schema is that it's supposedly used inside another schema as a complement. I don't think it's a good solution to build my entire page's content around MediaObjects.
While more accurate than MediaObject, it faces the same limitations.
What is a suitable microdata structure for music mixes?
What I need seems to exist in schemas, but I only a little bit from each of them. Ideally, a schema that is right for me, would include the following microdata properties:
- Name of artist who created the mix compilation (may be a sub schema, for instance a Person or PerformingGroup)
- Name of the mix compilation
- Artwork of the mix compilation
- List of musical works incorporated in the mix compilation, in order of appearance.
- Duration of mix compilation
- URL to audio file: the actual mix compilation
- Date of publishing
- Audio format and encoding (for example MP3)
- Comments about this content (may be in sub schema, for instance Comment)
Perhaps someone could produce a example of a combination of schemas to include all required properties that Google Webmaster could throw errors on. I'm kind of lost at this point which schema is best for my content.