| railML 3.x - NTSM use case organisational/contact data [message #1931] |
Tue, 28 August 2018 16:52  |
Futera Miloš
Messages: 1
Registered: August 2018
|
Junior Member |
|
|
Dear railML-Community,
we intend to publish our network statement with the availability of a
stable railML 3 version also in this format.
We would like to publish the following values in railML-3 format:
- Country and IM of a line, a track and an operating point
- Membership in national classification (e.g. NUTS-1; NUTS-2; NUTS-3; ...)
- Regional Directorate / Branch of the IM
- Dispatching area and dispatching centre of the IM
- Category of TSI INF for Passenger and Cargo
- Address of the operating point and availability
(telephone, fax, mobile GSM, GSM-R, RBC availability,...)
Can these values be added in one of the next
railML-3 versions under the use case NSTM?
--
Miloš Futera
Správa železniční dopravní cesty, státní organizace
http://www.szdc.cz
|
|
|
|
| Re: railML 3.x - NTSM use case organisational/contact data [message #1932 is a reply to message #1931] |
Tue, 28 August 2018 17:44  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Milos,
thank you for your input to updating the railML NEST use case. Please
let me comment on your long "wishlist" in detail below:
Am 28.08.2018 um 16:52 schrieb Futera Miloš:
> [...]
> - Country and IM of a line, a track and an operating point
railML 3 already contains information about the infrastructure manager
responsible for a line or operational point. Both elements,
<operationalPoint> and <line> have an appropriate attribute
@infrastructureManagerRef that links to the <infrastructureManager> in
container <organisationalUnits>. The codelist infrastructureManagers.xml
lists all the infrastructure managers with their UIC and ISO country
code, e.g. "SZDC" with "0054" (UIC) and "CZ" (ISO). So, I think, that
this request is fulfilled with railML 3.1.
> - Membership in national classification (e.g. NUTS-1; NUTS-2; NUTS-3; ...)
Interesting topic. So far, railML does not contain any location
information in context of "NUTS" [1]. However, this seems to be a very
generic part of the model (to be applied for many elements) and
therefore, detailed investigation of possible implementation options
shall be done - I think, that this is a topic for the railML NEST
working group.
> - Regional Directorate / Branch of the IM
If I understand you correctly, you want to reference a department or
regional office of a known infrastructure manager? What is the purpose
behind? Which (specific) information do you need?
> - Dispatching area and dispatching centre of the IM
Again a topic of responsibilities. Probably it is not sufficient to have
only one reference to an infrastructure manager from an OP or a line.
Maybe, it is better to reference different railway companies by their
role: For example, a railway line can be owned by one company,
maintained by another one and operated by a third one. So, instead of
having one attribute @infrastructureManagerRef, we may think about
several attributes @ownedBy, @operatedBy, @maintainedBy, @dispatchedBy?
> - Category of TSI INF for Passenger and Cargo
Do you refer to TSI line categories? Certainly, we should have
references to TSI codes, but the aim should be to model the railway
infrastructure primarily by its physical parameters and not by
definitions of categories.
> - Address of the operating point and availability
> (telephone, fax, mobile GSM, GSM-R, RBC availability,...)
Good point. I am quite sure that there exists already some standard or
data exchange format or schema for address and contact data. Does
anybody from the community have any experiences?
> Can these values be added in one of the next
> railML-3 versions under the use case NSTM?
As I mentioned in the beginning: we should take these issues on the
agenda for the railML NEST use case working group and then work on their
implementation step by step.
[1]
https://en.wikipedia.org/wiki/Nomenclature_of_Territorial_Un its_for_Statistics
Best regards from Dresden
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
