Jump to content

Property talk:P2550

Add topic
From Wikidata

Documentation

recording or performance of musical work/composition
item is a recording or release of this composition
Descriptionl'entité est un enregistrement ou une représentation de cette composition (fr) – (Please translate this into English.)
Representsaudio recording (Q3302947)
Data typeItem
Domainitems with instance of (P31) of musical release (Q2031291) or its subclasses (note: this should be moved to the property statements)
Allowed valuesitems with instance of (P31) of composed musical work (Q207628) or musical form (Q862597) or their subclasses (note: this should be moved to the property statements)
ExampleOb-La-Di, Ob-La-Da (Q58885066)Ob-La-Di, Ob-La-Da (Q1135588)
Enter Sandman (Q66057646)Enter Sandman (Q672508)
See alsoedition or translation of (P629), manifestation of (P1557), performer (P175), meeting of (P13188)
Lists
Proposal discussionProposal discussion
Current uses
Total30,094
Main statement29,99999.7% of uses
Qualifier910.3% of uses
Reference4<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Allowed entity types are Wikibase MediaInfo (Q59712033), Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
List of violations of this constraint: Database reports/Constraint violations/P2550#Entity types, hourly updated report
Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2550#Scope, hourly updated report, SPARQL
Conflicts with “instance of (P31): musical release (Q2031291), release group (Q108346082), musical work/composition (Q105543609), human (Q5), album (Q482994): this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2550#Conflicts with P31, search, SPARQL
Conflicts with “composer (P86): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2550#Conflicts with P86, hourly updated report, search, SPARQL
Conflicts with “lyricist (P676): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2550#Conflicts with P676, hourly updated report, search, SPARQL
Conflicts with “music created for (P9899): this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2550#Conflicts with P9899, search, SPARQL


interess for the property inverse?

[edit]

Hello,

I find usefull to create the inverse property of recording or performance of musical work/composition (P2550). The label is already existing recording/performed version (Q67006033).

What do you think about?

Notified participants of WikiProject Performing arts --SAPA bdc (talk) 12:16, 4 November 2021 (UTC)Reply

see also discussion on the bitrot (in french). --SAPA bdc (talk) 12:43, 4 November 2021 (UTC)Reply
Hello SAPA bdc Hello. In RDF, a triple reads in both directions. Therefore a property normally doesn't need an inverse property; it only needs an inverse label so that humans can easily read the triple in reverse direction. The human readable interface of Wikidata however doesn't make inverse statements readily visible. One has to clink on "What links here", in the tools menu, or open up the "Derived statements" at the bottom of the item. Or else these inverse triples can be retrieve via the query service.
This being said, in Wikidata, certain important properties do have inverse properties. The most notorious one is part of (P361) and its inverse property has part(s) (P527). This relationship particular is structurally quite fundamental, so I presume this inverse property was created to ensure the relationship would be visible to human readers on both ends of the triple.
Inverse properties should however generally be avoided, because they multiply the editing effort by two : a given triple has to be populated twice. Therefore, I would not recommend creating an inverse property for recording or performance of musical work/composition (P2550). Fjjulien (talk) 02:54, 3 December 2021 (UTC)Reply

Conflicts with "“instance of (P31): release (Q2031291)" ?

[edit]

Hi. I don't really understand this constraint: Conflicts with "instance of (P31): release (Q2031291)". Why is release(Q2031291) in conflict when all it's subclasses are okay? The description reads, "item is a recording or release of this composition" The Domain says, "items with instance of (P31) of release (Q2031291) or its subclasses"

I'm really confused. But I'm also pretty inexperienced in reading these property constraints. Thanks --Metadatum (talk) 01:10, 23 April 2022 (UTC)Reply