├── Trias.xsd ├── Trias_Alerts.xsd ├── Trias_Booking.xsd ├── Trias_Common.xsd ├── Trias_Connections.xsd ├── Trias_Facilities.xsd ├── Trias_FacilitySupport.xsd ├── Trias_Fares.xsd ├── Trias_FaresSupport.xsd ├── Trias_IndividualTrips.xsd ├── Trias_JourneySupport.xsd ├── Trias_LocationSupport.xsd ├── Trias_Locations.xsd ├── Trias_Maps.xsd ├── Trias_ModesSupport.xsd ├── Trias_Personalisation.xsd ├── Trias_Positioning.xsd ├── Trias_Refine.xsd ├── Trias_RequestSupport.xsd ├── Trias_ServiceRegister.xsd ├── Trias_SituationSupport.xsd ├── Trias_StopEvents.xsd ├── Trias_TripInfo.xsd ├── Trias_Trips.xsd ├── Trias_Utility.xsd ├── Trias_VehicleInterface.xsd └── siri-1.4 ├── ReadMe.txt ├── Siri-1.4.spp ├── acsb ├── acsb_accessibility-v0.3.xsd ├── acsb_all-v0.3.xsd ├── acsb_limitations-v0.2.xsd └── acsb_passengerMobility-v0.3.xsd ├── datex2 └── DATEXIISchema_1_0_1_0.xsd ├── ifopt ├── ifopt_administration-v0.3.xsd ├── ifopt_allStopPlace-v0.3.xsd ├── ifopt_checkpoint-v0.3.xsd ├── ifopt_countries-v0.2.xsd ├── ifopt_equipment-v0.3.xsd ├── ifopt_feature-v0.2.xsd ├── ifopt_location-v0.3.xsd ├── ifopt_modes-v0.2.xsd ├── ifopt_modification-v0.3.xsd ├── ifopt_path-v0.2.xsd ├── ifopt_stop-v0.3.xsd ├── ifopt_time-v0.2.xsd └── ifopt_types-v0.2.xsd ├── siri.xsd ├── siri ├── siri_all-v1.3.xsd ├── siri_allBasic-v1.3.xsd ├── siri_base-v1.3.xsd ├── siri_common-v1.4.xsd ├── siri_facilities-v1.2.xsd ├── siri_facility-v1.3.xsd ├── siri_feature-v1.1.xsd ├── siri_journey-v1.3.xsd ├── siri_location-v1.1.xsd ├── siri_modes-v1.1.xsd ├── siri_operator-v1.2.xsd ├── siri_participant-v1.1.xsd ├── siri_permissions-v1.2.xsd ├── siri_reference-v1.2.xsd ├── siri_requests-v1.3.xsd ├── siri_situation-v1.1.xsd ├── siri_situationActions-v1.0.xsd ├── siri_situationAffects-v1.1.xsd ├── siri_situationClassifiers-v1.1.xsd ├── siri_situationIdentity-v1.1.xsd ├── siri_situationReasons-v1.1.xsd ├── siri_situationServiceTypes-v1.0.xsd ├── siri_time-v1.2.xsd ├── siri_types-v1.1.xsd └── siri_utility-v1.1.xsd ├── siriSg.xsd ├── siri_connectionMonitoring_service.xsd ├── siri_connectionTimetable_service.xsd ├── siri_discovery.xsd ├── siri_estimatedTimetable_service.xsd ├── siri_facilityMonitoring_service.xsd ├── siri_generalMessage_service.xsd ├── siri_productionTimetable_service.xsd ├── siri_situationExchange_service.xsd ├── siri_stopMonitoring_service.xsd ├── siri_stopTimetable_service.xsd ├── siri_vehicleMonitoring_service.xsd ├── siri_wsConsumer.wsdl ├── siri_wsProducer.wsdl └── xml └── xml.xsd /Trias.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | Root element for TRIAS messages 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | ================ Requests ============================================= 35 | 36 | 37 | 38 | Service request element 39 | 40 | 41 | 42 | 43 | Request structure - wrapping generic SIRI request elements. 44 | 45 | 46 | 47 | 48 | 49 | 50 | Service specific request contents. 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | Subscription request element 60 | 61 | 62 | 63 | 64 | Subscription request structure - wrapping generic SIRI request element. 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | Group of all requests, including Heartbeat, Status, Termination etc. 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | Group of all service-related requests 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | Choice of payload requests 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | Group of subscription requests. 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | ================ Responses ============================================= 141 | 142 | 143 | 144 | Group of all response messages, including Heartbeat, Status, Termination etc. 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | Group of all topical response messages 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | Service delivery element 165 | 166 | 167 | 168 | 169 | Delivery structure - wrapping generic SIRI response elements. 170 | 171 | 172 | 173 | 174 | 175 | 176 | Service specific delivery contents. 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | Choice of delivery payload elements. 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | -------------------------------------------------------------------------------- /Trias_Alerts.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Time windows when alerts are welcome. 11 | 12 | 13 | 14 | 15 | Maximum frequency of subsequent alerts for the same reason. 16 | 17 | 18 | 19 | 20 | Earliest time for first alert. Measured as duration before beginning of event. Only for dated events. 21 | 22 | 23 | 24 | 25 | 26 | ==================================================== Situation Monitoring ==================================================== 27 | 28 | 29 | 30 | Request to send current facility status information 31 | 32 | 33 | 34 | 35 | ==================================================== Facility Monitoring ==================================================== 36 | 37 | 38 | 39 | Request to send current facility status information 40 | 41 | 42 | 43 | 44 | ==================================================== Trip Monitoring ==================================================== 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | IPKOM Monitoring parameters 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | Priority of events 71 | 72 | 73 | 74 | 75 | Minimum change of delay to send new notifications 76 | 77 | 78 | 79 | 80 | Whether to fetch information from other systems. Default is false. 81 | 82 | 83 | 84 | 85 | Whether alternatives should be part of the response. Default is false. 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | -------------------------------------------------------------------------------- /Trias_Connections.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | == Connection Demand ======================================= 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | The amount of time the traveller will approximately need to cover the distance between feeder and distributor. 19 | 20 | 21 | 22 | 23 | For each person that has special accessibility needs one element PassengerAccessibilityNeeds should be inserted here. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | == Connection Protection ======================================= 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | Delete a ConnectionDemand 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | == Delete Connection Demand Response ======================================= 84 | 85 | 86 | 87 | Response for a request to delete a ConnectionDemand 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | == Connection Report ======================================= 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | == Connection Status Request Response ======================================= 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | == Connection Status Subscription ======================================= 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | == Connection Status ================================================ 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | -------------------------------------------------------------------------------- /Trias_FacilitySupport.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | ==================================== Facilities from SIRI ============================================= 7 | 8 | 9 | 10 | Wrapper for SIRI facilities. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | Wrapper for SIRI stop facilities. 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | Wrapper for SIRI service facilities. 27 | 28 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /Trias_IndividualTrips.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | ================= Individual Route Service ===================== 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ==================================================== 22 | 23 | 24 | 25 | IndividualRouteRefine request structure. 26 | 27 | 28 | 29 | 30 | 31 | 32 | Context to hold objects, which are referenced within the response. 33 | 34 | 35 | 36 | 37 | 38 | 39 | ==================================================== 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | ==================================================== 51 | 52 | 53 | 54 | IndividualRouteRefine response element 55 | 56 | 57 | 58 | 59 | Context to hold objects, which are referenced within the response. 60 | 61 | 62 | 63 | 64 | 65 | Context to hold objects, which are referenced within the response. 66 | 67 | 68 | 69 | 70 | 71 | 72 | ====================== Request sub structures =========================== 73 | 74 | 75 | 76 | Individual trip request parameter structure 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | Individual trip refine request parameter structure 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | Type of algorithm to be used. If not given, "optimal" is the default, which means, that the router uses it's own measures for the optimal route. 101 | 102 | 103 | 104 | 105 | Disallow motorways. 106 | 107 | 108 | 109 | 110 | Disallow toll roads. 111 | 112 | 113 | 114 | 115 | Disallow ferries. 116 | 117 | 118 | 119 | 120 | Disallow tunnels (not underpasses). 121 | 122 | 123 | 124 | 125 | Disallow larger bridges (not overpasses). 126 | 127 | 128 | 129 | 130 | Allow unpaved roads. 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | ====================== Response sub structures ========================== 162 | 163 | 164 | 165 | 166 | 167 | Id of this individual route for referencing purposes. Unique within individual route response. 168 | 169 | 170 | 171 | 172 | Overall duration of the route. 173 | 174 | 175 | 176 | 177 | Departure time at origin. 178 | 179 | 180 | 181 | 182 | Arrival time at destination. 183 | 184 | 185 | 186 | 187 | Route distance. 188 | 189 | 190 | 191 | 192 | There must be exactly one route leg more than via locations were given in the request. 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | -------------------------------------------------------------------------------- /Trias_Maps.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | Image format as media type (formerly known as MIME type). E.g. PNG, GIF, JPEG. 12 | 13 | 14 | 15 | 16 | Map layers. Contains background and information layers. 17 | 18 | 19 | 20 | 21 | Opaqueness of the background, if no background layer was chosen. 22 | 23 | 24 | 25 | 26 | Background color of the map, if no background layer was chosen. 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | FUNCTION 3: Image-Coordinates-to-geo-position service 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | additional declarations 73 | 74 | 75 | 76 | Enumeration of available map layers (e.g. satellite, physical, routes, railway network, traffic) 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | Image size of the map. 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | Media type (formerly known as MIME type) of the returned file. Allowed are only the sub-types of the type "image". The current list of allowed subtypes is defined by the IANA. 122 | 123 | 124 | 125 | 126 | Defines the geographical area of the map. 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | -------------------------------------------------------------------------------- /Trias_Positioning.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | Positioning request element. 8 | 9 | 10 | 11 | 12 | A positioning request estimates the passenger's location in relation to stops and/or services. 13 | 14 | 15 | 16 | 17 | The movement pattern of a passenger may be obtained as GPS track (LastPositions) or from the sequence of the most recently passed stops (StopSequence). 18 | 19 | 20 | 21 | Sequence of geographic positions. 22 | 23 | 24 | 25 | 26 | Sequence of stop positions. 27 | 28 | 29 | 30 | 31 | 32 | Parameters to filter and control the result. 33 | 34 | 35 | 36 | 37 | 38 | 39 | Parameters that control the search. 40 | 41 | 42 | 43 | 44 | Filters to narrow the search space. 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | Filters to narrow the search space. If used, then the position is only searched within the realm of the given lines, modes or operators. 53 | 54 | 55 | 56 | 57 | 58 | Lines/Directions to include/exclude. 59 | 60 | 61 | 62 | 63 | Transport operators to include/exclude. 64 | 65 | 66 | 67 | 68 | 69 | 70 | Parameters that control the search behaviour. 71 | 72 | 73 | 74 | 75 | Maximum number of ranked positions that should be returned with the response. 76 | 77 | 78 | 79 | 80 | 81 | 82 | Geographic position with timestamp. 83 | 84 | 85 | 86 | 87 | Timestamp when the passenger has passed this position. 88 | 89 | 90 | 91 | 92 | Coordinate position. 93 | 94 | 95 | 96 | 97 | Speed with which passenger has passed this position. 98 | 99 | 100 | 101 | 102 | Direction in which passenger has passed this position. 103 | 104 | 105 | 106 | 107 | 108 | 109 | Stop locations with timestamps. 110 | 111 | 112 | 113 | 114 | 115 | Arrival time when the passenger arrived at this stop. 116 | 117 | 118 | 119 | 120 | Departure time when the passenger departed from this stop. 121 | 122 | 123 | 124 | 125 | 126 | ==================================================== 127 | 128 | 129 | 130 | Positioning response element. 131 | 132 | 133 | 134 | 135 | Positioning response structure. 136 | 137 | 138 | 139 | 140 | Error messages related to the response as a whole. 141 | 142 | 143 | 144 | 145 | Result structure. 146 | 147 | 148 | 149 | 150 | 151 | 152 | The positioning result including all suggestions. 153 | 154 | 155 | 156 | 157 | Result ID for further referencing 158 | 159 | 160 | 161 | 162 | Container for ranked positions. 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | Container for the suggested positions. 171 | 172 | 173 | 174 | 175 | One or more ranked positions. 176 | 177 | 178 | 179 | 180 | 181 | 182 | Position suggestion with ranking. 183 | 184 | 185 | 186 | 187 | A position within the Public Transport network may be near a stop/station (StationaryLocation) or on board of a vehicle (TripLocation). 188 | 189 | 190 | 191 | Location outside of Public Transport vehicles. 192 | 193 | 194 | 195 | 196 | Location in a Public Transport vehicle. 197 | 198 | 199 | 200 | 201 | 202 | Probability from 0 to 100. 100 means perfectly sure. 203 | 204 | 205 | 206 | 207 | 208 | -------------------------------------------------------------------------------- /Trias_Refine.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | ===================== Request structures ============================================================ 11 | 12 | 13 | 14 | Refine request element. 15 | 16 | 17 | 18 | 19 | Refine request structure. 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | ===================== Response structures ============================================================ 31 | 32 | 33 | 34 | Refine response element. 35 | 36 | 37 | 38 | 39 | Refine response structure. 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | -------------------------------------------------------------------------------- /Trias_RequestSupport.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | ====================================================Simple Types ==================================================== 7 | 8 | 9 | 10 | Type definition to identify data versions. 11 | 12 | 13 | 14 | 15 | 16 | Type definition for calculation time in milliseconds. 17 | 18 | 19 | 20 | 21 | 22 | Type definition for authorisation signatures. 23 | 24 | 25 | 26 | 27 | 28 | Type definition for certificate IDs. 29 | 30 | 31 | 32 | 33 | 34 | Properties that allow checks for message integrity. 35 | 36 | 37 | 38 | 39 | Authorisation signature. 40 | 41 | 42 | 43 | 44 | Certificate ID to retrieve the corresponding public key. 45 | 46 | 47 | 48 | 49 | 50 | ====================================================Contexts ==================================================== 51 | 52 | 53 | 54 | Generic context for all request messages. 55 | 56 | 57 | 58 | 59 | Data version 60 | 61 | 62 | 63 | 64 | Preferred languages in which to return text values. The order of languages determines their priority. 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | Generic context for all response messages. 74 | 75 | 76 | 77 | 78 | Data version 79 | 80 | 81 | 82 | 83 | Default language in which text values are returned, if not specified in the InternationalTextStructure. 84 | 85 | 86 | 87 | 88 | Calculation time. 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | Generic context for all subscription requests. 98 | 99 | 100 | 101 | 102 | Data version 103 | 104 | 105 | 106 | 107 | Preferred languages in which to return text values. The order of languages determines their priority. 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | ====================================================Request definitions==================================================== 116 | 117 | 118 | 119 | Basic request structure common for all TRIAS service requests. 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | Basic structure common for all TRIAS subscription requests. 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | Wrapper for SIRI delivery request group. 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | Wrapper for SIRI status request group. 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | Request element for terminating subscriptions (from SIRI). 156 | 157 | 158 | 159 | ====================================================Response definitions==================================================== 160 | 161 | 162 | 163 | Wrapper for SIRI service response group. 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | Basic response structure common for all TRIAS service responses. 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | Wrapper for SIRI status response group. 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | Status of the response (error conditions, more data available) 193 | 194 | 195 | 196 | 197 | 198 | Whether there is a further delivery message with more current updates that follows this one. Default is false. 199 | 200 | 201 | 202 | 203 | 204 | 205 | Response element to Data Ready message (from SIRI). 206 | 207 | 208 | 209 | 210 | Response element to Data Received message (from SIRI). 211 | 212 | 213 | 214 | ====================================================Request options ==================================================== 215 | 216 | 217 | 218 | Options for a Refine request. 219 | 220 | 221 | 222 | 223 | If true, then the request may contain object references from another EKAP. Default is FALSE. 224 | 225 | 226 | 227 | 228 | 229 | -------------------------------------------------------------------------------- /Trias_SituationSupport.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | Wrapper type for SIRI PtSituationsElementStructure 7 | 8 | 9 | 10 | 11 | SIRI situation details. 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | Reference to situation message. Message details might be found in response context or through other communication channels. 20 | 21 | 22 | 23 | 24 | Reference structure for situation message. Situation details might be found in response context or through other communication channels. 25 | 26 | 27 | 28 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /Trias_Utility.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | ========================================= General ================================================ 5 | 6 | 7 | 8 | Percent value as integer, limited to max value 100. 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | Percent value as integer, no upper limit. 17 | 18 | 19 | 20 | 21 | 22 | Data type for priority values, from 1 (highest) to 5 (lowest). 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | String that consists of only zeros and ones. 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | Data type for distances, in meters. 40 | 41 | 42 | 43 | 44 | 45 | Data type for lengths, in meters. 46 | 47 | 48 | 49 | 50 | 51 | Data type for speed, in meter per second. 52 | 53 | 54 | 55 | 56 | 57 | Type definition for phone numbers 58 | 59 | 60 | 61 | 62 | 63 | Type definition for e-mail addresses. 64 | 65 | 66 | 67 | 68 | 69 | Text with id and language code. 70 | 71 | 72 | 73 | 74 | Text content. 75 | 76 | 77 | 78 | 79 | Id of this text. May be used for matching to pre-recorded audio files. 80 | 81 | 82 | 83 | 84 | Language in which Text is formulated. 85 | 86 | 87 | 88 | 89 | 90 | 91 | URL with label. 92 | 93 | 94 | 95 | 96 | Label for link description. 97 | 98 | 99 | 100 | 101 | URL to resource on web. 102 | 103 | 104 | 105 | 106 | 107 | ========================================= Coordinates ============================================== 108 | 109 | 110 | 111 | Longitude from Greenwich. 112 | 113 | 114 | 115 | 116 | 117 | Latitude from equator. 118 | 119 | 120 | 121 | 122 | 123 | Altitude metres from sea level. 124 | 125 | 126 | 127 | 128 | 129 | Expressed as WGS84 130 | 131 | 132 | 133 | 134 | Longitude from Greenwich Meridian. -180 (West) to +180 (East). 135 | 136 | 137 | 138 | 139 | Latitude from equator. -90 (South) to +90 (North). 140 | 141 | 142 | 143 | 144 | Altitude metres from sea level. 145 | 146 | 147 | 148 | 149 | 150 | 151 | The absolute compass bearing in degrees. 152 | 153 | 154 | 155 | 156 | 157 | 158 | -------------------------------------------------------------------------------- /siri-1.4/ReadMe.txt: -------------------------------------------------------------------------------- 1 | Server Interface for Real-time Information 2 | (C) Copyright CEN SIRI 2004-2011 3 | 4 | Changes to SIRI schema v1.4a since v1.3 5 | 6 | Note that this is a work in progress version that may be updated further. Any Changes will be backwards compatible 7 | ie, if not used will not break existing function unless marked specifically 8 | 9 | ============================ 10 | 11 | 2011-04-18 Corrections - New cumulative fix version 1.4a 12 | Minor correctiosn arising from user feedback 13 | 14 | (a) siri_generalMessage_service.xsd (line 221) Missing extension point in InfoMessageStructure in Robin Vettier Ixxi.biz 15 | (i) add to general message request 16 | (ii) and siri_generalMessage_service.xsd subscription structure --> 17 | (iii) Missing type: Assign a type of normalizedString to formatRef 18 | (b) siri_requests-v1.2.xsd (line 814) ErrorConditionStructure shouldd not be abstract . Fix from RV ixxi.biz- 19 | made abstract 20 | (c) siri_journey-v1.2.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer according to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com 21 | made optional Fix from RV ixxi.biz- 22 | (d) siri_productionTimetable_service.xsd Type on request ValidityPeriod start and end should be datetime not time 23 | - Change to ClosedTimestampRange instead of ClosedTemRange 24 | - Fix Subscription request to be an element and to have IncrementalUpdate paremeter Extensions 25 | (e) siri_situation-v1.0.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, 26 | (f) ifopt_location-v0.3.xsd Correct siri: namespace 27 | (g) Fix up examples 28 | (i) correct estimated timetable request, production timetable request, stop monitoring request, stop monitoring eprmissions. drop flat examples 29 | (ii) Add examples for facility monitorign and situation exchange 30 | (h) Drop vestigial of As Flatgroup alternative coding 31 | siri_connectionTimetable_service.xsd InterchangeHourneys 32 | siri_estimatedTimetable_service.xsd EstimatedCalls --> 33 | siri_productionTimetable_service.xsd DatedCalls --> 34 | (i) Add missing type 35 | siri_requests-v1.3.xsd formatRef 36 | DATEXIISchema_1_0_1_0.xsd modelBaseversion 37 | (j)siri_facility-v1.3.xsd TidyUp empty ValidtyConditionGroup 38 | (g) Add xmlSPy project spp. 39 | 40 | ====================== 41 | Version 1.3 Approved to accompany SIRI-SX & SIRI-FM 42 | 43 | 2009-03-31 Corrections 44 | (a) siri.xsd Correct cardinality on SIRI-SX request & SIRI-FM request to be many 45 | (b) siriSg.xsd Remove uneccessary groups for decoupled version 46 | 2009-03-31 Corrections 47 | (a) stopMonitoring 48 | change the element type of MaximumNumberOfCalls.Previous, MaximumNumberOfCalls.Onwards from xsd:positiveInteger to xsd:nonNegativeInteger 49 | 50 | and clarify handling of 51 | 52 | MaximumNumberOfCalls : If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. 53 | 54 | Previous : Maximum number of previous calls to include. Zero for none. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.previous absent, include all previous calls. 55 | 56 | Onwards : Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. 57 | 58 | ___________________________________________________________________________ 59 | 60 | (b) siriSg.xsd Remove uneccessary groups for decoupled version 61 | 2009-03-03 Corrections 62 | (a) siri.xsd Correct cardinality on SIRI-SX request & SIRI-FM request to be many 63 | (b) siriSg.xsd Correct cardinality on servcierequest & subscription request to be many 64 | 2009-09-18 Siricommon - allow empty Terminate subscription response 65 | (a) Relax mandatory on in siri_common 66 | 2008-11-18 Revise FM servics 67 | (a) Revise daytypes in siri_time-v1.2 68 | 2008-11-17 Revise to support substitution groups 69 | (a) Make all requests subtypes of abstract request. Add Subst elements 70 | (b) Introduce AbstractFunctionalServiceRequest, AbstarctCapoabilityServiceRequest, AbstarctDiscoveryRequest 71 | as common supertypes. revised versiosn of siri_requests-v1.2.xsd, siri_journey-v1.2.xsd and siri_permissions-v1.1.xsd, siri-All and siribase 72 | (c) add SiriSg and Siri_base-v1.3.xsd packages 73 | 2008-11-12 Corrections to the Caridnailities on the siri_discovery services 74 | (a) Change min maxes on >LineRef, StopPoints, Features etc etc 75 | Add SubscriberRef to TerminateSubscriptionRequest 76 | 2008-10-08 Corrections to the SIRI service 77 | (a) Add SubscriberRef to TerminateSubscriptionRequest 78 | 2008-10-06 Corrections to the SIRI service 79 | (a) Correct StopTimetable SubscriptionRequest to use group 80 | (b) Correct cardinality on AnnotateStopPointRef in StopPointDeliviery 81 | 2008-10-01 Corrections to the SIRI-SX service 82 | (a) Add StatusFilterGroup to SIRI-SX request with Verification, Progress and Reality 83 | (b) Make Predictability 84 | 2008-09-30 Corrections to the SIRI-SX service 85 | (a) Make Undefined and Unknown reason codes strinsg so they do not require content 86 | (b) Extensions change defaults to lax, type =#any to simplify binding 87 | 88 | 2008-07-07 Corrections to the SIRI-SX service 89 | (a) Allow link projection and start / end offset. 90 | (b) Introduce a separate AffectedSection to handle this (refines SectionRef) 91 | used on AffectedRoute and 92 | (c) Allow a link projection & Offset on connection Link via AFfectedPathLin 93 | (d) Add an AFfectedRoad to hold basic road details 94 | (e) Correct SX request to be predctability not nature 95 | (f) Add Scope to SX request 96 | 97 | 2008-07-05 Corrections to the SIRI-SX service 98 | (a) SIRI_SX Rename AccessibilityDisruption to AccessibilityAssessment & reuse ifopt defs 99 | 2008-07-05 Corercytions toi the SIRI-SX service 100 | (a) SIRI_SX Add missing SituationRecord to RoadSituation 101 | (b) SIRI_SX correct type to be participant ref not participant pair ref--> 102 | (c) Allow zero PT or Road Situation elements in a delivery 103 | (d) Affects Line group corrected to ref a lineref and not a route ref 104 | (e) Add missing scopeType to Situation classifier group 105 | (f) Add other subreasons 106 | (g) add secondary reasons 107 | 108 | 2008 05 08 StopMonitoring service 109 | (a) Correct type on FeatureRef in Stop monitoring 110 | (b) Add StopMonitoringMultipleRequest 111 | (c) Add optional MonitoringRef to StopMonitoringDelivery so that can return id even if no data 112 | 113 | 2008 03 27 114 | Fix up ifopt & ACSB version numbers to match ifopt 0.4 115 | 116 | 117 | 2008-03-26 EstimatedTimetable Production Timetable Service Service 118 | Add wrapper tag for Line + Direction to help binding to Axis 119 | Wraps multiple instances 120 | ** Note this will break strict Comaptibility with 1.0 121 | 122 | 2008 03 12 123 | Add comments for elements and arrtributes that lacked them 124 | Correct wdsl errors 125 | strip out degree character 126 | BeyondHorizon type corrected 127 | 128 | 2008 02 12 129 | Add SIRI-SX revisions & Datex2 harmonisation features 130 | 131 | 2008 02 12 V1.3 draft 132 | ===================================== 133 | 2007 10 17 134 | Add Situation Exchange & Facility Exchange services. 135 | Added a siri_all-v1.2.xsd, ifopt_allStopPlace-v0.3.xsd, acsp_all.xsd packages to force explicit declaration of all elements in an imported namespace on the first reference. This overcomes a limitation of some XML tools that only pick up thos elements on the first import and ignotre all subsequent imports. 136 | 137 | 138 | 2007 04 17 139 | Name Space improvements 140 | revise to use explicit namespaces 141 | Change name space : http://siri.org.uk/ ==? siri.org.uk/siri 142 | 143 | harmonise Facility Monitoring 144 | Revise SpecialNeeds to use acsb package 145 | Use Ifopt facility etc 146 | Factor out Extensions to utilty file 147 | 148 | 2007 04 V1.2 149 | ======================================= -------------------------------------------------------------------------------- /siri-1.4/acsb/acsb_accessibility-v0.3.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

Fixed Objects in Public Transport. This subschema defines common accessibility types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport Type for identifier of a hazard within a stop place. Type for reference to an identifier of a hazard within a stop place. Type for limitation on navigation Unique identifier of Hazard. Validty condition governing applicability of hazard. Type for Assesment Summary indication as to whether the component is considered to be accessible or not. The Limitations that apply to component The accessibility limitations of a component. The Suitability of the component to meet specifc user needs The Suitability of com[onent to meet a specifc user need. -------------------------------------------------------------------------------- /siri-1.4/acsb/acsb_all-v0.3.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | -------------------------------------------------------------------------------- /siri-1.4/acsb/acsb_limitations-v0.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

Fixed Objects in Public Transport. This subschema defines common accessibility limitation types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility limitation types for IFOPT Fixed Objects in Public Transport Group of Enumeration of values for an accessibility value. Group Of sensory limitatiins Whether a Place has Audible signals for the viusally impaired. Whether a Place hasVisual signals for the hearing impaired. Type for accessibility Whether a Place is wheelchair accessible. Whether a Place has step free access. Whether a Place has escalator free access. Whether a Place has lift free access. Whether a Place is wheelchair accessible. Whether a Place has Visual signals availble for the free access. Whether a Place allows gudie dog access. -------------------------------------------------------------------------------- /siri-1.4/acsb/acsb_passengerMobility-v0.3.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

Fixed Objects in Public Transport. This subschema defines common accessibility types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - Passenger Mobility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport Type for accessibility needs. Records the requirementrs of a passenger that may affect chocie of facilities Specific pyschosensory need that may constrain choice of services and facilities. Whether the passenger is accompanied by a carer or assistant. Type for of a specific need one of the following Whether user need is included or excluded. Defualt is included Relative ranking of need on a sclae 1-5 Passenger mobility need for which suitability is specified. Passenger mobility need for which suitability is specified. Passenger medical need for which suitability is specified. Passenger enceumbrance need for which suitability is specified. Identification of mobilityneeds Enumeration of specific psychosensory needs Enumeration of specific Medical needs Enumeration of specific encumbrances Type for of a specific need Whether the Facility is suitable Identification of specific needs -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_allStopPlace-v0.3.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 13 | 18 | 19 | 20 | 21 | 22 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_checkpoint-v0.3.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | main schema 8 | e-service developers 9 | Europe 10 | Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 11 | 12 | 2006-08-12 13 | 14 | 15 | 2006-09-22 16 | 17 | 18 | 2007-03-29 19 | 20 | 21 | 2011-04-19 22 | 23 | 24 | 25 |

Fixed Objects in Public Transport. This subschema defines common Checkpoint types.

26 | 27 | 28 | text/xml 29 | http://www.w3.org/2001/XMLSchema 30 | XML schema, W3C Recommendation 2001 31 | 32 | {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd 33 | [ISO 639-2/B] ENG 34 | Kizoom, 109-123 Clifton Street, London EC4A 4LD 35 | Unclassified 36 | CEN, Crown Copyright 2006, 2007 37 | 38 | 39 |
    40 |
  • Derived from the SIRI standards.
    • 41 |
42 | 43 | Draft for approval 44 | 45 | Arts, recreation and travel, Tourism, Travel (tourism), Transport, 46 | Air transport, Airports, 47 | Ports and maritime transport, Ferries (marine), 48 | Public transport, Bus services, Coach services, Bus stops and stations, 49 | Rail transport, Railway stations and track, Train services, Underground trains, 50 | Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, 51 | Rail transport, Roads and road transport 52 | 53 | Cen TC278 WG3 SG6 54 | 55 | IFOPT Fixed Objects in Public Transport - Checkpoint Types. 56 | Standard 57 | 58 | 59 | Fixed Objects Checkpoint types for IFOPT Fixed Objects in Public Transport 60 | 61 | 62 | 63 | 64 | 65 | 66 | Type for identifier of a hazard within a stop place. 67 | 68 | 69 | 70 | 71 | 72 | Type for reference to am identifier of a hazard within a stop place. 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | Type for a Checkpoint Hazard that can be assocaited with 82 | 83 | 84 | 85 | 86 | Unique identifier of Hazard. 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | Validty condition governing applicability of hazard. 98 | 99 | 100 | 101 | 102 | Type of process that may occur at checkpoint 103 | 104 | 105 | 106 | 107 | Type of process that may occur at checkpoint 108 | 109 | 110 | 111 | 112 | Type of physical featrue that may slow use of checkpoint 113 | 114 | 115 | 116 | 117 | Type of crowding that may slow use of checkpoint 118 | 119 | 120 | 121 | 122 | Classification of feature of checkpoint. 123 | 124 | 125 | 126 | 127 | 128 | 129 | Allowed values for a checkpoint. 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | Allowed values for a checkpoint. 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | Allowed values for a checkpoint. 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | Allowed values for a checkpoint. 192 | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | Group of delays found at a stop grou. Duratiosn relate to given validity condition. 203 | 204 | 205 | 206 | 207 | Minimum duration needed to pass through checkpoint. 208 | 209 | 210 | 211 | 212 | Average duration expected to pass through checkpoint. 213 | 214 | 215 | 216 | 217 | Maximum duration expected to pass through checkpoint. 218 | 219 | 220 | 221 | 222 | 223 | 224 | -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_feature-v0.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

Fixed Objects in Public Transport. This subschema defines common accessibility types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.2/ifopt}ifopt_accessibility-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_modes-v0.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22

Fixed Objects in Public Transport. This subschema defines common mode types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_modes-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - mode Types. Standard Mode types for IFOPT Fixed Objects in Public Transport Types of stop place. Access to stop place. -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_modification-v0.3.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | main schema 8 | e-service developers 9 | Europe 10 | Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 11 | 12 | 2006-08-12 13 | 14 | 15 | 2006-09-22 16 | 17 | 18 | 2007-03-29 19 | 20 | 21 |

Fixed Objects in Public Transport. This subschema defines data Modification base types.

22 | 23 | 24 | text/xml 25 | http://www.w3.org/2001/XMLSchema 26 | XML schema, W3C Recommendation 2001 27 | 28 | {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_modification-v0.3.xsd 29 | [ISO 639-2/B] ENG 30 | Kizoom, 109-123 Clifton Street, London EC4A 4LD 31 | Unclassified 32 | CEN, Crown Copyright 2006, 2007 33 | 34 | 35 |
    36 |
  • Derived from the SIRI standards.
    • 37 |
38 | 39 | Draft for approval 40 | 41 | Arts, recreation and travel, Tourism, Travel (tourism), Transport, 42 | Air transport, Airports, 43 | Ports and maritime transport, Ferries (marine), 44 | Public transport, Bus services, Coach services, Bus stops and stations, 45 | Rail transport, Railway stations and track, Train services, Underground trains, 46 | Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, 47 | Rail transport, Roads and road transport 48 | 49 | Cen TC278 WG3 SG6 50 | 51 | IFOPT Fixed Objects in Public Transport - Modification Types. 52 | Standard 53 | 54 | 55 | Data Modification types for IFOPT Fixed Objects in Public Transport 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | Classification of modification as addition, deletion or revision. Enumerated value. 64 | 65 | 66 | 67 | 68 | This is a definition of a new entity 69 | 70 | 71 | 72 | 73 | This is a deletion of an existing entity 74 | 75 | 76 | 77 | 78 | This is a revision to an existing entity. All values are replaced. 79 | 80 | 81 | 82 | 83 | 84 | 85 | Classification of modification as addition, deletion, revision or delta only. Enumerated value. 86 | 87 | 88 | 89 | 90 | This is a definition of a new entity 91 | 92 | 93 | 94 | 95 | This is a deletion of an existing entity 96 | 97 | 98 | 99 | 100 | This is a revision to an existing entity. All values are replaced. 101 | 102 | 103 | 104 | 105 | This is a change to an existing enity. Only those values expliciitly supplied will be changed. 106 | 107 | 108 | 109 | 110 | 111 | 112 | A revision number is an integer that should be increased by one each time the unit that is refers to is modified. 113 | 114 | 115 | 116 | 117 | 118 | Indicates whether the entity this annotates is available for use. Use of this attribute allows entities to be retired without deleting the details from the dataset. 119 | 120 | 121 | 122 | 123 | Entity is active. 124 | 125 | 126 | 127 | 128 | Entity is inactive. 129 | 130 | 131 | 132 | 133 | Entity is still active but is in the process of being made inactive.. 134 | 135 | 136 | 137 | 138 | 139 | 140 | Grouping for modifications metadata. Creation Date required 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | Grouping for modifications metadata. 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | Grouping for modifications metadata for a document. 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | The name of the file containing the instance document. 170 | 171 | 172 | 173 | 174 | -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_path-v0.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2007-03-12 2007-03-29

Fixed Objects in Public Transport. This subschema defines stop place path types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - Stop place Base Types. Standard Basic link types for IFOPT Fixed Objects in Public Transport Type for Unique Identifier of Path Junction Reference to a Path Junction Type for reference to a Path Junction Type for Unique Identifier of Access Link Reference to an Access Link Type for reference to an Access Link Type for Unique Identifier of NavigationPath Reference to a NavigationPath. Type for Unique Identifier of NavigationPath Values for flow direction Values for path heading Values for path heading Values for Navigation type -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_time-v0.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22

Fixed Objects in Public Transport. This subschema defines Time base types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - Time Base Types. Standard Basic Time types for IFOPT Fixed Objects in Public Transport Data Type for a range of times. Start time must be specified, end time is optional. The (inclusive) start time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Type for a validity condition The (inclusive) start date and time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Day type for which timeband applies. If absent all day types in context. Any timebands which further qualify the validity condition. Timeband during which element is available or in effect. Type for a timeband. A collection of one or more validity conditions Reference to the identifier of an administrative area. -------------------------------------------------------------------------------- /siri-1.4/ifopt/ifopt_types-v0.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

Fixed Objects in Public Transport. This subschema defines common base types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 IFOPT Fixed Objects in Public Transport - Base Types. Standard Basic types for IFOPT Fixed Objects in Public Transport Arbitrary extensions. Info Link . Type for Info Link. Type for collection of info links. Distance in metres -------------------------------------------------------------------------------- /siri-1.4/siri/siri_all-v1.3.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | -------------------------------------------------------------------------------- /siri-1.4/siri/siri_allBasic-v1.3.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /siri-1.4/siri/siri_feature-v1.1.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers CEN TC278 WG3 SG7 Team Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2004-09-29 2004-10-01 2005-02-14 2005-02-20 2005-03-20 2005-05-11 2007-03-29

SIRI is a European CEN standard for the exchange of real time information .

This package defines common basic domain model identifier elements that are used in one or more SIRI fucntional service.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_reference-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG7 SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. Common DomainModel elements. Standard Data Type for Identifier of a Product Category. Data Type for Reference to a Product Category. Data Type for Identifier of a ServiceCategory. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a ServiceCategory. Data Type for Identifier of a Vehicle Feature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Vehicle Feature Code. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Identifier of a StopFeature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Feature Code. -------------------------------------------------------------------------------- /siri-1.4/siri/siri_location-v1.1.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Cen TC278 WG3 SG7 Team Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2004-09-29 2004-10-01 2005-02-14 2005-05-11 2005-05-04 2007-03-29

SIRI is a European CEN standard for the exchange of real time information . This subschema defines geospatial location elements

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_location-v1.1.xsd [ISO 639-2/B] ENG CEN Unclassified CEN, VDV, RTIG 2005, 2007
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG7 SIRI XML schema. Geo spatial location subschema Standard Longitude from Greenwich. Latitude from equator. Altitude metres from sea level. WGS84 Coordinates. Longitude from Greenwich Meridian. -180 (East) to +180 (West). Latitude from equator. -90 (South) to +90 (North). Altitude Type for GM Coordinates. Type for coordinate reference system GML Spatial coordinate reference system Type for gepspatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. Longitude from Greenwich Meridian. -180 (East) to +180 (West). Decimal degrees. eg 2.356 Latitude from equator. -90 (South) to +90 (North). Decimal degrees. eg 56.356 Coordinates of points in a GML compatibe format, as indicated by srsName attribute. Precision for point measurement. In meters. Identifier of point. identifier of data reference system for geocodes if point is specified as gml compatible Coordinates. A gml value. If not specified taken from system configuration. Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres Type for absolute bearing -------------------------------------------------------------------------------- /siri-1.4/siri/siri_operator-v1.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2006-08-12 2006-09-22 2009-10-27

SIRI Real-tiem server interface. This subschema defines operator base types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.2/ref}siri_operator-v1.1.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS Unclassified CEN, Crown Copyright 2006
  • Derived from the SIRI standards.
Version 0.1 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG6 SIRI Server Interface for Real-tiem Info - Operator Types. Standard Operator types for sirie Reference to an Operator Data Type for Identifier of an Operator Code. Reference to an Organisation Data Type for Identifier of an OrganisationCode. -------------------------------------------------------------------------------- /siri-1.4/siri/siri_participant-v1.1.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers CEN TC278 WG3 SG7 Team Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2004-09-29 2007-05-15 2008-07-015

SIRI is a European CEN standard for the exchange of real time information . This subschema defines common Participant type elements

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_participant [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2004,2005,2007
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport CEN TC278 WG3 SG7 SIRI XML schema. Participant type elements. Standard Type for Unique identifier of participant. Reference to Unique identifier of participant. -------------------------------------------------------------------------------- /siri-1.4/siri/siri_time-v1.2.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-10-03 2005-10-04 2005-05-11 2007-03-29 2008-11-10

SIRI is a European CEN standard for the exchange of real time information .

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_time-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG7 SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. Subschema of time types. Standard Data Type for a range of date and times. Both start and end time are required. The (inclusive) start date and time. The (inclusive) end date and time. Data Type for a range of times. Both start and end time are required. The (inclusive) start time. The (inclusive) end time. Data Type for a range of times. Start time must be specified, end time is optional. The (inclusive) start time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Data Type for a range of date times. Start time must be specified, end time is optional. The (inclusive) start time stamp. The (inclusive) end time stamp. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Tpeg DayType pti_table 34 Values for Day Type TPEG pti_table 34 Values for Day Type TPEG pti_table 34 Values for Day Type TPEG pti_table 34 -------------------------------------------------------------------------------- /siri-1.4/siri/siri_types-v1.1.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-10-03 2005-10-04 2005-05-11 2007-04-17

SIRI is a European CEN standard for the exchange of real time information .

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_types-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2004, 2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport Cen TC278 WG3 SG7 SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. Subschema of time types. Standard VersionString A type with no allowed content, used when simply the presence of an element is significant. A restriction of W3C XML Schema's string that requires at least one character of text. Tyoe for a string in a specified language A name that requires at least one character of text and forbids certain reserved characters. @lang. ISO language code (default is en) A string containing a phrase in a natural language name that requires at least one character of text and forbids certain reserved characters. Id type for document references Internet protocol address of form 000.000.000.000 Limited version of duration that allows for precise time arithmetic. Only Month, Day, Hour, Minute Second terms should be used. Milliseconds should not be used. Year should not be used. Negative values allowed. e.g. PT1004199059S", "PT130S", "PT2M10S", "P1DT2S", "-P1DT2S". Limited version of duration. Must be positive International phonenumber +41675601 etc Email address type -------------------------------------------------------------------------------- /siri-1.4/siri/siri_utility-v1.1.xsd: -------------------------------------------------------------------------------- 1 | main schema e-service developers CEN TC278 WG3 SG7 Team Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2008-09-307 2007-04-17

SIRI is a European CEN standard for the exchange of real time information . This subschema defines common request processing elements

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_requests-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_utility-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, Ports and maritime transport, Ferries (marine), Public transport, Bus services, Coach services, Bus stops and stations, Rail transport, Railway stations and track, Train services, Underground trains, Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, Rail transport, Roads and road transport CEN TC278 WG3 SG7 SIRI XML schema. Shared Utility elements. Standard Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). Type for Extensions to schema. Wraps an 'any' tag to ensure decidability. Placeholder for user extensions. -------------------------------------------------------------------------------- /siri-1.4/siriSg.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | main schema 8 | e-service developers 9 | Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln 10 | Mark Cartwright, Centaur Consulting Limited, Guildford 11 | Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt 12 | Stefan Fjällemark, HUR - Hovedstadens, Valby 13 | Jonas Jäderberg, Columna, Borlänge 14 | Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de 15 | Nicholas Knowles, KIZOOM LTD., London EC4A 1LT 16 | Werner Kohl, Mentz Datenverarbeitung GmbH, München 17 | Peter Miller, ACIS Research and Development, Cambridge CB4 0DL 18 | Dr. Martin Siczkowski, West Yorkshire PTE, Leeds 19 | Gustav Thiessen BLIC thi@BLIC.DE 20 | Dr Bartak, bartak@apex-jesenice.cz 21 | Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf 22 | Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin 23 | Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS 24 | Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe 25 | Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall 26 | El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall 27 | Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln 28 | Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg 29 | Robin VETTIER, ixxi.com 30 | Europe 31 | >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 32 | 33 | 2008-11-17 34 | 35 | 36 | 37 | 2008-04-18 38 | 39 | 40 | 41 | 2009-03-30 42 | 43 | 44 | 45 | 2011-04-18 46 | 47 | 48 | 49 |

SIRI is a European CEN technical standard for the exchange of real time information.

50 |

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services. 51 | 52 | This version of the schema uses substitution groups to provide a loosley coupled encoding 53 | Additional servcies may be added just by an incudues statement. 54 | 55 | It includes the following SITI servbices 56 | 57 |

    58 |
  • Production Timetable: Exchanges planned timetables.
    • 59 |
  • Estimated Timetable: Exchanges real-time updates to timetables.
    • 60 |
  • Stop Timetable: Provides timetable information about stop departures and arrivals.
    • 61 |
  • Stop Monitoring: Provides real time information about stop departures and arrivals.
    • 62 |
  • Vehicle Monitoring: Provides real time information about vehicle movements.
    • 63 |
  • Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
    • 64 |
  • Connection Monitoring: Provides real time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
    • 65 |
  • General Message: Exchanges general information messages between participants
    • 66 |
  • Facility Monitoring: Provides real time information about facilities.
    • 67 |
  • SItuation Exchange: Provides real time information about Incidents.
    • 68 |
69 |

70 |

SIRI supports both direct request/response and publish subscribe patterns of interaction.

71 |

SIRI includes common mechanisms and messages for system status management.

72 |

SIRI documents can be exchanged using http post, and/or SOAP.

73 | 74 | 75 | text/xml 76 | http://www.w3.org/2001/XMLSchema 77 | XML schema, W3C Recommendation 2001 78 | 79 | {http://www.siri.org.uk/schemas/1.4}siriSg.xsd 80 | [ISO 639-2/B] ENG 81 | Kizoom Sogtweare Ltd 16 High Holborn, London WC1V 6BX 82 | 83 | http://www.siri.org.uk/schemas/1.3/siri_base.xsd 84 | http://www.siri.org.uk/schemas/1.3/siri_estimatedTimetable_service.xsd 85 | http://www.siri.org.uk/schemas/1.3/siri_productionTimetable_service.xsd 86 | http://www.siri.org.uk/schemas/1.3/siri_stopMonitoring_service.xsd 87 | http://www.siri.org.uk/schemas/1.3/siri_vehicleMonitoring_service.xsd 88 | http://www.siri.org.uk/schemas/1.3/siri_connectionTimetable_service.xsd 89 | http://www.siri.org.uk/schemas/1.3/siri_connectionMonitoring_service.xsd 90 | http://www.siri.org.uk/schemas/1.3/siri_generalMessage_service.xsd 91 | http://www.siri.org.uk/schemas/1.3/siri_discovery.xsd 92 | http://www.siri.org.uk/schemas/1.3/siri_situationExchange_service.xsd 93 | 94 | Unclassified 95 | CEN, VDV, RTIG 2004 -2011 96 | 97 | 98 |
    99 |
  • Derived from the VDV, RTIG XML and Trident standards.
    • 100 |
101 | 102 | Version 1.4 Version with cumulatvie fixes 103 | 104 | Arts, recreation and travel, Tourism, Travel (tourism), Transport, 105 | Air transport, Airports, 106 | Ports and maritime transport, Ferries (marine), 107 | Public transport, Bus services, Coach services, Bus stops and stations, 108 | Rail transport, Railway stations and track, Train services, Underground trains, 109 | Business and industry, Transport, Air transport , Ports and maritime transport, Public transport, 110 | Rail transport, Roads and road transport. 111 | 112 | Cen TC278 WG3 SG7 113 | 114 | SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. Substitution groups version 115 | Standard 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | Service Interface for Real Time Operation. 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | -------------------------------------------------------------------------------- /siri-1.4/xml/xml.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | See http://www.w3.org/XML/1998/namespace.html and http://www.w3.org/TR/REC-xml for information about this namespace. 7 | 8 | 9 | 10 | This schema defines attributes and an attribute group suitable for use by schemas wishing to allow xml:base, xml:lang or xml:space attributes on elements they define. 11 | To enable this, such a schema must import this schema for the XML namespace, e.g. as follows: 12 | <schema . . .> 13 | . . . 14 | <import namespace="http://www.w3.org/XML/1998/namespace" 15 | schemaLocation="http://www.w3.org/2001/03/xml.xsd"/> 16 | 17 | Subsequently, qualified reference to any of the attributes or the group defined below will have the desired effect, e.g. 18 | 19 | <type . . .> 20 | . . . 21 | <attributeGroup ref="xml:specialAttrs"/> 22 | 23 | will define a type which will schema-validate an instance 24 | element with any of those attributes 25 | 26 | 27 | In keeping with the XML Schema WG's standard versioning 28 | policy, this schema document will persist at http://www.w3.org/2001/03/xml.xsd. 29 | At the date of issue it can also be found at http://www.w3.org/2001/xml.xsd. 30 | The schema document at that URI may however change in the future, in order to remain compatible with the latest version of XML Schema itself. In other words, if the XML Schema namespace changes, the version 31 | of this document at http://www.w3.org/2001/xml.xsd will change 32 | accordingly; the version at http://www.w3.org/2001/03/xml.xsd will not change. 33 | 34 | 35 | 36 | 37 | In due course, we should install the relevant ISO 639 2- and 3-letter 38 | codes as the enumerated possible values . . . 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | See http://www.w3.org/TR/xmlbase/ for 192 | information about this attribute. 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | --------------------------------------------------------------------------------