Wikidata:Property proposal/presentation template
presentation template / output template / value template
[edit]Originally proposed at Wikidata:Property proposal/Generic
| Description | template for displaying an item as a value in a Wikimedia project |
|---|---|
| Data type | Item |
| Allowed values | Wikimedia template (Q11266439) |
| Example 1 | Buenos Aires Stock Exchange (Q891560) → Template:Buenos Aires Stock Exchange (Q6731940) |
| Example 2 | Order of the Republic (Q4335955) → Q14153695 |
| Example 3 | United States of America (Q30) → Template:USA (Q5612638) |
| Example 4 | prose writer (Q12144794) → Template:Prosaist (Q15278141) |
| See also |
|
| Distinct-values constraint | yes |
Motivation
[edit]We currently have only one property for specifying that a template is associated with some item: topic's main template (P1424). According to the documentation, it should only be used for infoboxes and navigation templates, and it would be good to leave it that way (or maybe they should even be separated). But there is also a fundamentally different type of template. These are templates used to visually represent an entity. This can be a ticker template for a stock exchange or some image representation for an award or flag. Moreover, items are likely to have both a value for topic's main template (P1424) and this one. Therefore, I propose to create a new property that allows linking template items that can be used to render the item visually in Wikimedia projects. —putnik 11:23, 20 March 2021 (UTC)
Discussion
[edit]
Oppose All of these examples can be modelled using topic's main template (P1424), it does not have to be restricted to infoboxes or navboxes. If you want to specify the role of the template, you have the qualifier object of statement has role (P3831), with Wikimedia infobox template (Q19887878), Wikimedia navigational template (Q11753321), or any other value you want. Howewer, I think this is innecesary: these data are already (or must be) stored on the template items. --Tinker Bell ★ ♥ 22:14, 20 March 2021 (UTC)
- I totally agree that we can use the same property with qualifiers for many different purposes. But we can also not use it if it is not convenient. For example, instead of all properties with images, you could use only image (P18) with qualifiers, and this is also a possible approach. But for practical use, it is often more convenient to create multiple properties. So here, I propose to be guided by practical benefits and look back at real use. Perhaps someday all templates will have more specific values of instance of (P31) (I personally support and do a lot for this), and qualifiers will be filled in in the properties. But now the situation is very far from this, and if we rely only on qualifiers, we will not be able to effectively use these templates. And worse, once the property is filled with new template elements, it will also become less usable for infoboxes and navigation templates. —putnik 09:51, 25 March 2021 (UTC)
- Oppose per Tinker Bell. --Hannes Röst (talk) 14:17, 30 April 2021 (UTC)
Not done - no support for the proposal --DannyS712 (talk) 01:23, 2 January 2022 (UTC)
