Property talk:P2550

Allowed entity types are Wikibase MediaInfo (Q59712033), Wikibase item (Q29934200): the property may only be used on a certain entity type (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#Entity types

Scope is as main value (Q54828448): the property must be used by specified way only (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#Scope, SPARQL

Value type “play (Q25379), dramatico-musical work (Q58483083), musical work/composition (Q105543609), poem (Q5185279), choreographic work (Q58483088), literary work (Q7725634), lecture (Q603773), oration (Q861911), performance artwork (Q22672348)”: This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value play (Q25379), dramatico-musical work (Q58483083), musical work/composition (Q105543609), poem (Q5185279), choreographic work (Q58483088), literary work (Q7725634), lecture (Q603773), oration (Q861911), performance artwork (Q22672348) (or a subclass thereof). (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#Value type Q25379, Q58483083, Q105543609, Q5185279, Q58483088, Q7725634, Q603773, Q861911, Q22672348, 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, SPARQL

Conflicts with “instance of (P31): audio track (Q7302866)”: 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

This property is being used by: hy:Կաղապար:Տեղեկաքարտ Երաժշտական ստեղծագործություն Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Hello,

I find usefull to create the inverse property of recording or performance of (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 . 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 (P2550). Fjjulien (talk) 02:54, 3 December 2021 (UTC)[reply]

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]