Complex type
StopMonitoringSubscriptionStructure
Defined in OpRa/SIRI/xsd/siri_stopMonitoring_service.xsd:367
Type for Subscription Request for Stop Monitoring Service.
Base type
Used by elements
Content model
Type structure
-
inherited from
AbstractSubscriptionStructure4 items-
Type for unique identifier of a subscription.
-
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request.
-
Identifier to be given to Subscription.
-
-
Requested end time for subscription.
-
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1)
-
- Defined here
-
Request for information about Stop Visits, i.e. arrivals and departures at a stop.
-
Parameters that affect the subscription publishing and notification processing.
-
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request.
-
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless.
-
-
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).