Property talk:P1647
Documentation
all resources related by this property are also related by that property
Description | all resources related by this property are also related that property. Implements rdfs:subPropertyOf. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Represents | subproperty (Q112037424) | ||||||||||||
Data type | Property | ||||||||||||
Domain | According to this template:
Wikidata property (Q18616576) - Wikidata:Glossary#Property
According to statements in the property:
When possible, data should only be stored as statementsWikidata property (Q18616576) | ||||||||||||
Allowed values | Other Wikidata property (Q18616576) - Wikidata:Glossary#Property (note: this should be moved to the property statements) | ||||||||||||
Example | According to this template:
According to statements in the property:
When possible, data should only be stored as statementsparent taxon (P171) → subclass of (P279) subproperty of (P1647) → related property (P1659) | ||||||||||||
See also | external superproperty (P2235) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P1647#Item P2302, search, SPARQL
|
What is the reason for the P1629 constraint?
[edit]I don't understand this constraint:
Property "Wikidata item of this property (P1629)" declared by target items of “subproperty of (P1647)”: If [item A] has this property with value [item B], [item B] is required to have property “Wikidata item of this property (P1629)”.
That is, I understand what it does (I believe), but I don't understand the reason. NisJørgensen (talk) 14:03, 25 July 2019 (UTC)
- @NisJørgensen: I removed such constraint. --Horcrux (talk) 18:17, 6 April 2024 (UTC)
incorrect claim in core of Wikidata ontology
[edit]I see the claim here that subproperty of (P1647) subproperty of (P1647) subclass of (P279).
Surely this is incorrect. But the real question is how such a core incorrect claim can have persisted since September 2019 without anyone noticing. Is there any way to protect the core items of the Wikidata ontology from bad changes? Is there nothing in Wikidata that would flag material changes to the core items of the Wikidata ontology? Peter F. Patel-Schneider (talk) 19:11, 24 July 2023 (UTC)
@Samoasambia: For what concerns this rollback, there are properties that are correctly violating the constraint, such as related property (P1659) or complementary property (P8882) (or Wikidata property example (P1855) itself), since they must be used on other properties, not on items.
So, if there is something to be fixed, it should be value-requires-statement constraint (Q21510864). Horcrux (talk) 15:11, 27 August 2024 (UTC)
- @Horcrux: Good point, I depreciated the constraint. I agree that it would be useful if value-requires-statement constraint (Q21510864) allowed multiple property values that could be satisfied if one of them is met. Samoasambia ✎ 06:23, 28 August 2024 (UTC)
- @Horcrux: I added a new complex constraint for property constraint (P2302) that looks for properties without any example statements. The results will show up here once the bot updates the page but you can already access it via the Query Service. Samoasambia ✎ 18:56, 29 August 2024 (UTC)