Home » railML newsgroups » railml.common » [Ontology0.6] less UML and more ontology
[Ontology0.6] less UML and more ontology [message #3454] Thu, 06 February 2025 12:55 Go to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 129
Registered: February 2025
Location: Brussels
Senior Member
Hello all,

The ontology currently contains much UML things inside.

- The class "BaseObject" is needed in XML schemas for requiring an ID for each data entity. But for ontology/RDF this is not needed since every entity by the standard, has a URI (even blank nodes). So this class can be removed. Every owl class is an instance of "Thing" that is very comparable to "BaseObject"

- The class "NamedObject" is needed in XML schemas for adding properties such as name. But for ontology/RDF this is not needed since we have the property "rdfs:label" that can be added to each entity and it does not need to be specified. So this class can be removed

There might be other examples but these two are good for starting the discussion.

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

[Updated on: Thu, 06 February 2025 12:56]

Report message to a moderator

Re: [Ontology0.6] less UML and more ontology [message #3481 is a reply to message #3454] Tue, 25 February 2025 08:55 Go to previous messageGo to next message
Rémi Collet is currently offline  Rémi Collet
Messages: 13
Registered: November 2024
Junior Member
I noticed the same things, and I add the very xml-y class RailML3 : https://ontology.railml.org/#RailML3 which is already deprecated though. What would be the benefit of keeping it at this time ?

Somewhat related to the topic "less UML and more ontology", the definition of Designator https://ontology.railml.org/#Designator refers to "primary keys". I think we should rather designate the latter as "external identifier". For semantic's sake, we could even call the class "External identifier".

Ontologist @Infrabel (Belgian Railway Infrastructure Manager)
remicollet(at)infrabelbe

[Updated on: Tue, 25 February 2025 08:55]

Report message to a moderator

Re: [Ontology0.6] less UML and more ontology [message #3981 is a reply to message #3454] Thu, 30 April 2026 17:41 Go to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 104
Registered: November 2022
Senior Member
Dear all

Since beginning of development of tooling railXMI2RDF announced on 48th railML conference https://www.railml.org/en/events/48th-railml-conference-madr id#dflip-flipbook_railml48-governance-and-organisational-new s-from-railml-org_13520/1/ it is suggested to merge UML model of railML and reference register https://wiki3.railml.org/wiki/Dev:Reference_register with further step replacing targets like tRef and tElementWitIDRef with the ones given in the reference register.

Generating ontology utilising transformation procedure behind railXMI2OWL helps to enrich model of railML and reduce usage of classes like tRef and tElementWitIDRef.

Therefore it gets possible to target an aim of less UML and more OWL for railML ontology.

Sincerely,

Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Previous Topic: [Ontology v0.6] hasNetElement property wrong definition? Quid "onNetElement"?
Next Topic: [railML 3.3] Dublin Core schema not reachable via http
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Jun 17 06:13:06 CEST 2026