Home » railML newsgroups » railml.common » [Ontology v0.6] hasNetElement property wrong definition? Quid "onNetElement"?
[Ontology v0.6] hasNetElement property wrong definition? Quid "onNetElement"? [message #3568] Sat, 19 April 2025 23:58
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 40
Registered: February 2025
Location: Brussels
Member
I'm trying to create a SpotLocation

I thought I needed to do something like this:

:mySpotLocation a rtm:SpotLocation;
                rtm:onNetElement :myNetElement;
                rtm:hasIntrinsicCoordinate 0.1; 
                rtm:hasApplicationDirection "both".

However:

1) there is no datatype property "rtm:onNetElement". This is a problem for both the "SpotLocation" as well as the "AssociatiatedNetElement" (for Area- and LinearLocation)

2) there is a railml:hasNetElement but it has as domain "Infrastructure" which is very odd. Is this correct?

3) The property rtm:hasIntrinsicCoordinate has a domain limited to "AssociatedPositioningSystem". I think this needs to be extended with "SpotLocation" as well as the "AssociatiatedNetElement" (for Area- and LinearLocation)

4) There is a class "IntrinsicCoordinate" which is in the range of the property "hasIntrinsicCoordinate". But why does it need to be a class? It's always a double and doesn't have any other attributes.


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
Previous Topic: [Ontology v0.6] wrong range for hasElement?
Next Topic: [Ontology v0.6] Widoco documentation not always complete
Goto Forum:
  


Current Time: Sun Jun 22 04:57:59 CEST 2025