Template:Semcon: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
Line 2: Line 2:
|proposed={{semconProposed|{{{1}}}|{{{proposed}}}}}
|proposed={{semconProposed|{{{1}}}|{{{proposed}}}}}
|approved={{semconApproved|{{{1}}}|{{{proposed}}}|{{{approved}}}}}
|approved={{semconApproved|{{{1}}}|{{{proposed}}}|{{{approved}}}}}
|deprecated={{semconApproved|{{{1}}}|{{{proposed}}}|{{{approved}}}|{{{deprecated}}}}}
|deprecated={{semconDeprecated|{{{1}}}|{{{proposed}}}|{{{approved}}}|{{{deprecated}}}}}
|#default='''Obligatory argument ''status'' missing'''}}</includeonly><noinclude>
|#default='''Obligatory argument ''status'' missing'''}}</includeonly><noinclude>
==Usage==
==Usage==

Revision as of 17:17, 27 March 2019

Usage

This template is designated for semantic constraints. It presents them in a standardized way and provides listing in Category:Semantic constraints.

Please, don't forget to hint at semantic constraints with template:semconHint!

Arguments

The template has one unnamed obligatory argument and four named arguments:

  • 1: The constraint.
  • status: The status of the semantic constraint: proposed, approved or deprecated
  • proposed: The date of proposal, obligatory
  • approved: The approvement date, obligatory if status is either approved or deprecated
  • deprecated: The deprecation date, obligatory if status=deprecated

Example

{{semcon|Never put off until tomorrow what you can do today.|status=approved|proposed=monday|approved=thursday}}

delivers Obligatory argument status missing