Home » railML newsgroups » railml.common » [Ontology v0.6] wrong range for hasElement?
[Ontology v0.6] wrong range for hasElement? [message #3567] Sat, 19 April 2025 23:45 Go to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 116
Registered: February 2025
Location: Brussels
Senior Member
IRI: http://ontology.railml.org/railtopomodel#hasElement

Seems to have the range "RTM_Network". But it's the super property of hasElementA and hasElementB. Shouldn't it have the same range, thus "RTM_Netelement"?


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
Re: [Ontology v0.6] wrong range for hasElement? [message #3884 is a reply to message #3567] Wed, 04 February 2026 08:27 Go to previous messageGo to next message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 102
Registered: November 2022
Senior Member
Dear Mathias

Thanks for reporting this. It seems to be a mistake in the ontology v0.6.

Property http://ontology.railml.org/railtopomodel#hasElement was added manually to the ontology v0.6 for the reasoning purposes.

Since v0.7 is supposed to be generated instead of manual development, this issue is to be further investigated.

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [Ontology v0.6] wrong range for hasElement? [message #3989 is a reply to message #3884] Tue, 05 May 2026 17:32 Go to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 102
Registered: November 2022
Senior Member
Dear Mathias

the issue was resolved in the branch https://development.railml.org/railml/ontology/-/tree/RTM1-5 ?ref_type=heads by repurposing the property rtm:hasElement for netConnector needs according to the model of RTM 1.5 introduced for splitting and merging of railML files. Further documentation of connector is available under https://wiki3.railml.org/wiki/IS:netConnector#Best%20Practic e_/_Examples .

For reasoning purposes other additional property may be introduced.

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML 3.3] Dublin Core schema not reachable via http
Next Topic: [railML3] Remove @version attribute from root
Goto Forum:
  


Current Time: Sat May 09 16:23:00 CEST 2026