Template:Tag status values
Jump to navigation
Jump to search
approved
: the key or tag has successfully completed the approval processde facto
: the tag is in widespread use, and while it was not approved in a proposal process, it has a widespread acceptance among mappers (2)deprecated
: deprecated tags that are discouraged from being useddiscardable
: tags that are so useless that editors remove them automatically, for example Tag:odbl=cleanimported
is used for a tag which was added from an external databasein use
: the key or tag is in use (2)obsolete
: a key or tag which is no longer found in the databaseproposed
: the key or tag has been proposed to be used (but not yetapproved
) and usage of this tagging is minimal (1)undefined
orvoting
: the key or tag is currently being voted on as part of the approval process
Notes:
- By "usage of this tagging is minimal" it is meant that there is minimal usage world wide, for example a tag that has been used 50 times. Note that depending on the tag low usage may be normal, generally properties will have a much higher usage than specific features.
in use
andde facto
can be used for tags that are in use but have proposal in some stage that was not approved. For example, a heavily used tag with rejected proposal can havede facto
status.inuse
was sometimes applied insteadin use
, the same withdefacto
instead ofde facto
. It is highly preferable to avoid this.
This documentation is transcluded from Template:Tag status values/doc. (Edit | history)
Note to editors: Please don't categorize this template by editing it directly. Instead, place the category in its documentation page, in its "includeonly" section.
Note to editors: Please don't categorize this template by editing it directly. Instead, place the category in its documentation page, in its "includeonly" section.
Usage
Add this template without parameters {{Tag status values}}
See also
- Template:Description and Template:StatusLang and Template:MultipleTaggingDescription where status values are parsed: it should be kept in sync with this documentation page
- Template:KeyDescription/doc and Template:ValueDescription/doc where there are ANOTHER repetitions of documentation, though it is not mentioning all values which are less preferred
- Category:Feature descriptions with incorrect status value where pages using invalid values should be listed