| [Ontology v0.6] hasOperationalType/hasTrafficType [message #3704] |
Thu, 28 August 2025 14:34  |
Mathias Vanden Auweele
Messages: 174
Registered: February 2025
Location: Brussels
|
Senior Member |
|
|
Hello all,
According to railML 3.3 XSD schema, an operational point can have 0 or more opOperations that each have a OperationalType and TrafficType attribute. This links the operation and traffic type. So a specific operational point could be of operationType='Station' for trafficType='Passengers' as well as of operationalType='depot' for trafficType='freight'
Also see: https://wiki3.railml.org/wiki/IS:opOperations#3.3-0
V0.6 of the railML ontology defines properties hasOperationalType and hasTrafficType directly with domain OperationalPoint. The ontology does not restrict the number of these properties. So the above operational point can still both be of operationalType 'station' and 'depot' and have both the trafficType 'passengers' and 'freight', but the link between the OperationalType and the TrafficType is lost.
In order to comply with railML UML, the ontology should:
1) add the class "OpOperation"
2) make "OpOperation" the domain of hasOperationalType and hasTrafficType
3) add a property "hasOpOperation" with domain "OperationalPoint" and range "OpOperation"
Thanks
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
Search
Help
Members
Login
Home
