Template:Semcon: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
*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: | *{{anchor|forum}}forum: Either a link to the forum entry, where the constraint was discussed or a call of [[template:ticket]]. Please, don't introduce semantic constraints (not even proposed ones) without a former discussion. If the value of ''forum'' is anything other than a link to the {{rml}} forum or a call of [[template:ticket]], 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 |
Revision as of 12:13, 14 March 2022
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: Either a link to the forum entry, where the constraint was discussed or a call of template:ticket. Please, don't introduce semantic constraints (not even proposed ones) without a former discussion. If the value of forum is anything other than a link to the railML® forum or a call of template:ticket, 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
|
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
|
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
|
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
|