Home » railML newsgroups » railml.infrastructure » Track: description vs. trackDescr
Track: description vs. trackDescr [message #1543] Wed, 05 April 2017 19:18 Go to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 44
Registered: January 2016
Dear all,

the element <track> has an attribute @description and a repeatable child
element <trackDescr>, which both are based on datatype xs:string.

My questions to you: For which purpose do you use which description? Do
you use the <trackDescr> at all? Can you provide us an example of a
track with the different kind of descriptions?

Based on your feedback, we may update the wiki page [1] and close the
Trac ticket [2]. If <trackDescr> is not used, we may also declare it
DEPRECATED with railML version 2.4.

[1] http://wiki.railml.org/index.php?title=IS:trackDescr
[2] http://trac.railml.org/ticket/113

Best regards

Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Re: Track: description vs. trackDescr [message #1581 is a reply to message #1543] Thu, 18 May 2017 16:00 Go to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 202
Registered: August 2008
Senior Member
Dear Christian,

we currently don't use <track description= > nor <trackDescr>.

I would prefer keeping <track description= > and declaring <trackDescr>
being deprecated.

With best regards,
Previous Topic: Infrastructure registers
Next Topic: railML 2.3 infrastructure extension proposal operational properties of an OCP
Goto Forum:

Current Time: Sat May 27 02:34:59 CEST 2017