| Re: [RailML3] Renaming Track into UsagePattern [message #2505 is a reply to message #2504] |
Fri, 24 July 2020 18:41  |
Stefan Wegele
Messages: 4
Registered: November 2016
|
Junior Member |
|
|
Hello Christian,
agree, the term usagePattern is too broad. Perhaps it could be TrackUsagePattern, so it can be read as "usage pattern of a track".
If we say, the <track> is a railway section that can be traversed by a train in a continuous motion and we give it an ID, we create a second-layer-graph. Any train path can be defined by a list of <track>.ids. I would call this "navigability".
To prevent that, we could remove the ID-attribute, so nobody can use it for referencing. In addition we could relax the definition to "it defines functional track attributes for a subset of the network". In this case we could keep the naming <track>.
Of cause we could claim - don't use Tracks for path definitions (navigation), but this was the default way of doing in RailML2. Applications which should be ported to RailML3 would try it with the well-known element <track> first.
Best regards
Stefan
|
|
|
|
Members
Search
Help
Login
Home
