| new track data types and a common question [message #75] |
Tue, 11 May 2004 07:24 |
Heidrun.Jost
Messages: 5
Registered: April 2004
|
Junior Member |
|
|
Hello,
the UNISIG standardization defines the following track condition
functions additionally to the present track data types in RailML:
- airTightness
- stoppingNotPermitted
- switchOffBaliseTransmission
- radioHole
- switchOffRegenerativeBrake
- switchOffEddyCurrentBrake
- switchOffMagneticShoeBrake
Additionally I need for customer request the track condition:
- slipperyTrackZone
Common question:
Is it better to define these track zone or to define a user
defined data field with arbitrary content
for project specific enhancements? I think,
each use of RailML will have specific parts. Either all
customer requirements are part of RailML or I must have
an additional XML file with customer specific parts. An
additional file is a bad solution.
If all customer requirements are part of RailML is it better
to have additional specific elements or a "dummy" element?
Best regards,
Heidrun Jost
|
|
|
|
Members
Search
Help
Login
Home
