Template talk:KeyDescription
Contents |
Proposed reuse for Machine-readable Map Feature list
There is a group working on a Machine-readable Map Feature list. In order to automatically harvest information about keys (which we call tag-defs) from the Wiki, this template should be slightly modified. —Preceding unsigned comment added by Gubaer (talk • contribs) 19:23, 21 December 2008
Proposed new arguments
- displayName (optional): a display name for the key in the language given by lang. Will be used by interactive applications for drop-down lists, menu entries, etc.
- onRelation (optional): whether this key can be used on relations either yes (default) or no
- status (optional): the status of this key in it's life-cycle (similar to status in the template Template:ValueDescription). Either proposed, rejected, accepted (default) or deprecated. —Preceding unsigned comment added by Gubaer (talk • contribs) 19:32, 21 December 2008
Proposed changed arguments
- groups (optional): a comma separated list of groups this key belongs to. Groups should be declared with a new template Template:GroupRef. Example:
groups={{GroupRef|name=naming|lang=en}}, {{GroupRef|name=non-physical|lang=en}}
—Preceding unsigned comment added by Gubaer (talk • contribs) 19:29, 21 December 2008
- Google definition: Perhaps use Wikipedia, instead of Google? —Preceding unsigned comment added by Acrosscanadatrails (talk • contribs) 13:12, 3 February 2009
Proposed expansion of the template
The expansion of the template should include a reference to the category <lang>:Category:Keys. Example:
[[Category:en:Keys]]—Preceding unsigned comment added by Gubaer (talk • contribs) 19:40, 21 December 2008
- probably [[Category:EN:Keys]] --dr&mx 20:07, 28 February 2012 (UTC)
Transition
New and changed arguments are optional. They shouldn't brake existing uses of the template. Neither does the declaration of a category.
We therefore suggest
- update the template
- adjust wiki pages (add arguments for the new parameters) step by step —Preceding unsigned comment added by Gubaer (talk • contribs) 19:40, 21 December 2008
Add a Proposal link
Hi, would it be a good idea to add a backlink to the proposal of a feature? Sometimes it is a very detailed help and gives further informations for usage, even on start of the feature --!i! 10:44, 17 August 2010 (BST)
Proposal - parameter - replaces
It might be useful to include a parameter which inidicates whether a key replaces another key; this would decrease the incidence of using "obsolete" keys. Example, see Key:power output, which refers to Key:power rating . . . which in turn redirects to Key:generator:output. --Ceyockey 13:17, 24 November 2010 (UTC)
- well, i saw your comment by chance (actually by using "What links here") when reorganising some power keys ... sorry for destroying your example ;-) (I won't change the links here, though) -- Schusch 23:38, 24 November 2010 (UTC)
Proposal - value interpretation
I think it would be really useful if the description also included information about the scale type and the default unit of the value. This would simplify automatic conversion of values (e.g. for people who prefer inches and feet instead of cm and m).
Examples (I think that's the easiest to explain what I suggest):
| key | scaleType | defaultUnit |
|---|---|---|
| width | number | m |
| voltage | number | V |
| wires | count | |
| population | count | inhabitants |
| lanes | count | |
| ele | number | m |
| include | number | % |
| maxweight | number | t |
| maxspeed | number | km/h |
| website | link | http:// |
| link | mailto: | |
| name | text | |
| highway | list | |
| amenity | list | |
| start_date | date |
Therefore valid scales could be 'number', 'count', 'link', 'text' (maybe we should distinguish between texts which "can" be translated like "name" and those which can't? are there any?), 'list' (for keys like highway, amenity, landuse, ...), 'date', etc.
What do you think? -- Skunk 15:36, 17 October 2011 (BST)
