TT:passengerTextInfo

From railML 3 Wiki
Revision as of 21:57, 25 April 2022 by RailML Coord Documentation (talk | contribs) (Created page TT:passengerTextInfo using XSD2MediaWiki Converter 1.0.6)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element TT:passengerTextInfo of railML® version 3.2
Documentation A passenger text info is an additional information that is provided for a train that is usually used by passenger information systems, either onboard the train or at the station. It can take the form of multilingual texts, pictures or symbols.
Subschema timetable
Parents* passengerTextInfos
Children mediaCategories (0..1), name (0..*), text (0..*)
Attributes:
  • type: Indicates the type of passenger info resource is encoded with this element. (optional; xs:string)
Possible values:
  • image: Indicates that the passenger text info takes the form of an image
  • symbol: Indicates that the element is a symbol
  • text: Indicates that the element is text based.,

  • URI: Can be used to refer to a resources that is available at the provided URI (optional; xs:anyURI),

  • id: unique identifier (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.


Changes 3.1→3.2

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues