Bitmap's relationships script does a request like http://musicbrainz.org/ws/2/release/ab156a4c-060e-366c-8e68-3c9dc94e51b4?inc=recordings+recording-level-rels+work-level-rels+label-rels+url-rels+work-rels
This returns (or at least used to, see MBS-4792) nearly all the information about the work - the name, disambiguation comment, ISWCs and relationships, but not the language.
If I get it right no property of works is returned (also not the type), just the relations. E.g. this is the request Picard makes:
And this is the XML request for the work of the first track:
What would be needed in my opinion is a "works" include parameter for releases, e.g.:
This would be very useful, because PICARD-242 could be implemented then.
EDIT: The only property returned is the title.
Hm. I'm not sure I agree. We used to return all the information about the work except for the type. I don't know why that was the case and since I never use that field, I never even noticed. Since we are (or rather, given that we broke it, should be) already returning almost everything about the work (and would have to continue doing so for backwards compatibility), it seems overkill to me to add a new option just to add the type and language.
We return all information inside the work table, without joining any other tables. I'm not really sure what to do here, the options are:
I agree both options have pros and cons... so why not control it with `inc`-options?
A decision has been reached, work language will always be present.
In review with http://codereview.musicbrainz.org/r/2126/