Global element
PtSituationElement
Defined in SIRI/xsd/siri_model/siri_situation.xsd:242
Type for individual PT Incident.
Type
Content model
Element structure
-
inherited from
AbstractSituationElementStructure7 items-
Time of creation of SITUATION.
-
Elements Reference to a SITUATION or an update to a SITUATION. Participant ref is optional and may be supplied from context.
-
Type for reference to a SITUATION or an update to a SITUATION. Participant ref is optional and may be supplied from context.
-
Unique identifier of a Country of a Participant who created SITUATION. Provides namespace for Participant If absent proided from context.
-
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context.
-
Unique identifier of SITUATION within a Participant. Excludes any version number.
-
-
-
-
inherited from
SituationElementStructure3 items-
situation Informatiion.
-
Associations with other SITUATIONs.
-
Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance.
-
-
Time at which SITUATION element was versioned. Once versioned, no further changes can be made.
-
- Defined here
-
Body of SITUATION.
-
Status elements.
-
Whether the SITUATION has been verified.
-
ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION.
-
Assessement of likely correctness of data. Default is reliable
-
Whether SITUATION is real or a test.
-
Likellihood of a future situation happening.
-
DEPRECATED - Use the element Progress instead, which provides an enumeration of possible values detailed in WorkflowStatusEnumeration. Publishing status one of a specified set of substates to which a SITUATION can be assigned. -v2.1
-
-
Elements affecting temporal scope of SITUATION.
-
Structured Classification Elements using TPEG Pts038 AlertCause.
-
Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message!
-
Structured classification of nature of SITUATION, from which a standardized message can be generated.
-
-
TPEG Pts38: AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
-
-
DEPRECATED since SIRI 2.1 - use only TpegReasonGroup and PublicEventReason.
-
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason)
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason)
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason)
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason)
-
-
-
Structured classification of Public Event, from which a standardized message can be generated.
-
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0)
-
Reference to a ControlAction being a reason for the situation. It is place in the ReasonGroup to emphasise that the CONTROL ACTION is the reason for the SITUATION, and not the way around: in the opposite case (a SITUATION being the reason for the CONTROL ACTION, some weather condition, or an accident, for example) the CONTROL ACTION will refer the SITUATION.
Note that if the ControlAction is the master ControlAction of a GroupOfControlActions it is assumed that the refence is valid for all the ControlActions of the group.
-
-
Severity of Incident - TPEG Pti26. Default is 'normal'.
-
Arbitrary rating of priority 1-High.
-
Confidentiality of SITUATION.
-
Intended audience of SITUATION.
-
Nature of scope, e.g. general, network.
-
Scope of incident - TPEG Pti27 ReportType
-
Whether the SITUATION was planned (e.g. engineering works) or unplanned (e.g. service alteration). Default is 'false', i.e. unplanned.
-
A whitespace-separated list of arbitrary application specific classifiers, tags or message categories for filtering or display, for example as icons on a situation map. Can be overwritten in an individual action.
-
Additional reasons
-
-
Reason
-
Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message!
-
Structured classification of nature of SITUATION, from which a standardized message can be generated.
-
-
TPEG Pts38: AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
DEPRECATED since SIRI 2.1 - use only AlertCause.
-
-
-
DEPRECATED since SIRI 2.1 - use only TpegReasonGroup and PublicEventReason.
-
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason)
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason)
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason)
-
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason)
-
-
-
Structured classification of Public Event, from which a standardized message can be generated.
-
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0)
-
Reference to a ControlAction being a reason for the situation. It is place in the ReasonGroup to emphasise that the CONTROL ACTION is the reason for the SITUATION, and not the way around: in the opposite case (a SITUATION being the reason for the CONTROL ACTION, some weather condition, or an accident, for example) the CONTROL ACTION will refer the SITUATION.
Note that if the ControlAction is the master ControlAction of a GroupOfControlActions it is assumed that the refence is valid for all the ControlActions of the group.
-
-
-
-
-
-
Text description of SITUATION. Some or all of this may have been generated from the other structured content elements. Where text has been overriden this is indicated.
-
Default language.
-
Summary of SITUATION. If absent should be generated from structure elements, and/or by condensing Description. (Unbounded since SIRI 2.0)
-
Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0)
-
Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0).
-
Further advice to passengers. (Unbounded since SIRI 2.0)
-
For internal information only, not passenger relevant
-
Any images associated with SITUATION.
-
Image description.
-
inherited from
ImageStructure3 items-
-
Reference to an image.
-
Embedded image.
-
-
Categorisation of image content.
-
-
-
-
Hyperlinks to other resources associated with SITUATION.
-
Hyperlink description.
-
-
-
Body of SITUATION.
-
-
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).