Template:Semcon: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
Line 12: Line 12:
*1: The constraint.
*1: The constraint.
*status: The status of the semantic constraint: ''proposed'', ''approved'' or ''deprecated''
*status: The status of the semantic constraint: ''proposed'', ''approved'' or ''deprecated''
proposed: The date of proposal, obligatory
*proposed: The date of proposal, obligatory
approved: The approvement date, obligatory if status is either approved or deprecated
*approved: The approvement date, obligatory if status is either approved or deprecated
deprecated: The deprecation date, obligatory if status=deprecated
*deprecated: The deprecation date, obligatory if status=deprecated


==Example==
==Example==

Revision as of 17:13, 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.|proposed=monday|approved=thursday}}

delivers Obligatory argument status missing