Home » railML newsgroups » railML.infrastructure » [railML3] missing @ruleCode? (railML3, @ruleCode)
Re: [railML3] missing @ruleCode? [message #2967 is a reply to message #2911] Fri, 18 March 2022 12:46 Go to previous messageGo to previous message
Torben Brand is currently offline  Torben Brand
Messages: 158
Registered: March 2016
Senior Member
Dear railML community,

Jernbanedirektoratet recommends the use of <typeDesignator> for the described UC.
The reason being that an attribute @ruleCode is obvious not powerful enough to describe both the register and the entry in a unique manner without merging the two values. The use of <designator> would water out the principle that <designator> is used to designate individual items. Thus, the use of <typeDesignator> would be best suited to univocally define the type of item. (here signal or board) We also thought about adding attributes like an enumeration list @kind or a boolean attribute @isType in <designator>, but concluded that this might also muddle <designator> breaking the principle we stated earlier.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Loading gauge profile
Next Topic: [railML3] Identifiers in Infrastructure
Goto Forum:
  


Current Time: Fri May 03 11:54:50 CEST 2024