Home » railML newsgroups » railML.infrastructure » [railML3] Restricting IS:line and RTM:linearPositioningSystem (New semantic constraints suggested)
[railML3] Restricting IS:line and RTM:linearPositioningSystem [message #3224] Wed, 10 April 2024 16:59 Go to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 36
Registered: November 2022
Member
Dear all

Based on the issues discovered during the recent certifications of railML3 data and the "new" initiative of railML.org defining best practices for splitting and merging railML3 file, railML.org suggests to introduce new semantic constrains. Please review the suggested semantic constrains IS:006 and IS:014 and provide your comments.

Suggested semantic IS:006 constraint for railML3
each railway line with own mileage should always be associated with its own <linearPositioningSystem>, i.e. Advanced example of railML has three lines with their own mileages, thus should have thee <linearPositioningSystem>s.

Suggested semantic IS:014 constraint for railML3
@startMeasure and @endMeasure are start and end values of a railway <IS:line> associated with <RTM:linearPositioningSystem> not max and min values of a current file with e.g. line section

See the all semantic constraint on the Wiki https://wiki3.railml.org/index.php?title=Dev:Semantic_Constr aints

Thanks in advance.

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

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: Infrastructure element datamodel quality and input-data source
Next Topic: [railML3] Restricting aggregation of RailTopoModel
Goto Forum:
  

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

Current Time: Sun May 19 15:21:55 CEST 2024