Home » railML newsgroups » railML.infrastructure » Infrastructure element datamodel quality and input-data source
Re: Infrastructure element datamodel quality and input-data source [message #3233 is a reply to message #3213] Fri, 26 April 2024 18:09 Go to previous messageGo to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 75
Registered: March 2008
Member
Dear Torben,

Regarding your question 1, I have to point out that human readable properties like name and description "are not to be used to contain computer-processable data, nor shall it be parsed by programmes in any way." (see https://wiki3.railml.org/wiki/Dev:Identities#Differentiation _from_other_indications)

Regarding question 2, there is also a proposal to move states into Common, to allow use by all the subschemas: https://development.railml.org/railml/version3/-/issues/491
I still think the interpretation of a state referring to an area should be decided in the Infrastructure community.

Regarding question 3, is this covered by an existing or proposed railML 3 use case?

Best regards
Thomas

Thomas Nygreen – Common Schema Coordinator
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
Read Message
Read Message
Read Message
Read Message
Previous Topic: railML3 suggestion to add values for @detects in IS:detector
Next Topic: [railML3] Improvement for railML element „etcsLevelTransition"
Goto Forum:
  

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

Current Time: Wed Oct 02 12:24:35 CEST 2024