| Borders of states, tarifs etc. [message #557] |
Mon, 26 May 2014 12:35  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear everyone,
in trac ticket #242 (see [1]; scheduled for railML 2.3) it is written
that an element for describing borders in the infrastructure is needed.
However, we already have such an element. In particular:
railML contains already the type 'tBorder'. It looks like this:
<xs:complexType name="tBorder">
<xs:complexContent>
<xs:extension base="rail:tDelimitedOrientedElement">
<xs:attribute name="type" type="rail:tBorderType" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
The contained data type 'tBorderType' defines borders of states, tarifs,
etc.:
<xs:simpleType name="tBorderType">
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="tarif" />
<xs:enumeration value="area" />
<xs:enumeration value="state" />
<xs:enumeration value="country" />
<xs:enumeration value="station" />
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="rail:tOtherEnumerationValue" />
</xs:simpleType>
</xs:union>
</xs:simpleType>
So, what exactly is needed, that is not already covered by the current
implementation? Any comments appreciated...
[1] https://trac.railml.org/ticket/242#comment:5
Best regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
| Re: Borders of states, tarifs etc. [message #1249 is a reply to message #557] |
Mon, 01 June 2015 11:19  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear railML IS users,
there have not been any requests from the community. Therefore, the Trac
ticket #242 has been closed stating that the current implementation is
sufficient. If you don't agree, please feel free to discuss.
Best regards
Christian
Am 26.05.2014 um 12:35 schrieb Christian Rahmig:
> Dear everyone,
>
> in trac ticket #242 (see [1]; scheduled for railML 2.3) it is written
> that an element for describing borders in the infrastructure is needed.
> [...]
>
> So, what exactly is needed, that is not already covered by the current
> implementation? Any comments appreciated...
>
> [1] https://trac.railml.org/ticket/242#comment:5
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
