| Re-factoring of <infraAttributes> [message #1844] |
Mon, 18 June 2018 12:58  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear railML community,
railML 2.4 is approaching, but we still have many elements and
attributes in our model that need some revision. For example:
<infraAttributes> and their child elements...
<infraAttributes><owner>
The attribute @uic-no can be marked DEPRECATED, because the information
is modelled as "companyCode" in codelist infrastructureManagers.xml.
<infraAttributes><operationMode>
Both parameters, @modeLegislative and @modeExecutive, are simple text
strings and not documented in the wiki and the schema. My question to
you: do you use these attributes? If yes, what do you model with these
attributes?
The attribute @clearanceManaging lists the following values: "sight",
"time", "blocking", "LZB-blocking" and "absBrakeDist". If needed at all,
I suggest to mark at least "LZB-blocking" as DEPRECATED. Any comments?
<infraAttributes><trainProtection>
Currently, the train protection system is characterized by the
attributes @monitoring (enumeration value list: "none", "intermittent",
"continuous") and @medium (enumeration value list: "mechanical",
"electric", "inductive", ...). How about adding an attribute
@trainProtectionSystem (string) to reference the matching train
protection system from codelist TrainProtectionSystems.xml. This is
already possible for the single <trainProtectionElement>.
<infraAttributes><powerTransmission>
The attribute @type is used to distinguish between conventional railways
and rack railways (de: Zahnradbahn) or others. The usage of the other
attribute @style (string) is completely unclear. If nobody has any
intelligent idea, I suggest to mark this attribute DEPRECATED. Btw: the
<powerTransmissionChange> element has also an attribute @style, which is
as myterious as the one in <infraAttributes><powerTransmission>.
<infraAttributes><speed>
What does the attribute @status stand for? Yes, this attribute appears
also in <speedChange>, but remains mysterious there, too.
<infraAttributes><epsgCode>
The purpose of this element is to name the EPSG codes of the positioning
systems that are used throughout the referencing infrastructure. In the
<geoCoord> element we used attributes @epsgCode and @heightEpsgCode.
This differs from <infraAttributes><epsgCode> where the attributes are
named @default and @extraHeight. I suggest to synchronize the naming
using @epsgCode and @heightEpsgCode. Any objections?
<infraAttributes><generalInfraAttribute>
The documentation of this element in the wiki [1] is completely empty.
Well, if there is no use case for the <generalInfraAttribute>, I suggest
to remove it aka mark it DEPRECATED.
As usual, any kind of comment is highly appreciated...
Best regards
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
