Adding PublicationRef and ConsequenceCode #209
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,142 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <!-- (C) Copyright 2005-2012 CEN SIRI --> | ||
| <Siri xmlns="http://www.siri.org.uk/siri" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:d2="http://datex2.eu/schema/2_0RC1/2_0" version="2.0" xsi:schemaLocation="http://www.siri.org.uk/siri ../../xsd/siri.xsd"> | ||
| <ServiceDelivery> | ||
| <!--=======HEADER================================================== --> | ||
| <ResponseTimestamp>2026-05-17T16:00:26+01:00</ResponseTimestamp> | ||
| <ProducerRef>GT7</ProducerRef> | ||
| <Status>true</Status> | ||
| <MoreData>false</MoreData> | ||
| <!--=======PAYLOAD============================================== --> | ||
| <SituationExchangeDelivery version="2.0"> | ||
| <ResponseTimestamp>2026-05-17T16:00:26+01:00</ResponseTimestamp> | ||
| <Situations> | ||
| <PtSituationElement> | ||
| <CreationTime>2026-05-17T16:00:00.0Z</CreationTime> | ||
| <CountryRef>fr</CountryRef> | ||
| <ParticipantRef>GT7</ParticipantRef> | ||
| <SituationNumber>123456</SituationNumber> | ||
| <Version>0</Version> | ||
| <References> | ||
| <RelatedToRef> | ||
| <CreationTime>2026-05-17T16:00:00</CreationTime> | ||
| <CountryRef>fr</CountryRef> | ||
| <ParticipantRef>GT7</ParticipantRef> | ||
| <SituationNumber>123456</SituationNumber> | ||
| <Version>0</Version> | ||
| </RelatedToRef> | ||
| </References> | ||
| <Source> | ||
| <Country>fr</Country> | ||
| <SourceType>directReport</SourceType> | ||
| <AgentReference>987654</AgentReference> | ||
| <TimeOfCommunication>2026-05-17T15:55:00.0Z</TimeOfCommunication> | ||
| </Source> | ||
| <Verification>verified</Verification> | ||
| <Progress>open</Progress> | ||
| <QualityIndex>certain</QualityIndex> | ||
| <ValidityPeriod> | ||
| <StartTime>2026-05-17T16:00:00.0Z</StartTime> | ||
| <EndTime>2026-05-17T17:30:00.0Z</EndTime> | ||
| </ValidityPeriod> | ||
| <AlertCause>unattendedBag</AlertCause> | ||
| <Severity>slight</Severity> | ||
| <Priority>2</Priority> | ||
| <Audience>public</Audience> | ||
| <ReportType>point</ReportType> | ||
| <Summary xml:lang="fr">Bagage oublié à la station Saint-Paul</Summary> | ||
| <Summary xml:lang="en">Unattended bag at the metro station Saint-Paul</Summary> | ||
| <Description xml:lang="en">Unattended bag at the metro station Saint-Paul on the line 1, direction Château de Vincennes. No service between Hôtel-de-Ville and Château de Vincennes. Disrupted service between La Défense and Hôtel-de-Ville.</Description> | ||
| <Affects> | ||
| <Operators> | ||
| <AllOperators/> | ||
| </Operators> | ||
| <StopPoints> | ||
| <AffectedStopPoint> | ||
| <StopPointRef>STPL987SSP</StopPointRef> | ||
| <StopPointName xml:lang="fr">Hôtel-de-Ville</StopPointName> | ||
| </AffectedStopPoint> | ||
| </StopPoints> | ||
| <StopPlaces> | ||
| <AffectedStopPlace> | ||
| <StopPlaceRef>STPL987SP</StopPlaceRef> | ||
| <StopPlaceName xml:lang="FR">Hôtel-de-Ville</StopPlaceName> | ||
| <StopPlaceType>metroStation</StopPlaceType> | ||
| </AffectedStopPlace> | ||
| </StopPlaces> | ||
| </Affects> | ||
| <Consequences> | ||
| <Consequence> | ||
| <ConsequenceCode>C1</ConsequenceCode> | ||
| <Period> | ||
| <StartTime>2026-05-17T16:00:00.0Z</StartTime> | ||
| <EndTime>2026-05-17T17:30:00.0Z</EndTime> | ||
| </Period> | ||
| <Condition>noService</Condition> | ||
| <Severity>verySevere</Severity> | ||
| <Blocking> | ||
| <JourneyPlanner>true</JourneyPlanner> | ||
| <RealTime>true</RealTime> | ||
| </Blocking> | ||
| <Boarding> | ||
| <ArrivalBoardingActivity>alighting</ArrivalBoardingActivity> | ||
| <DepartureBoardingActivity>boarding</DepartureBoardingActivity> | ||
| </Boarding> | ||
| </Consequence> | ||
| <Consequence> | ||
| <ConsequenceCode>C2</ConsequenceCode> | ||
| <Period> | ||
| <StartTime>2026-05-17T16:00:00.0Z</StartTime> | ||
| <EndTime>2026-05-17T17:30:00.0Z</EndTime> | ||
| </Period> | ||
| <Condition>disruption</Condition> | ||
| <Severity>slight</Severity> | ||
| <Blocking> | ||
| <JourneyPlanner>true</JourneyPlanner> | ||
| <RealTime>true</RealTime> | ||
| </Blocking> | ||
| <Boarding> | ||
| <ArrivalBoardingActivity>alighting</ArrivalBoardingActivity> | ||
| <DepartureBoardingActivity>boarding</DepartureBoardingActivity> | ||
| </Boarding> | ||
| </Consequence> | ||
| </Consequences> | ||
| <PublishingActions> | ||
| <PublishToWebAction> | ||
| <ActionData> | ||
| <Type>LongText</Type> | ||
| <Prompt xml:lang="en">Unattended bag at the Saint-Paul station. No service between Hôtel-de-Ville and Château de Vincennes. Disrupted service between La Défense and Hôtel-de-Ville.</Prompt> | ||
| </ActionData> | ||
| <PublicationRef>WEB123</PublicationRef> | ||
| <ConsequenceRef>C1</ConsequenceRef> | ||
| <ConsequenceRef>C2</ConsequenceRef> | ||
| <Incidents>true</Incidents> | ||
| <HomePage>true</HomePage> | ||
| <Ticker>false</Ticker> | ||
| </PublishToWebAction> | ||
| <PublishToMobileAction> | ||
| <ActionData> | ||
| <Type>ShortText</Type> | ||
| <Prompt xml:lang="en">Unattended bag at Saint-Paul station. Disrupted service between La Défense and Hôtel-de-Ville.</Prompt> | ||
| </ActionData> | ||
| <PublicationRef>MOB123</PublicationRef> | ||
| <ConsequenceRef>C2</ConsequenceRef> | ||
| <Incidents>true</Incidents> | ||
| <HomePage>false</HomePage> | ||
| </PublishToMobileAction> | ||
| <PublishToMobileAction> | ||
| <ActionData> | ||
| <Type>ShortText</Type> | ||
| <Prompt xml:lang="en">Unattended bag at Saint-Paul station. No service between Hôtel-de-Ville and Château de Vincennes.</Prompt> | ||
| </ActionData> | ||
| <PublicationRef>MOB456</PublicationRef> | ||
| <ConsequenceRef>C1</ConsequenceRef> | ||
| <Incidents>true</Incidents> | ||
| <HomePage>false</HomePage> | ||
| </PublishToMobileAction> | ||
| </PublishingActions> | ||
| </PtSituationElement> | ||
| </Situations> | ||
| </SituationExchangeDelivery> | ||
| </ServiceDelivery> | ||
| </Siri> |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1236,6 +1236,11 @@ Note that if the ControlAction is the master ControlAction of a GroupOfControlAc | |
| <xsd:documentation>Type for disruption.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <xsd:sequence> | ||
| <xsd:element name="ConsequenceCode" type="xsd:NMTOKEN" minOccurs="0"> | ||
|
Contributor
There was a problem hiding this comment. This linking causes overly complex parsing. Notice that the example has multiple ConsequenceRef's.
Collaborator
Author
There was a problem hiding this comment. @skinkie, indeed the example has multiple
Contributor
There was a problem hiding this comment. I think is the wrong solution for the problem. It creates relationships within the document not able to be checked or enforced. There was a problem hiding this comment. The problem to solve here is the case of a SituationExchange that has several different consequences and several messages describing the situation. In this case, for a single SituationExchange, there can be several complementary messages (PublishingAction):
Depending on the context, a system using the SituationExchange needs to be able to choose between the more specific version of the message for a specific consequence (for example, a display at a specific bus stop for a specific line) or the broader version of the message whose text describes all the consequences in a single optimized message (for example, a display in the hall of a bus station to optimize screen usage).
Contributor
There was a problem hiding this comment. The question is more in the direction: is the document structure wrong for this. If it does not logically flow that PublishingActions are related to Consequences. There was a problem hiding this comment. The document structure does not seem fundamentally wrong to me.
Collaborator
There was a problem hiding this comment. @skinkie This is 2.3 Consequences, Control and PublishingAction never had a hierarchical relation. Ergo it is a messy n:m relation. In my view this was always a result on the way the standard was made. If changes are to be made, they would be for 3.0. However, in the DACH area it is unlikely that there will support for it. There was a problem hiding this comment. Adding an identifier to PublishingActions and Consequences seems to be a natural move to allow finer traceability of SituationExchange changes. There is no conceptual or relational change in adding optional identifiers. Also, I don't think that forcing a hierarchical relationship between Consequences and PublishingActions is a good idea, as both concepts are related but can exist independently (and a PublishingAction can also be related to several Consequences). Having an optional link between PublishingActions and Consequences does not break or change the concepts. It simply allows the optional indication that a specific PublishingAction is related to one or more Consequences. This is not a conceptual modification (but an addition) or a technical breaking change. |
||
| <xsd:annotation> | ||
| <xsd:documentation>Unique identifier of the Consequence, facilitating its link with the ParametrisedActionStructure.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:element> | ||
| <xsd:element name="Period" type="HalfOpenTimestampOutputRangeStructure" minOccurs="0" maxOccurs="unbounded"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Period of effect of disruption, if different from that of SITUATION.</xsd:documentation> | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.