Template:Semcon: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(→‎Arguments: Date parsed)
Line 15: Line 15:
*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
{{note|The dates in parameters ''proposed'', ''approved'' and ''deprecated'' have to be entered in format '''yyyy-mm-dd''', as they are parsed by [[Template:Date]]!}}


==Example==
==Example==

Revision as of 15:25, 16 May 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
🗒️ The dates in parameters proposed, approved and deprecated have to be entered in format yyyy-mm-dd, as they are parsed by Template:Date!


Example

{{semcon|Never put off until tomorrow what you can do today.|status=deprecated|proposed=2019-02-12|approved=2019-03-18|deprecated=2019-04-05}}

delivers

Private-cloud-icon.png Deprecated Semantic Constraint:
 
Never put off until tomorrow what you can do today.
 
Proposed on February 12th 2019
Approved on March 18th 2019
Deprecated on March 18th 2019
Deprecated semantic constraints may still be valid for older railML® versions!
{{{forum}}}
Please, recognize our guidelines on semantic constraints