Template:Semcon: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
No edit summary
Line 1: Line 1:
<includeonly>{{#switch:status
<includeonly>{{#switch:{{{status}}}
|proposed={{semconProposed|{{{1}}}|{{{proposed}}}}}
|proposed={{semconProposed|{{{1}}}|{{{proposed}}}}}
|approved={{semconApproved|{{{1}}}|{{{proposed}}}|{{{approved}}}}}
|approved={{semconApproved|{{{1}}}|{{{proposed}}}|{{{approved}}}}}

Revision as of 17:30, 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

Private-cloud-icon.png Semantic Constraint:
 
Never put off until tomorrow what you can do today.
 
Proposed on monday
Approved on thursday
{{{forum}}}
Please, recognize our guidelines on semantic constraints