| Extending railML: multiple domain specific Extensions for the same Elemen [message #4019] |
Tue, 26 May 2026 11:35  |
Silvan Gruber
Messages: 11
Registered: July 2024
|
Junior Member |
|
|
Dear railML-community,
The SBB's signaling systems are divided into various subsystems (controllers, interlocking, RadioBlockCentre, balises, object controllers, etc.) from different suppliers. The SBB provides the high-level engineering data for these subsystems in railML format.
For the engineering of these subsystems, there is a need to extend the content represented in railML with subsystem-specific information to ensure unambiguous engineering at the supplier's site. Since this information cannot be represented using the standard railML 3.3, it is necessary to extend the railML schema for the subsystems according to https://wiki3.railml.org/wiki/Dev:Extending_railML. It is important to note that the subsystem-specific content is only valid for a single subsystem and is not relevant for other subsystems. (see figure below)
The following requirements must be considered:
- A railML dataset should be valid for all subsystems in its core.
- The basic railML structure remains unchanged.
- A standard railML element can be extended with multiple domain-specific content elements
- Extensions that are valid for multiple subsystems must be defined at a higher level.
- railML base types are extended according to Dev:Using xsi:type railML 3 Wiki.
- Subsystem-specific extensions should be able to be modified independently.
- Extensions should be integrated into the railML datasets being exchanged.
- The specific extensions should only describe in detail objects that are included in the railML standard.
A solution has been proposed by railML.org and SBB, which is currently being further developed and documented. Results and documentation will be attached to this post.
Best regards,
Silvan Gruber
[Updated on: Tue, 26 May 2026 11:39] Report message to a moderator |
|
|
|
|
|
Members
Search
Help
Login
Home
