Home » railML newsgroups » railML.infrastructure » [railML3] Type of a name of an operational point (Adding a new attribute in railML3 specifying whether the name is operational, traffic or local)
[railML3] Type of a name of an operational point [message #3211] Wed, 13 March 2024 13:56
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 36
Registered: November 2022
Dear all

<operationalPoint> [1] in railML3 has child <name> with @description, @name and @language attributes [2]. railML.org would be grateful if you could communicate your thoughts on the following points:
(1) should railML 3.3 be extended by @type of enumerated datatype of <name> for <operationalPoint> element?
(2) do you see any other ways (implicit) to categorize type of the name of <operationalPoint> in railML3?

As an example in railML2 there is this attribute of the name of <ocp> called @type with extendable enumeration "operationalName, trafficName, localName" [3]. This classification of names of operational points seems to be videly used in the real world.

Currently, when transforming railML2 data to railML3 @type (operationalName, trafficName) of railML2 has to be either discarded or mapped to the @description of railML3.

@description of <name> of <operationalPoint> of railML3 in this context:
- seems to be rather generic;
- something human-readable comparing to the enumerated datatype.

[1] https://wiki3.railml.org/wiki/IS:operationalPoint
[2] https://wiki3.railml.org/wiki/Generic:name
[3] https://wiki2.railml.org/index.php?title=IS:ocp&stable=0


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Wed, 13 March 2024 13:57]

Report message to a moderator

Read Message
Previous Topic: Avalanche system and Derailment detection
Next Topic: [railML3] <border> of type infrastructureManager
Goto Forum:

Current Time: Mon May 20 23:41:28 CEST 2024