InnholdContent
Table of Contents
| Info | ||
|---|---|---|
| ||
Se komplette eksempler for datainnsendingSee complete examples:
|
Tidsbegrenset ved opprettelse
Sluttid satt allerede ved første innsending
Meldingen vil vises i reisesøk og sanntidsdatastrøm frem til tidpunktet i <EndTime>.
...
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>.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<Progress>open</Progress> <ValidityPeriod> <StartTime>2018-02-11T11:33:11</StartTime> <EndTime>2018-04-22T22:55:00</EndTime> </ValidityPeriod> |
Gyldig frem til ny melding avslutter den opprinnelige
Sluttid er ikke satt ved første innsending
...
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.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<Progress>open</Progress> <ValidityPeriod> <StartTime>2018-02-11T11:33:11</StartTime> </ValidityPeriod> |
Sette sluttid ved senere/siste innsending
...
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.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<Progress>closed</Progress> <ValidityPeriod> <StartTime>2018-02-11T11:33:11</StartTime> <EndTime>2018-02-12T20:10:00</EndTime> </ValidityPeriod> |
Når 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.