| [Ontology v0.6] minor comments on Classes & their definition [message #3515] |
Tue, 18 March 2025 10:40  |
Rémi Collet
Messages: 13
Registered: November 2024
|
Junior Member |
|
|
Hello everyone !
Here are a few minor issues on classes I spotted while reading the docs (https://ontology.railml.org/).
The fact that there so few and minor comments tells me that Larissa did an awesome job. Congratulations to her for that !
[Preliminary note : "the xsd" is raiml3.3]
- http://ontology.railml.org/railml3#AreaElementProjection : "element projection as area location (min 3 coordinates, whereas the last coordinate is identical to the first one to close the area)"
The wording is ambiguous. I suggest we use the same wording as in the xsd :
"element projection as area location (min 4 coordinates (e.g. 3 points for triangle and 1 additional to close the area), whereas the last coordinate is identical to the first one to close the area)"
- http://ontology.railml.org/railml3#ASpeedProfile & http://ontology.railml.org/railml3#ATrainDetectionElement & http://ontology.railml.org/railml3#ATrainProtection & http://ontology.railml.org/railml3#SRSReferenceGroup : no definition
There is no definition for these attribute groups, but there exists an annotation in the xsd. Perhaps consider using them ?
More generally, what is the use of these attribute groups in the ontology ? Perhaps this issue is best discussed in another topic, though*. For example, adding to this topic : https://www.railml.org/forum/index.php?t=msg&th=1024& ;amp ;start=0&
- http://ontology.railml.org/railtopomodel#AssociatedPositioni ngSystem : "allows to group couples of coordinates to define the translation parameters between an external (geometric or linear) coordinate system and the element???s intrinsic coordinate system."
Typo or encoding error
- http://ontology.railml.org/railml3#BaseItineraryPoint : "A base itinerary is made up of 1 or more base itinerary points. Instinctively one would assume that at least 2 base itinerary points would be required, however for modeling stabling of trains at a track only a single point is needed and the requirement for a second one would actually be a problem. When describing a movement from one place to another however at least 2 base itinerary points are needed. Each such base itinerary point represents a stop or passthrough at an operational point along the route."
This is rather weird wording for a rdfs:comment. Consider rephrasing, or moving parts of this definition into a skos:editorialNote https://www.w3.org/2012/09/odrl/semantic/draft/doco/skos_edi torialNote.html ? It is the same definition in the xsd.
- http://ontology.railml.org/railml3#Braking : "train subsystem achieving safe and effective brake actions to allow speed reductions [Cruceanu, C??t??lin, and X. Perpinya. "Train braking." Relaibility and safety in railway, Intech (2012): 29-74.]"
Typos or encoding errors
- http://ontology.railml.org/railml3#DrivingResistanceDetails : no definition
There is no definition either in the xsd
- http://ontology.railml.org/railtopomodel#ElementCollectionOr dered : "Ordered set (mathematical) of element??s parts. Order is important. Repetition of elements is not allowed."
Typo or encoding error
- http://ontology.railml.org/railtopomodel#ElementCollectionUn ordered : "Set (mathematical) of element??s parts. Order is not important. Repetition of elements is not allowed."
Typo or encoding error
- http://ontology.railml.org/railml3#ElementProjection : no definition
This is a complex type in the xsd. What is the use of keeping this in the ontology ? Perhaps this is best discussed in a separate topic.*
- http://ontology.railml.org/railml3#EtcsArea : "sed to aggregate part of the infrastructure network equipped with ETCS components based on a specific operated system version"
Typo. Moreover, the definition differs from the one in the xsd.
- http://ontology.railml.org/railml3#EtcsSignalClassificationC riteria : "use this child element to specify the ETCS signal in more detail"
Use of imperative. I suggest we rather use the passive voice :
"Child element used to specify the ETCS signal in more details"
- http://ontology.railml.org/railtopomodel#GeometricCoordinate & http://ontology.railml.org/railtopomodel#GeometricPositionin gSystem : "localization expressed in a geometrical (or geographical) Reference System, so it defines the hasCoordinates (x, y, z or ?, ?, h)."
Typos or encoding errors
- http://ontology.railml.org/railtopomodel#PositioningNetEleme nt : "The NetElement with its own internal Linear Referencing System (which we called ???Intrinsic Positioning System??? as it is proper to the NetElement, created and destroyed with it)"
Typos or encoding errors
- http://ontology.railml.org/railml3#TractionDetails : no definition
Consider using the xsd definition :
"Describes the traction-force-curve as polynoms or hyperbolas over the speed range of the <powerMode> element to be used for run-time calculation / train movement simulation"
- http://ontology.railml.org/railml3#TractionInfo : no definition
Consider using the xsd definition :
"Maximum tractive force at wheels in Newton; used to calculate the traction force to be used for run-time calculation / train movement simulation in case there is no specific [tractive effort]$; given, in the lower speed range where the power hyperbola [propulsion power]$) is not defined or too high"
[]$ : both are concepts in the xsd, but only tractive effort was ported to the ontology it seems.
More general note : capitalization at the start of the definitions seem random. This should be more consistent.
*Best discussed in another topic count : 2
Ontologist @Infrabel (Belgian Railway Infrastructure Manager)
remicollet(at)infrabelbe
[Updated on: Tue, 18 March 2025 10:57] Report message to a moderator |
|
|
|
|
|
|
|
Members
Search
Help
Login
Home
