Template:Semcon: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
<includeonly>{{anchor|id}}{{#switch:{{{status}}}
<includeonly>{{anchor|{{{id}}}}}{{#switch:{{{status}}}
|proposed={{semconProposed|{{{1}}}|{{date|{{{proposed|'''FIXME'''}}}}}|id={{{id|}}}}}
|proposed={{semconProposed|{{{1}}}|{{date|{{{proposed|{{FIXME}}}}}}}|id={{{id|}}}|forum={{{forum|{{fixme}}}}}}}
|approved={{semconApproved|{{{1}}}|{{date|{{{proposed|'''FIXME'''}}}}}|{{date|{{{approved|'''FIXME'''}}}}}|id={{{id|}}}}}
|approved={{semconApproved|{{{1}}}|{{date|{{{proposed|{{FIXME}}}}}}}|{{date|{{{approved|{{FIXME}}}}}}}|id={{{id|}}}|forum={{{forum|{{fixme}}}}}}}
|deprecated={{semconDeprecated|{{{1}}}|{{date|{{{proposed|'''FIXME'''}}}}}|{{date|{{{approved|'''FIXME'''}}}}}|{{date|{{{deprecated|'''FIXME'''}}}}}|id={{{id|}}}}}
|deprecated={{semconDeprecated|{{{1}}}|{{date|{{{proposed|{{FIXME}}}}}}}|{{date|{{{approved|{{FIXME}}}}}}}|{{date|{{{deprecated|{{FIXME}}}}}}}|id={{{id|}}}|forum={{{forum|{{fixme}}}}}}}
|#default='''Obligatory argument ''status'' missing'''}}[[category:allSemcons]]</includeonly><noinclude>
|#default='''Obligatory argument ''status'' missing'''}}[[category:allSemcons]]</includeonly><noinclude>
==Usage==
==Usage==
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''
*id: a unique designator for the respective semantic constraint with the rule "AA:NNN" where AA is the abbreviation of the subscheme (e.g. TT for timetable, IL for interlocking, ...) and NNN a three-digit, ascending and unique number  
*id: a unique designator for the respective semantic constraint with the rule "AA:NNN" where AA is the abbreviation of the subscheme (e.g. TT for timetable, IL for interlocking, ...) and NNN a three-digit, ascending and unique number
*{{anchor|forum}}forum: Link to the forum entry, where the semantic constraint was proposed. Please, don't introduce semantic constraints (not even proposed ones) without former discussion. If the value of ''forum'' is anything other than a link to the {{rml}} forum, an error message will appear.
*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
Line 20: Line 21:
==Example==
==Example==
===Proposed semantic contraint===
===Proposed semantic contraint===
<pre>{{semcon|All work and no play makes Jack a dull boy.|status=proposed|proposed=1980-10-16|id=AA:nnn}}</pre>
<pre>{{semcon|All work and no play makes Jack a dull boy.|status=proposed|proposed=1980-10-16|id=AA:nnn|forum=https://www.railml.org/forum/index.php?t=msg&th=704&start=0&}}</pre>
delivers
delivers
{{semcon|All work and no play makes Jack a dull boy.|status=proposed|proposed=1980-10-16|id=AA:nnn}}
{{semcon|All work and no play makes Jack a dull boy.|status=proposed|proposed=1980-10-16|id=AA:nnn}}

Revision as of 08:32, 7 April 2020

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
  • id: a unique designator for the respective semantic constraint with the rule "AA:NNN" where AA is the abbreviation of the subscheme (e.g. TT for timetable, IL for interlocking, ...) and NNN a three-digit, ascending and unique number
  • forum: Link to the forum entry, where the semantic constraint was proposed. Please, don't introduce semantic constraints (not even proposed ones) without former discussion. If the value of forum is anything other than a link to the railML® forum, an error message will appear.
  • 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

Proposed semantic contraint

{{semcon|All work and no play makes Jack a dull boy.|status=proposed|proposed=1980-10-16|id=AA:nnn|forum=https://www.railml.org/forum/index.php?t=msg&th=704&start=0&}}

delivers

Private-cloud-icon.png Proposed Semantic Constraint "AA:nnn":
 
All work and no play makes Jack a dull boy.
 
Proposed on October 16th 1980
FIXME
Please, recognize our guidelines on semantic constraints

Approved semantic contraint

{{semcon|People who live in glass houses shouldn't throw stones.<br>{{Deu|Wer im Glashaus sitzt, soll nicht mit Steinen werfen.}}|status=approved|proposed=2019-06-04|approved=2019-06-05|id=AA:nnn}}

delivers

Private-cloud-icon.png Semantic Constraint "AA:nnn":
 
People who live in glass houses shouldn't throw stones.
Wer im Glashaus sitzt, soll nicht mit Steinen werfen.
 
Proposed on June 04th 2019
Approved on June 05th 2019
FIXME
Please, recognize our guidelines on semantic constraints

Deprecated semantic contraint

{{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|id=AA:nnn}}

delivers

Private-cloud-icon.png Deprecated Semantic Constraint "AA:nnn":
 
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!
FIXME
Please, recognize our guidelines on semantic constraints