InnholdContent

Tidsbegrenset ved opprettelse

<EndTime> er satt

...

Limited validity already when published

The message is visible to the public and in real-time data streams up to the time defined in <EndTime>.

<Progress>open</Progress>
	<ValidityPeriod>
		<StartTime>2018-02-11T11:33:11</StartTime>
		<EndTime>2018-04-22T22:55:00</EndTime>
	</ValidityPeriod>
	<UndefinedReason/>
	<Priority>18</Priority>
	<ReportType>general</ReportType>
	<Description xml:lang="NO">Plattform 2 er ikke i bruk. Vær oppmerksom på at det kan bli sporendringer.</Description>
	<Description xml:lang="EN">Platform 2 is closed. Track changes may occur.</Description>
	<Affects>
		<StopPoints>
			<AffectedStopPoint>
				<StopPointRef>NSR:StopPlace:652</StopPointRef>
				<StopPointName>Dovre</StopPointName>
			</AffectedStopPoint>
		</StopPoints>
	</Affects>
</PtSituationElement>

Gyldig frem til ny melding avslutter den opprinnelige

...

</ValidityPeriod>

Valid until a new message closes the initial message

The message is visible to the public and in real-time data streams from the time defined in <StartTime> until an updated of the message (with the same ID) changes <Progress> from 'open' to 'closed.

<Progress>open</Progress>
<ValidityPeriod>
	<StartTime>2018-02-11T11:33:11</StartTime>
</ValidityPeriod>

...

EndTime must be defined in the "closing" message

When the status of a message changes from 'open' to 'closed', EndTime of the message must be set to at least 5 hours into the future. This is to ensure that all systems are able to receive the close-message, even when there are severe disturbances in uptime.

<Progress>closed</Progress>
<ValidityPeriod>
	<StartTime>2018-02-11T11:33:11</StartTime>
	<EndTime>2018-02-12T20:10:00</EndTime>
</ValidityPeriod>

Når <Progress>closed<When <Progress>closed</Progress> er mottat vil meldingen

...

is received, the message will:

• not be shown in search results in the journey planner.
• be available with <Progress>closed</Progress> in real-time streams until the <EndTime> has passed.