Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

relation of release/release event to catalogue number and label #6

Open
zazi opened this issue Oct 13, 2011 · 0 comments
Open

relation of release/release event to catalogue number and label #6

zazi opened this issue Oct 13, 2011 · 0 comments

Comments

@zazi
Copy link
Member

zazi commented Oct 13, 2011

While dealing with this issue at the moment, I raised this agonized question one more time at the MBZ dev IRC channel:

<zazi> one release can different catalog numbers 
<zazi> or
<zazi> a catalog number can have different releases
<zazi> ?
<ocharles> A release has multiple release labels (label/cat no pairs)
<reosarevok> zazi: all the labels and catalog numbers for a single release are supposed to be related to the same country-date (that is, the actual CD or whatever was published as a cooperation by two or more labels, or the label gave it several catalog numbers)
<reosarevok> (also, a catalog number can be in different releases, for example if the label gave the same catalog number to the CD and vinyl editions)
<reosarevok> (but AFAIK it doesn't link them in any way in the database, it just means they happen to have the same info in that field)
<zazi> yep, that's what I thought as well

My conclusion is that we should move the domain of mo:catalogue_number and mo:label to mo:ReleaseEvent instead of mo:Release. Any opinions?

See also [1] for an earlier discussion at the MO mailing list about this issue.

[1] http://groups.google.com/group/music-ontology-specification-group/browse_thread/thread/67b726c9c30e0989/9f0f54d3d59840bc?lnk=gst&q=catalgue+number#9f0f54d3d59840bc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant