Wikidata:Property proposal/release of
release of
[edit]Originally proposed at Wikidata:Property proposal/Creative work
| Description | the music release this is a release of |
|---|---|
| Represents | musical release (Q2031291) |
| Data type | Item |
| Domain | item |
| Allowed values | subclass of (P279) musical release (Q2031291) |
| Example 1 | Taste of Love (Q107051335) → Taste of Love (Q106797774) |
| Example 2 | Taste of Love (Taste Version) (Q107050654) → Taste of Love (Q106797774) |
| Example 3 | Taste of Love (Fallen Version) (Q107050890) → Taste of Love (Q106797774) |
| Source | https://schema.org/releaseOf https://musicbrainz.org/doc/Release |
| Planned use | replace music releases that use edition or translation of (P629) with this property and add new releases |
| Robot and gadget jobs | maybe replace edition or translation of (P629) with this |
| See also | edition or translation of (P629) |
| Wikidata project | Wikidata:WikiProject Music |
Motivation
[edit]Using edition or translation of (P629) (as we do currently) doesn't really make sense for music releases since music releases are always called "releases" and not "editions". edition or translation of (P629) is also book-focused. Having constraints for music releases is also a focus of creating this property.
Having a dedicated release property would also allow for synonymous linkage between MusicBrainz entities and their Release group -> Release data structure, something we're trying to replicate on Wikidata.
An inverse property called "has release" could also be usefully created.
WikiProject Music has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Lectrician1 (talk) 02:09, 7 July 2021 (UTC)
Discussion
[edit]
Neutral on this property; 
Oppose on the "has release" property. Mahir256 (talk) 16:25, 7 July 2021 (UTC)
Comment I’m not opposing this, but I found the rationale a bit short: if it’s just a matter of the music lingo using “release”, then we could just rename “edition or translation of” to “edition, translation, or release of” − sure, it becomes a bit the kitchen sink, but how much of a problem is that really?
Also, just a note that if that property would go ahead, then we might end up using it for video games, if we ever get around defining a multi-layered data model with separate items for platform-realizations, local releases etc. Of course, creating this property should not be blocked on WD:VG deciding how we might want to use it, but putting it on the radar that the scope is likely wider than just music. Jean-Fred (talk) 20:09, 7 July 2021 (UTC)- @Jean-Frédéric: Actually, now that I look at the Wikiproject Books data model and your video games data model, it seems like we're all dealing with the same thing.
- We need a way to establish a relationship between the "release group" for music, "work" for books, "video game" for video games and their corresponding "releases", "editions", and "releases".
- I think I might go forward with not proposing this property and instead:
- Solving the current translation of debate
- Proposing renaming "edition of"/"edition or translation of" to "edition/version/release of" Lectrician1 (talk) 01:15, 21 July 2021 (UTC)
- Neutral I don't know much about music topics, but as Jean-Frédéric said, if the relationship are the same, we don't need to create two properties only because the terms used are different. Oppose 'has release' --Tinker Bell ★ ♥ 18:23, 9 July 2021 (UTC)
Support I'm very much in favor of a dedicated property, but oppose the inverse like the others before me. P629 currently requires us to use the inverse property P747, which is exactly what we're trying to move away from. Having a dedicated property will make it much easier to set up clear, sensible, constraints that are realistic and manageable. Moebeus (talk) 17:43, 11 July 2021 (UTC)
@Jean-Frédéric @Mahir256 @Tinker Bell after talking with User:Moebeus, it seems like a major reason for creating this property is the possibility of music-related constraints for the property.
edition or translation of (P629) currently "relies" on the version, edition or translation (Q3331189) class for relationships and we don't use that class for music releases. There are also other reasons, such as not wanting to adopt Wikiproject Book's FRBR-based data model since it doesn't work well for music release relationships which can sometimes be many layers deep compared with work-expression-manifestation.
With this in, mind would you all consider supporting "release of"? Lectrician1 (talk) 14:30, 23 August 2021 (UTC)
- Support--Trade (talk) 17:39, 23 August 2021 (UTC)
- @Lectrician1, Trade, Jean-Frédéric, Moebeus, Tinker Bell, Mahir256:
WikiProject Music has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. 
Done as release of (P9831). UWashPrincipalCataloger (talk) 07:43, 27 August 2021 (UTC)
