Template:Future: Difference between revisions
[checked revision] | [checked revision] |
No edit summary |
|||
Line 4: | Line 4: | ||
{|type="wikitable" border="0" | {|type="wikitable" border="0" | ||
|[[File:sunrise.png|50px]] | |[[File:sunrise.png|50px]] | ||
|{{#ifeq:{{{version}}}|{{current}}|This instance of [[Template:Future]] seems to be '''obsolete'''. Please check, if this {{{unit|article}}} contains information that is only | |{{#ifeq:{{{version}}}|{{current}}|This instance of [[Template:Future]] seems to be '''obsolete'''. Please check, if this {{{unit|article}}} contains information that is only valid for future {{rml}} versions. If this is not the case, feel free to remove this template. Don't forget to check [[:Category:Future]] if there are more obsolete instances.|This {{{unit|article}}} contains information that is only valid for a '''future {{rml}} version'''. The {{{unit|article}}} refers to version {{{version}}}, whereas the current {{rml}} version is {{current}}.}}{{#if:{{{user|}}}| {{{user}}}|}} | ||
|} | |} | ||
|} | |} |
Revision as of 14:14, 29 January 2018
Usage
This template can be used to mark articles with contents refering to future railML® versions. This is necessary because the claim of this wiki is to represent the current shema. Generally speaking, information on future versions should be removed, but especially just prior to a new release it can be too puristic to avoid any prospects.
To mark information on future versions include {{Template:Future}} into the source code. When the new version is published, please remember to check Category:Future and remove obsolete instances of this template.
Articles, where this template is included, are listed in Category:Future.
For other templates see Category:Template.
Options
This template has there named parameters.
The arguments are
- version: obligatory; the version to which the content refers
- unit: optional; the scope of the text on future versions: does it affect the complete article or only e.g. a section or paragraph? The defult is Article.
- user: Your signature. For convenience, use user=~~~~
Examples
Under version 2.3,
{{future|version=3.0}}
delivers
|
{{future|version=3.0|unit=section|user=~~~~}}
delivers
|
{{future|version=2.3|unit=section|user=~~~~}}
delivers
|