Home » railML newsgroups » railML.infrastructure » [railML3.1|Simple Example] Errors
Re: [railML3.1|Simple Example] Errors [message #1891 is a reply to message #1871] Mon, 06 August 2018 16:04 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Felix,

again I am little bit confused about the source of data you used.
However, I am going to investigate on this and let you know about my
findings.

Best regards
Christian

Am 06.07.2018 um 14:58 schrieb Felix Prüter:
> Dear all,
> validating the Simple Example xml for railML v3.1 raised a
> list of errors:
> elements called *Ref (like platformRef) are used but not
> allowed by the schema (the corresponding element is written
> w/o the Ref suffix) etcsSignal (element of signal) should be
> etcs conforming to the schema speedSignal (element of
> signal) is not allowed by the schema at all, although
> mentioned in the corresponding html documentation in the SVN
> [1] --> clash between xsd and UML model / documentation?
> [1] https://svn.railml.org/railML3/tags/railML-3.1-beta
>
> Kind 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


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Hierarchy of overlaying speed profiles and National vs. Generic speed profiles.
Next Topic: Marking @frontier and @chargeFrontier as DEPRECATED?
Goto Forum:
  


Current Time: Wed May 08 08:39:49 CEST 2024