Property talk:P6186
Documentation
Wikimedia category that contains subcategories dedicated to specific instances of the said item
Data type | Item | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Example | explorer (Q11900058) → Category:Wikipedia categories named after explorers (Q7780950) short story (Q49084) → Category:Wikipedia categories named after short stories (Q20654614) volcano (Q8072) → Category:Wikipedia categories named after volcanoes (Q18013201) | |||||||||
See also | topic's main category (P910), related category (P7084) | |||||||||
Lists |
| |||||||||
Proposal discussion | Proposal discussion | |||||||||
Current uses |
| |||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P6186#Value type Q30432511, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6186#Entity types
List of violations of this constraint: Database reports/Constraint violations/P6186#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6186#Item P279, search, SPARQL
The object is not "eponymous"[edit]
@Thierry Caro: Despite I believe this property is pretty useful, I think the chosen name is not correct for its purpose. Category:Victor Hugo (Q7367470) is an eponymous category, while Category:Wikipedia categories named after explorers (Q7780950) is something quite different. --Horcrux (talk) 13:10, 9 December 2018 (UTC)
- @Horcrux: This comes from the name of the mother category on the English Wikipedia, Category:Eponymous categories. Feel free to change the label if this is really an issue. I would go for
Category for categories of instances
or something similar. Thierry Caro (talk) 13:24, 9 December 2018 (UTC)- @Thierry Caro: The children of en:Category:Eponymous categories are not eponymous categories but containers of eponymous categories. See also en:WP:EPONYMOUS.
- I think "container of eponymous categories" (with alias "eponymous categories", in the plural) could be a good choice. --Horcrux (talk) 16:25, 9 December 2018 (UTC)
- I agree that "container of eponymous categories" is more precise; maybe "eponymous category" could remain as an alias. --Epìdosis 09:04, 10 December 2018 (UTC)
Type constraint[edit]
@Mormegil: I added the type constraint because this didn't seem like a property that could apply to any arbitrary item (e.g. not State Bank of India, Pedanandipadu branch (Q65958099) or Unusual immunoglobulin and T-cell receptor gene rearrangement patterns in acute lymphoblastic leukemias (Q33681386), as two random examples) and I used role (Q214339) for the value because most of the existing items fit that. I agree that this is a tricky constraint to figure out the right value for, and I'd be glad for suggestions if you have any. I'm also fine leaving the constraint off for now (or adding it merely as a suggestion constraint). JesseW (talk) 16:30, 14 September 2022 (UTC)
- You’re right it makes sense for the property to have a similar constraint. However, as I mentioned in the comment, I would prima facie expect this property be limited to any class. Because I think any class of entities can have a metacategory containing categories for the individual items of the class. I.e. the constraint should IMHO be category for eponymous categories (P6186)property constraint (P2302)item-requires-statement constraint (Q21503247)
property (P2306)subclass of (P279) (which both your examples would correctly fail, being just instances, not classes, while my specific case which lead me here, news leak (Q21694520), would correctly pass). Does that make sense from your point of view? --Mormegil (talk) 09:30, 15 September 2022 (UTC) - Yep, that looks like a great solution! Please add it (or I will in a few days). JesseW (talk) 13:07, 15 September 2022 (UTC)
- Done --Mormegil (talk) 13:23, 15 September 2022 (UTC)
- Yep, that looks like a great solution! Please add it (or I will in a few days). JesseW (talk) 13:07, 15 September 2022 (UTC)