| Re: RailML-compliant? [message #1253 is a reply to message #1242] |
Mon, 14 September 2015 10:30  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear all,
just for clarification:
As already indicated by Bernhard an <openEnd> element as a child element
of <switch> is, of course, invalid syntax. Please refer to [1] to find
out that a <switch> must have at least one <connection> element for
defining the connection to a branching track.
[1]
http://schemas.railml.org/2013/railML-2.2/documentation/rail ML.html#element_switch_Link05F708D0
Best regards
Christian
Am 02.02.2015 um 15:01 schrieb A. Kuckelberg:
> Dear all,
> we received "RailML2.2-compliant" infrastructure data but had some
> problems parsing it.
>
> There is one element <switch> (within infrastructure ->
> tracks->track->trackTopology->connections) which contains an
> openEnd-element:
>> <switch [...]>
>> <openEnd id="..." code="..."/>
>> </switch>
> Is this compliant to RailML 2.2?
> If so, where can I find it within the schema?
> If not, is this invalid data with respect to the RailML-2.2-Schema?
>
> The corresponding part of the XSD is:
> <xs:complexType name="eSwitch">
> <xs:complexContent>
> <xs:extension base="rail:tSwitch">
> <xs:sequence>
> <xs:element name="connection" type="rail:tSwitchConnectionData"
> maxOccurs="3">
> <xs:annotation>
> <xs:documentation
> source="http://wiki.railml.org/index.php?title=IS:connection_switch" />
> </xs:annotation>
> </xs:element>
> </xs:sequence>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
>
>
> Thanks in advance,
> Alexander
>
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
