Template:InheritAnnotationRef: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
No edit summary
Line 25: Line 25:
|constraints =
|constraints =
* {{Attr|ref}} {{RailMLType|tGenericRef}}, mandatory
* {{Attr|ref}} {{RailMLType|tGenericRef}}, mandatory
 
*{{attr|target}}: {{intro|2.5}}, specifies the target output of the passenger information (e.g. info for output in train or at the platform).
**{{enum|station}}: indicates that passenger info is to be output via the stationary info system at the platform/station.
**{{enum|train}}: indicates that passenger info is to be output via the onboard info system in the train.
*{{attr|priority}}: {{intro|2.5}}, specifies the priority of the announcements. if multiple announcements apply, the order in which they are played is determined by the priority (highest priority first).
* {{Attr|operatingPeriodRef}} {{RailMLType|tGenericRef}}, optional
* {{Attr|operatingPeriodRef}} {{RailMLType|tGenericRef}}, optional
One {{{parentLink|{{TT:Tag|connection}}}}} can have an unlimited number of {{{selfLink|{{TT:Tag|annotationRef|connection}}}}} elements. {{AddAnn|{{{constraints_en|}}}|{{{constraints_de|}}} }}
One {{{parentLink|{{TT:Tag|connection}}}}} can have an unlimited number of {{{selfLink|{{TT:Tag|annotationRef|connection}}}}} elements. {{AddAnn|{{{constraints_en|}}}|{{{constraints_de|}}} }}



Revision as of 16:01, 28 March 2022