| [Ontology v0.6] hasNetElement property wrong definition? Quid "onNetElement"? [message #3568] |
Sat, 19 April 2025 23:58  |
Mathias Vanden Auweele
Messages: 143
Registered: February 2025
Location: Brussels
|
Senior 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
|
|
|
|
|
|
|
|
| Re: [Ontology v0.6] hasNetElement property wrong definition? Quid "onNetElement"? [message #3892 is a reply to message #3883] |
Sat, 14 February 2026 17:37  |
Mathias Vanden Auweele
Messages: 143
Registered: February 2025
Location: Brussels
|
Senior Member |
|
|
Dear Larissa,
1) I think "refersToNetElement" is not a good name for this property. I understand where it comes from, the attribute "ref" is used in XML to link the NetElement. But we need to build a conceptual ontology that should be breathing XML. We should be able to read the triples as if they are sentences. As such a Position never refers to a NetElement but "is on" a NetElement.
3,4) Why are there two properties like this? And why is the datatype property abbreviated?
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
| Re: [Ontology v0.6] hasNetElement property wrong definition? Quid "onNetElement"? [message #3980 is a reply to message #3892] |
Thu, 30 April 2026 15:59 |
Larissa Zhuchyi
Messages: 107
Registered: November 2022
|
Senior Member |
|
|
Dear Mathias
3,4) ontology v0.6 is based on RailTopoModel v1.4. It has datatype property rtm:hasIntrinsicCoord and object property rtm:hasIntrinsicCoordinate since RTM v1.4 has properties intrinsicCoordinates and intrinsicCoord.
RTM is originally a language independent model. It seems to me that these were named originally differently because of json use case mentioned at https://wiki.railtopomodel.org/wiki/RTM_use_cases_and_applic ation_examples that likely do not differentiate between elements and attributes.
In any case this seems to be useful also in OWL modeling since sets of object and datatype properties do not intersect.
I hope this answers your question.
Sincerely,
Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
