IS:balise

From wiki.railML.org
Jump to: navigation, search

balise
 


Scheme description / Schemenbeschreibung / Description du schéma

Position of balise in the XML-Tree / Position von balise im XML-Baum / position de balise dans l’aborescence XML

Multiplicity / Anzahl / Multiplicité

[1..∞]

Semantics / Bedeutung / Sémantique

A <balise> defines a single balise and its attributes. A balise is an electronic beacon or transponder placed between the rails of a railway as part of an Automatic Train Protection (ATP) system. http://en.wikipedia.org/wiki/Balise (external link)

Attributes of balise / Attribute von balise / Attributs de balise

  • id: XML-file-wide unique, machine-interpretable identity, required for later referencing that element internally. For a detailed explanation see Dev:identities.
    XML-Datei-weit eindeutige, maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities.
  • code (introduced with version 2.1): This is a short string for typical, specific abbreviations, used in different systems with the same understanding.
  • name: This is a short name for the current item.
  • description: This is a more detailed description as addition to the short name. It shall allow a short overview or hints to the contents of this data set.
Birne.png Please be aware that this attribute is only intended to forward simple remarks/explanations from one end-user to another end-user. It is not to be used to contain computer-processable data, nor shall it be parsed by programmes in any way. In case of semantical overlaps or discrepancies to machine processable file contents, any machine processable contents have priority over possible human interpretable contents. However, the attribute may be used to transmit complementary details to machine processable parameters.

Bitte, berücksichtigen Sie, dass dieses Attribut nur für einfache Kommentare/Erklärungen von Endbenutzer zu Endbenutzer bestimmt ist. Es ist nicht für maschineninterpretierbare Daten gedacht und wird nicht geparst werden. Im Falle semantischer Überschneidungen oder Widersprüche zu maschinenlesbaren Inhalten wird diesen der Vorzug gegenüber durch Menschen lesbaren gegeben. Allerdings können durch Menschen lesbare Felder für Ergänzungen zu maschinenlesbaren verwendet werden.

  • xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
    This is used for defining name and description.
  • pos: This is the position on a track defined as distance from its start (trackBegin) regardless the "absolute mileage" in absPos.
    Das ist die Position des Elements auf einem Track i.S. der realen Entfernung zum trackBegin. Sie ist damit unabhängig von der mit absPos modellierten Strecken-Kilometrierung.
Note.png For an explanation of the differences between pos and abspos see <mileageChange>
  • absPos: This is the position on a track as absolute mileage/chainage.
    Das ist die Position des Elements im Referenzsystem der Strecken-Kilometrierung.
Note.png For an explanation of the differences between pos and abspos see <mileageChange>
  • absPosOffset (deprecated with version 2.1): The semantics of this attribute aren't very clear. It seems to be redundant to the definitions with mileageChanges in "overlapping regions".
  • dir: This defines the validity of <balise> along the track. Possible values are:
  • none: <balise> has no direction restriction.
  • up: This denotes the direction from the <trackBegin> to the <trackEnd> (increasing relative position values).
  • down: This goes opposite to up (decreasing relative position values).
  • both: <balise> is valid in both directions.
  • unknown: <balise> is restricted to a certain direction, but this direction is not known.
  • countryID: This is the ID number for each country. It is used to determine to which country a balise belongs.
  • groupID: balises and baliseGroups can be joined to groups. groupID is needed to determine if a balise belongs to a group and if yes, to which one.
  • linkingAccuracy
  • linkReactionAscending
  • linkReactionDescending
  • staticTelegram: the telegram coded to the balise; representation of the binary telegram shall be a hex string
  • ndx

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

  • id: xs:ID, required
    a string, starting with a letter (a..zA..Z) or an underscore (_),
    followed by a non-colonized and non-spaced string consisting of letters, digits, points (.), dashes (-) or underscores (_)
  • pos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); required; must be greater than or equal to zero, less than or equal to the track's length
  • absPos: xs:decimal, 6 fraction digits, length value measured in meter; optional
  • absPosOffset: xs:decimal, 6 fraction digits, length value measured in meter; optional
  • dir: xs:string, generic type for direction statements: enumeration up, down, unknown, none, both; optional
  • countryID optional, up to 1023 countries
  • groupID optional, up to 16383 groups
  • linkingAccuracy optional
  • linkReactionAscending optional
  • linkReactionDescending optional
  • staticTelegram xs:string with further constraints to allow only HEX string patterns [0-9a-fA-F]*, optional — (introduced with version 2.4): an arbitrary string consisting of hex digits from 0 to 9, a to f; not allowing white space, letters; no length restriction
  • ndx optional

Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.

Notes / Anmerkungen / Notes

Don't mix up groups of balises in the sense of baliseGroup with the groups defined by the groupIDs. A baliseGroup can also be part of a group of balise elements with a certain ID.

General information on positioning

Positive pos values describe the distance from the track's begin. The track length is derived from the pos value in <trackEnd>.

The absolute mileage refered to by absPos is usually found on technical drawings of the track layout or on mileage posts next to the track.

Open issues / Offene Punkte/Pedenzen / Questions ouvertes

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.