Home » railML newsgroups » railML.infrastructure » [railML3] <border> representing open ends (unifying @type of open end borders)
[railML3] <border> representing open ends [message #3263] Tue, 25 June 2024 11:55 Go to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 49
Registered: November 2022
Member
Dear all

In an internal discussion of railML.org reviewing railML3 data coming from different parties there was an idea to unify representation of open ends in railML with semantic constraint IS:007 [1]:

"if border/@isOpenEnd='true' then border/@type should be set as @type='area'"

Do you agree that "area" is an appropriate type for borders representing open ends?

The background is as follows.

In railML3 border/@isOpenEnd=true is used to represent not surprisingly open ends. <border> also has a mandatory attribute @type with following enumeration "area, country, infrastructureManager, state, station, tariff, other:".

Currently users can set any types of borders to open ends, e.g. in one file open end can look like this <border isOpenEnd="true" @type="area"> and in other <border isOpenEnd="true" @type="other:model">.

[1] https://wiki3.railml.org/wiki/Dev:Semantic_Constraints

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Previous Topic: [railML3] Usage of //network/networkResource
Next Topic: railML3 suggestion to add values for @detects in IS:detector
Goto Forum:
  


Current Time: Mon Oct 14 13:19:36 CEST 2024