You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Typo corrections on siri_request_errorConditions.xsd (#158)
* Typo corrections on siri_request_errorConditions.xsd
Addresses issue #125
* Apply suggestions from code review
---------
Co-authored-by: Stefan de Konink <stefan@konink.de>
* Add example for DataSource in ET (#160)
* aligning SIRI with what was intended for OPERATING DAY (#134)
* aligning SIRI with what was intended
* Update xsd/siri_model/siri_journey_support.xsd
Co-authored-by: Stefan de Konink <stefan@konink.de>
* Lint and update documentation tables
---------
Co-authored-by: Stefan de Konink <stefan@konink.de>
Co-authored-by: haeckerbaer <54021300+haeckerbaer@users.noreply.github.com>
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
* Fix typos in documentation siri_situation.xsd (#147)
* Fix typos in documentation siri_situation.xsd
Fix typos & addition of one annotation missing
* add missing tags to new annotation
it seems that author added a new annotation in previous commit but forgot proper tags.
* correct typo
---------
Co-authored-by: haeckerbaer <54021300+haeckerbaer@users.noreply.github.com>
Co-authored-by: Tim Rivett <56296031+tim-rivett@users.noreply.github.com>
* remove blank in FareClassEnumerationList (#174)
---------
Co-authored-by: Tu-Tho Thai <info@tutho.com>
Co-authored-by: Stefan de Konink <stefan@konink.de>
Co-authored-by: Leonard Ehrenfried <mail@leonard.io>
Co-authored-by: Matthias Günter <matthias.guenter@sbb.ch>
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Tim Rivett <56296031+tim-rivett@users.noreply.github.com>
<xsd:documentation>Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition.</xsd:documentation>
168
+
<xsd:documentation>Additional description of error. This allows a description to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition.</xsd:documentation>
169
169
</xsd:annotation>
170
170
</xsd:element>
171
171
</xsd:sequence>
@@ -178,7 +178,7 @@ Rail transport, Roads and road transport
<xsd:documentation>Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0).</xsd:documentation>
496
+
<xsd:documentation>Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. (since SIRI 2.0).</xsd:documentation>
Copy file name to clipboardExpand all lines: xsd/siri_model/siri_journey_support.xsd
+9-4Lines changed: 9 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ Public transport, Bus services, Coach services, Bus stops and stations,
78
78
Rail transport, Railway stations and track, Train services, Underground trains,
79
79
Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
80
80
Rail transport, Roads and road transport
81
-
</Category>
81
+
</Category>
82
82
<Project>CEN TC278 WG3 SG7</Project>
83
83
</Subject>
84
84
<Title>SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of identifers common journey elements</Title>
@@ -262,7 +262,7 @@ Rail transport, Roads and road transport
<xsd:documentation>identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY is unique with the data horizon of the service. Often the OperationalDayType is used for this purpose.</xsd:documentation>
276
+
<xsd:documentation>Identifier of data frame within participant service. Used to ensure that the Reference to a DATED VEHICLE JOURNEY is unique with the data horizon of the service. Often the OPERATING DAY is used for this purpose.</xsd:documentation>
- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation.
493
493
- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition.
494
494
- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced.
495
-
</xsd:documentation>
495
+
</xsd:documentation>
496
496
</xsd:annotation>
497
497
<xsd:sequence>
498
498
<xsd:elementref="CompoundTrainRef"minOccurs="0"/>
@@ -955,6 +955,11 @@ The first class carriage of a TRAIN might, for example, be assigned to sector "A
0 commit comments